Discussion Locked

W2K Term Ser. and Linky Router

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm trying to set-up a W2K Term Serv behind a Linky (befsr11) router. The 'helpful' people @ linksys had me try about 100 different things, with no response. The machines trying to access the term serv get a 'server too busy' message when trying to connect. They can, however, connect to our ISP's term serv. We can also access the term serv locally so it's a matter of getting thru the linky. Please help.

5 replies

by mckaytech

Terminal services by default uses port 3389. Microsoft has an article on their TechNet site (#Q187628) that describes how to test whether this port is being blocked by your router/firewall.

Two other articles on troubleshooting TS connection issues are Q186645 and Q193891.

But it sounds suspiciously like a configuration problem on the Terminal Server itself because it sounds like your clients CAN get through the router to your ISP's terminal server. Also, the 'server too busy' message would be un-usual in the case of a complete connection failure.

paul

by currera501

If you are still having the problem, This is how you set it up. Go to the admin tools list and go to computer managment snapin and then right click on users and add who you want, When finished reboot thats it. That will get you logged on to the terminal server.

This discussion is closed to new replies.