HiWhen i connect remote desktop to windows 2000 server this connection generates massive traffic from windows 7 to that servernormally from windows xp it is kilobytes but from windows 7 traffic goes to 500-700 kilobytes/s :(What can i do to prevent this?Jarek

Hi Jarek, Maybe because the Remote Desktop version is different. In Windows 7 beta it is 6.1.7000, and in Windows XP it is 6.0.6000. The version in Windows 2000 is similar with it in Windows XP.Arthur Xie - MSFT

Hi Jarek,I am having the same problem with Windows 7 RC connecting to W2000 server. Traffic is huge. Moreover rdpclip process consumes huge amount of CPU resources.

I'm having the same problem.If I try to connect remotely to w2k than the cpu goes up to 100%. Than after a while my win7 loses all network connection. I have to run Repair on the Local Area Connection so I can get online again.

I think I have same problem here.I can connect to all W2k3 terminal server but cant connect to any w2k servers. Remote Desktop just hang at connection before login screen.I decided to wait some time - may be connection to slow - but after this time - my remote computer (domain controller) stop responding at all Connections to domain controller from another computer restores after I closemy Remote DesktopAny fix for this?

Our Cisco 2611xm router has been getting overwhelmed with traffic lately. I was able to determine that part of the problem is Windows 7 RC RDP connecting to Win2k or Win2k3, although it's a little worse with a Win2k connection. When I establish an RDP connection across the Cisco 2611xm to a Win2k server the routers CPU hits and holds at 100%. Connecting to a Win2k3 server averages closer to 95-97% CPU utilization on the router. Al

I'm having the same issue. Large amounts of data and Cisco 7206routers are pegging CPU. On our WAN connections that are using newer HP routers, the issue is not present. Also, this is from a 64-bit Win 7 RC. From a 32-bit RC virtual machine, it did not exhibit the negative behaviour.

Thank God I found this forum. I'm having the same problem with Windows 7 and connecting to a Windows 2K Server. It had me baffled for a while. I would log in, then it would slowly suck up all of the CPU on that server, along with knocking about 15 other users on it off, it would also finally kick me off. I read down the bottom of this thread and Microsoft doesn't seem to be offering any real solutions to it. Rather, I get the feeling that it's being ignored. I've got several servers and hundreds of workstations and I'm certainly not going to upgrade any of them until they find a solution to this problem.

I've found the same issue using Windows 7 RC 32bit connecting into a Windows 2000 server. As a simple workaround, before I establish a connection to a 2000 server: In Remote Desktop Connection, click/expand the "Options". Select the "Local Resources" tab, and uncheck "Clipboard" under "Local devices and resources". This should allow you to remote into the Win2000 box without the RDPClip process pinning the CPU... however, the clipboard-transfer will not be available. John

Thanks John, it seemed to work at first but instead of just slowing down and kicking me out, it just kicked me out. The terrible thing about this is that it kicks everyone out of the server and locks it up. Microsoft knows about this and isn't even addressing the problem, guess they figure its Windows 2000, why worry about it but I'm afraid it's going to bite them in the rear. Thanks for your help.

Hi. I am having the same problem. Running rdp from win7 RC 64bit to windows server 2k. CPU usage goes up to 40-45% (t9600) and bandwidth usage in resource monitor shows up to 50% of 100Mbit link. Even when I change setting on the rdp - disable clipboard, doesn't help. I found somewhere below command might help - tried it to no avail. Any help would be greatly appreciated.netsh interface tcp set global autotuning=disabled