Link to home
Start Free TrialLog in
Avatar of deltaend
deltaend

asked on

Server 2008 R2 RDP Very Slow

Here is the deal.  We have a Server 2008 R2 server with Hyper-V and a couple of Server 2008 R2 virtual machines running inside of it.  Currently, no matter what the client software is, the host Server 2008 R2 that has Remote Desktop Connections enabled on it for administrative purposes, runs painfully slowly through Remote Desktop Connections.  Locally on the box however it runs very quickly.  The virtual machines themselves do not share the host's slow problem, in fact, they seem to have even faster access to the internet than the host does but to be fair, the host itself doesn't have a network specific slowness issue, simply a painfully slow RDP when people connect TO the Host from a different computer (to administrate and such).  We tested several clients and have already performed the troubleshooting suggestions located at:
http://blog.tmcnet.com/blog/tom-keating/microsoft/remote-desktop-slow-problem-solved.asp
to no avail.  We have changed the network driver for the server back and forth from old to new, again to no avail.  We have fully disabled QOS on the server and disabled then re-enabled the firewall, network connection, and the virtual Hyper-V network.  

Any ideas?
Avatar of debuggerau
debuggerau
Flag of Australia image

Have you eliminated any routers and poor links that may change the experience?
Try accessing a remote RDP from a virtual session is a good test.

Does performance monitor show any bottlenecks?
Avatar of deltaend
deltaend

ASKER

We are trying this connection from inside of the building so there is only a single switch between the computer and the server.  From the same computer, connections to the Virtual Machines inside the host are flawless, and all other types of non-RDP related connection activity to the host server are fast as well.  It's like RDP on the host server decided that it wanted to move at dial-up speed.
The network diagnostics don't find anything wrong.
Update:  I removed the Hyper-V virtual network from the server and everything fixed itself with the host.  Now I have to figure out why adding the virtual Hyper-V network messes things up... any thoughts?
ASKER CERTIFIED SOLUTION
Avatar of deltaend
deltaend

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial