I have for years connected to a small set of servers via Remote Desktop (currently, Win7 client, Win2008 R2 servers). Performance is the equivalent of being directly connected. The client machine is not in the network, but I connect via IP and use network credentials.
Recently, I built a new server (to host Hyper-V), and then a new workstation (Win 7) to manage it and develop on it. This is all on the same network segment as the previously mentioned servers and client.
The new client connects easily to the new server, but latency is so bad that it can take 5-15 seconds for any mouse or keyboard action to be seen and implemented on the server. Trying the other Win7 client exhibits the same behavior. Using the new Win7 client to access the previously mentioned servers behaves identically with the other Win7 client--perfectly. Therefore, whatever the problem is, it is associated with the new server.
This problem is not unknown throughout the web world, and I have found both client-based and server-based fixes. Although tried, the client-based fix (changing AutoTuning values) does not work, nor does the server-based fix (disabling task offload).
Any other recommendations?