Hi - This is probably a simple problem but I'm a desktop guy first and a
server guy second. I have installed a server using server 2000 and have
enable Terminal server on it. I'm able to login via TS inside the office
using the server name so I'm assuming TS is running correctly. I have a
static IP for ext. connection but when I attempt to connect it says server
not available. I have a consumer grade router with firewall services and I'm
assuming I have to enable something in the router or open a port. Can
anybody help me with the answer? Chris P.

Yes, port 3389 has to be forwarded to your TS.
Note that this means that you open up your TS to the whole world.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Q2hyaXM=?= <Chris@discussions.microsoft.com> wrote on 03
aug 2006 in microsoft.public.win2000.termserv.apps:

> Hi - This is probably a simple problem but I'm a desktop guy
> first and a server guy second. I have installed a server using
> server 2000 and have enable Terminal server on it. I'm able to
> login via TS inside the office using the server name so I'm
> assuming TS is running correctly. I have a static IP for ext.
> connection but when I attempt to connect it says server not
> available. I have a consumer grade router with firewall
> services and I'm assuming I have to enable something in the
> router or open a port. Can anybody help me with the answer?
> Chris P.

Gulp ok you've scared me now. I have a TS running at a diff. job that has TS
enabled on the router and being passed thru to the server. Disc. this after
I posted this. To get in one must have a valid username and password. This
would be enabled on the server mentioned here. Is there a different approach
to all of this that I should consider/know about? thank you....Chris

"Vera Noest [MVP]" wrote:

> Yes, port 3389 has to be forwarded to your TS.
> Note that this means that you open up your TS to the whole world.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?Q2hyaXM=?= <Chris@discussions.microsoft.com> wrote on 03
> aug 2006 in microsoft.public.win2000.termserv.apps:
>
> > Hi - This is probably a simple problem but I'm a desktop guy
> > first and a server guy second. I have installed a server using
> > server 2000 and have enable Terminal server on it. I'm able to
> > login via TS inside the office using the server name so I'm
> > assuming TS is running correctly. I have a static IP for ext.
> > connection but when I attempt to connect it says server not
> > available. I have a consumer grade router with firewall
> > services and I'm assuming I have to enable something in the
> > router or open a port. Can anybody help me with the answer?
> > Chris P.
>

There are a lot of tools out there which are rather good in getting
your username / password combination.

I would recommend a freeware utility called SecureRDP.
Downloadable here:
http://www.2x.com/securerdp/
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Q2hyaXM=?= <Chris@discussions.microsoft.com> wrote on 03
aug 2006 in microsoft.public.win2000.termserv.apps:

> Gulp ok you've scared me now. I have a TS running at a diff.
> job that has TS enabled on the router and being passed thru to
> the server. Disc. this after I posted this. To get in one must
> have a valid username and password. This would be enabled on
> the server mentioned here. Is there a different approach to all
> of this that I should consider/know about? thank you....Chris
>
> "Vera Noest [MVP]" wrote:
>
>> Yes, port 3389 has to be forwarded to your TS.
>> Note that this means that you open up your TS to the whole
>> world.
>> _________________________________________________________ Vera
>> Noest MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?Q2hyaXM=?= <Chris@discussions.microsoft.com> wrote on
>> 03 aug 2006 in microsoft.public.win2000.termserv.apps:
>>
>> > Hi - This is probably a simple problem but I'm a desktop guy
>> > first and a server guy second. I have installed a server
>> > using server 2000 and have enable Terminal server on it. I'm
>> > able to login via TS inside the office using the server name
>> > so I'm assuming TS is running correctly. I have a static IP
>> > for ext. connection but when I attempt to connect it says
>> > server not available. I have a consumer grade router with
>> > firewall services and I'm assuming I have to enable something
>> > in the router or open a port. Can anybody help me with the
>> > answer? Chris P.

Thank you, I have downloaded the program and will read up on it Friday.

Have a good weekend...Chris P

"Vera Noest [MVP]" wrote:

> There are a lot of tools out there which are rather good in getting
> your username / password combination.
>
> I would recommend a freeware utility called SecureRDP.
> Downloadable here:
> http://www.2x.com/securerdp/
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?Q2hyaXM=?= <Chris@discussions.microsoft.com> wrote on 03
> aug 2006 in microsoft.public.win2000.termserv.apps:
>
> > Gulp ok you've scared me now. I have a TS running at a diff.
> > job that has TS enabled on the router and being passed thru to
> > the server. Disc. this after I posted this. To get in one must
> > have a valid username and password. This would be enabled on
> > the server mentioned here. Is there a different approach to all
> > of this that I should consider/know about? thank you....Chris
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Yes, port 3389 has to be forwarded to your TS.
> >> Note that this means that you open up your TS to the whole
> >> world.
> >> _________________________________________________________ Vera
> >> Noest MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> ___ please respond in newsgroup, NOT by private email ___
> >>
> >> =?Utf-8?B?Q2hyaXM=?= <Chris@discussions.microsoft.com> wrote on
> >> 03 aug 2006 in microsoft.public.win2000.termserv.apps:
> >>
> >> > Hi - This is probably a simple problem but I'm a desktop guy
> >> > first and a server guy second. I have installed a server
> >> > using server 2000 and have enable Terminal server on it. I'm
> >> > able to login via TS inside the office using the server name
> >> > so I'm assuming TS is running correctly. I have a static IP
> >> > for ext. connection but when I attempt to connect it says
> >> > server not available. I have a consumer grade router with
> >> > firewall services and I'm assuming I have to enable something
> >> > in the router or open a port. Can anybody help me with the
> >> > answer? Chris P.
>