Windows Forum

Ask something
Discussion Locked

Terminal Services Advanced Client

0 helpful
7 replies

by millstinej

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have deployed the use of the Web enabled terminal services on a windows 2000 seerver running IIS 5.0. It works fine BEHIND my Linksys router but when I try to access the page on the PUBLIC side or wan side of the router it doesn't function. I've port forwarded to the private side server on port 80 inside the router(I've done this before on my Linux box w/ Apache and it works FINE!) and it doesn't work. I've also called Linksys and they feel that it is an Windows IIS issue.

any help would be greatly appreciated...
Thanks

7 replies

by joseph moore

Sounds like a port filtering issue. I did a check on Technet, and article "Windows NT, Terminal Server, and Microsoft Exchange Services Use TCP/IP Ports (Q150543)" says that the ActiveX client for TSAC uses TCP port 80 & 3389.
So, my guess is yourLinksys box is blocking TCP port 3389 from external access.
Check the Linksys setup to allow that port to be reached from the outside world.

hope this helps

by nitin

Foward port 80 & 3389. These are required for TSAC to function. Only HTTP - I think you will get cannot open page error.

by shmaltz

You forgot to forward port 3389 to you Terminal Server. You have to forward 3389 to the TS, other wise the connection to the TS will fail.

This discussion is closed to new replies.