Cannot connect to Terminal Server

Sorry for the basic question. I just installed Terminal services on W2K
Advanced Server in Remote Administration mode. Also, created client disks
for installation on XP Home. The server is behind a router and tried to
remote access to it through the internet (static IP). No connection (server
busy message shows up). Is there any set up necessary for the router, like
port number and forwarding? Any other causes for this problem?
Appreciate any help on this.

Yes, you need to forward port 3389 to your TS.

By the way, the rdp client that comes with W2K server is by now
*very old*.
Download the newest here:

http://www.microsoft.com/downloads/...ilyID=80111f21-
d48d-426e-96c2-08aa2bd23a49&DisplayLang=en

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*


"=?Utf-8?B?a2szOTU=?=" <kk395@discussions.microsoft.com> wrote on
10 dec 2004:

> Sorry for the basic question. I just installed Terminal
> services on W2K Advanced Server in Remote Administration mode.
> Also, created client disks for installation on XP Home. The
> server is behind a router and tried to remote access to it
> through the internet (static IP). No connection (server busy
> message shows up). Is there any set up necessary for the
> router, like port number and forwarding? Any other causes for
> this problem? Appreciate any help on this.

Thank you Vera, with port 3389, it started working. By the way, is there any
way to restart the computer from Terminal Services? "Shut down" only allows
logoff and disconnect.
Also, the link you indicated for rdp client is not supported any more. Does
this (seems for W2K3) work, too, even if my server is W2K adv server?
http://www.microsoft.com/downloads/...&DisplayLang=en

Thank you very much for your help.


"Vera Noest [MVP]" wrote:

> Yes, you need to forward port 3389 to your TS.
>
> By the way, the rdp client that comes with W2K server is by now
> *very old*.
> Download the newest here:
>
> http://www.microsoft.com/downloads/...ilyID=80111f21-
> d48d-426e-96c2-08aa2bd23a49&DisplayLang=en
>
> --
> Vera Noest
> MCSE,CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> *----------- Please reply in newsgroup -------------*
>
>
> "=?Utf-8?B?a2szOTU=?=" <kk395@discussions.microsoft.com> wrote on
> 10 dec 2004:
>
> > Sorry for the basic question. I just installed Terminal
> > services on W2K Advanced Server in Remote Administration mode.
> > Also, created client disks for installation on XP Home. The
> > server is behind a router and tried to remote access to it
> > through the internet (static IP). No connection (server busy
> > message shows up). Is there any set up necessary for the
> > router, like port number and forwarding? Any other causes for
> > this problem? Appreciate any help on this.
>

Both links work for me, the one you found is version 5.2.3790,
which came with Windows Server 2003.
The one on my link is the updated client from XP SP2, version
5.1.2600.2180, aka version 6.0.2600.0 (Microsoft mixed up the
version numbers).
Both should be OK for you to connect to W2K TS.

Yes you can reboot the server from withing the TS session. If
Shutdown is not available on your Start menu, check your
permissions and your Group Policies, which might block this option
from the Start Menu.
You can always reboot the server from the command prompt, with
shutdown /reboot.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"=?Utf-8?B?a2szOTU=?=" <kk395@discussions.microsoft.com> wrote on
11 dec 2004 in microsoft.public.win2000.termserv.apps:

