Windows Forum

Ask something
Discussion Locked

Slow Connecting to Terminal Server

0 helpful
6 replies

by greg.gotcher

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am have trouble with a few of my user connecting to Terminal Server. It just started happening. When the users click on the icon to connect to Terminal Server it says connecting to ... (where ServerName is the name of the server theyare trying to connect to) this can sit on the screen up to 5 minutes before it actually connects to the Terminal Server. It use to take between 10 and 20 seconds. I am running Windows 2000 Terminal Server with Service Pack 3. Any suggestions would be greatly appreciated as my users are becoming very frusterated. Thank You in advance for your help.

6 replies

by sgt_shultz

what have you tried? have you eliminated wiring as a possible culprit? what do these problem users have in common do you think? do they sit near each other, logon at unusual times, anything like that? has any thing changed? new cleaning person, new phone wiring, anybody mucking about in the walls or ceiling?

by greg.gotcher

That's the problem, nothing has really changed. It is sparatic users that are not working correctly. I believe the only thing that they have in common is that they are using Windows 98 machines to run the client.

by jeremy the it guy

I had this problem and if I used the computer's IP address instead of it's hostname, it worked alot faster. Reason being is that there is no underlying connections to DNS servers for name resolution and such. Give it a try. If it doesn't work, it's not DNS. If so, I can help you fix DNS. Thanks, Jeremy

This discussion is closed to new replies.