Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Poor connection time to Terminal Server

Status
Not open for further replies.

MockY

Programmer
Jul 7, 2006
94
I just rebuilt my network. Before I had all services on one server (DC, TS, DHCP and so on) which made the experience for my 30+ users sluggish. I finally got down to rebuilt it and have now specific machines for each server role.

The problem is now that when ever a client tries to connect to the Terminal Server using the RDP 6.0 client, it takes almost 2 minutes before the user is connected and is prompted to enter the log in information. Once that is done, it takes about 30 seconds before the profile is fully loaded and the user can start his session. Once logged on, the system flies and works perfectly, just like I intended it to.

I assume it has to to with DNS settings but I have tried many different solutions but none works. Using the same RDP 6.0 client to connect to the Domain Controller works just fine. It takes about 4 seconds to fully log in and load the profile. This was the case before when the same machine ran Terminal Services and as a Domain Controller.

So any ideas why this is? If a user logs in using the older RDP client (5.1 I think) it logs in like it should, which makes me to believe that the encryption algorithm RDP 6.0 has makes it slow. However, this was not the case before and it was almost just as fast as the old client.

Any help is much appreciated, and I'll send more information is that is needed.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top