> Thank you Vera, with port 3389, it started working. By the way,
> is there any way to restart the computer from Terminal Services?
> "Shut down" only allows logoff and disconnect.
> Also, the link you indicated for rdp client is not supported any
> more. Does this (seems for W2K3) work, too, even if my server
> is W2K adv server?
> http://www.microsoft.com/downloads/details.aspx?
FamilyID=a8255ffc
> -4b4a-40e7-a706-cde7e9b57e79&DisplayLang=en
>
> Thank you very much for your help.
>
>
> "Vera Noest [MVP]" wrote:
>
>> Yes, you need to forward port 3389 to your TS.
>>
>> By the way, the rdp client that comes with W2K server is by now
>> *very old*.
>> Download the newest here:
>>
>> http://www.microsoft.com/downloads/....aspx?FamilyID=
80111f2
>> 1- d48d-426e-96c2-08aa2bd23a49&DisplayLang=en
>>
>> --
>> Vera Noest
>> MCSE,CCEA, Microsoft MVP - Terminal Server
>> http://hem.fyristorg.com/vera/IT
>> *----------- Please reply in newsgroup -------------*
>>
>>
>> "=?Utf-8?B?a2szOTU=?=" <kk395@discussions.microsoft.com> wrote
>> on 10 dec 2004:
>>
>> > Sorry for the basic question. I just installed Terminal
>> > services on W2K Advanced Server in Remote Administration
>> > mode. Also, created client disks for installation on XP Home.
>> > The server is behind a router and tried to remote access to
>> > it through the internet (static IP). No connection (server
>> > busy message shows up). Is there any set up necessary for
>> > the router, like port number and forwarding? Any other
>> > causes for this problem? Appreciate any help on this.

Vera,
Thanks a lot. I think Microsoft site had some problem when I accessed the
link before. Now it works ok. Also, I added my user name to the
administrator group and it showed restart and shutdown. Thank you very much
for your help. It was great!

"Vera Noest [MVP]" wrote:

> Both links work for me, the one you found is version 5.2.3790,
> which came with Windows Server 2003.
> The one on my link is the updated client from XP SP2, version
> 5.1.2600.2180, aka version 6.0.2600.0 (Microsoft mixed up the
> version numbers).
> Both should be OK for you to connect to W2K TS.
>
> Yes you can reboot the server from withing the TS session. If
> Shutdown is not available on your Start menu, check your
> permissions and your Group Policies, which might block this option
> from the Start Menu.
> You can always reboot the server from the command prompt, with
> shutdown /reboot.
>
> --
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
> "=?Utf-8?B?a2szOTU=?=" <kk395@discussions.microsoft.com> wrote on
> 11 dec 2004 in microsoft.public.win2000.termserv.apps:
>
> > Thank you Vera, with port 3389, it started working. By the way,
> > is there any way to restart the computer from Terminal Services?
> > "Shut down" only allows logoff and disconnect.
> > Also, the link you indicated for rdp client is not supported any
> > more. Does this (seems for W2K3) work, too, even if my server
> > is W2K adv server?
> > http://www.microsoft.com/downloads/details.aspx?
> FamilyID=a8255ffc
> > -4b4a-40e7-a706-cde7e9b57e79&DisplayLang=en
> >
> > Thank you very much for your help.
> >
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Yes, you need to forward port 3389 to your TS.
> >>
> >> By the way, the rdp client that comes with W2K server is by now
> >> *very old*.
> >> Download the newest here:
> >>
> >> http://www.microsoft.com/downloads/....aspx?FamilyID=
> 80111f2
> >> 1- d48d-426e-96c2-08aa2bd23a49&DisplayLang=en
> >>
> >> --
> >> Vera Noest
> >> MCSE,CCEA, Microsoft MVP - Terminal Server
> >> http://hem.fyristorg.com/vera/IT
> >> *----------- Please reply in newsgroup -------------*
> >>
> >>
> >> "=?Utf-8?B?a2szOTU=?=" <kk395@discussions.microsoft.com> wrote
> >> on 10 dec 2004:
> >>
> >> > Sorry for the basic question. I just installed Terminal
> >> > services on W2K Advanced Server in Remote Administration
> >> > mode. Also, created client disks for installation on XP Home.
> >> > The server is behind a router and tried to remote access to
> >> > it through the internet (static IP). No connection (server
> >> > busy message shows up). Is there any set up necessary for
> >> > the router, like port number and forwarding? Any other
> >> > causes for this problem? Appreciate any help on this.
>