Start -> Control Panel -> Programs -> Turn Windows Features on or off -> Uncheck the box "Remote Differential Compression". Click, OK and then you MUST restart your computer.My lan copies went from 1.3MB/s to 11MB/s on my 100baseT.I can't believe a release candidatewould ship with RDC enabled, making network file copying go so slow on any file server that is not Vista, or Windows 7. (Or wait... I can! Breaking things so they only work with new Microsoft operating systems is the name of your game isn't it?)In theoryRDC sounds impressive if it will workbetween two Windows 7 machines, butit hoses EVERYTHING that isn't RDC capable. If the RTMships with RDC enabled, I feelvery sorry for a lot of the world (NAS servers,*nixservers running SAMBA)waiting for files to copy.Is it really so hard to detect if the remote system supports RDC, andthen decide if the RDC code should be used?^^ Shame on you. I know you guys aren't that stupid, but you think we are. Shame on you.It's this kind of nonsense that keeps giving Microsoft a bad reputation, time and time again.

I've turned off RDC and it made no difference. I've seen other posts about this problem. None of these fixes have helped me. I've disabled TCPIP autotuning, RDC, IPv6, etc. I have 4 computers and an Xbox all mapped to a ReadyNAS NV+. All of the machines run XP Pro except for one machine I just upgraded (totally clean build) to RC1 build #7100. I have run all of the updates. I use this machine exclusively for media so this is a very significant problem in that even small audio files won't play back. I've also tried running with about AV, rolling back the network adapter driver, updating the network adapter driver, etc. Nothing has made a difference. My set up is a Mac Mini, bootcamped, with a brand new disc, clean install of Win7. The machine has 2GB of RAM. I also don't and can't connect with a LAN cable and only use wireless. This shouldn't make any differnce though as I used the exact same set up with XP and had no problem playing VOB files across the network. The network is a GigE Netgear swithc and Ruckus media router. Note that internet download speeds are really fast, this seems limited to Intranet. I've run out of ideas and the news groups all seem to have the same solutions. Judging from the posts I'm clearly not the only one suffering from this problem.

I was wrong. RDC was not the problem. It was just because I rebooted the computer after changing the RDC setting. I turned RDC back on. I am so sorry that had nothing to do with it. Running 7100 it just seems like after a few days or weeks the network file copy will slow way down. I haven't experienced this lately. I'm assuming an auto-update might have fixed it. Thank goodness. That was annoying.

I am wrong again, just a couple days ago I had to reboot my Windows 7 RC because the 100BaseT LAN dropped from around 10MB/sec down to around 1.3MB/sec. I hope they fixed this in the RTM. Something is causing a slow LAN degredation.

Yes. I too am very annoyed and bothered by slow copying to shared drives on a Linux Samba system (smb 3.2.11).I can access my web server running on this system without issue (it checks out a project from subversion in a few seconds) but it takes 10+ minutes to copy the same files to a shared drive. (I get at most 1.3MB/s, but usually in the 200b to 450kb/s range). I should also mention, before installing Windows 7 RTM, I have Vista with the latest hotfixes/SPs without any tinkering and it was much faster. While I have been overall pleased with Windows 7, this slow file copying is almost becoming a nightmare. If they do not release a fiew for this soon, I will reinstall Vista or just go to Linux with a VPC running Vista/7 for non coding activities.

And just to explain why this statement is incorrect, as the poster later found with linear troubleshooting: http://blogs.technet.com/b/askds/archive/2009/06/26/debunking-the-vista-remote-differential-compression-myth.aspxNed Pyle [MSFT] Enterprise Platforms Support - DS

I've also had this problem, but I've noticed that regardless of OS, restarting my Samba service solved my problems. Here's what I've noticed about my particular problem: 1) My shares degrade over time after a reboot. 2) File copy/move or modifying is not only excruciatingly slow on the shares after awhile, but grind my CPUs with DPC load, causing instability and freezing. 3) With mapped network drives, Explorer randomly freezes and slows in general (because of persistent connection). 4) Rebooting my local computer solves the problem. 5) Rebooting my remote system solves the problem. I found the weak link in my setup, and wrote a remote script to only restart the remote Samba service. Now, when I notice a slowdown, I run the script and like magic, all the CPU grind is gone, freezes and slow-downs go away, and file operations on network shares return to their former excellent speeds.