I have the exact same problem ((when copying files from my 2003 server to my win 7 ult)) as the guy in this post http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/0488557f-f692-48c6-8ab8-48c678827dc3 He was able to resolve his issue by making some "unknown registry changes" on his win 7 clients but i am unable to replicate his change. Here is the error I am getting: http://mss.www.idnet.com/copyerror2.PNG. The error only occurs when copying files that are usually over 20+ Meg from the 2003 server to the client. I can copy files from the client to the 2003 server successfully and to and from any other machines on the network (xp, vista, without problems). The issue only happens when I go from the 2003 server to the window 7 ult client. Server : win 2003 SP1 std Client : Win 7 ult Wireless going through DGN2000 netgear ( i have tried 2 other wirless access points and both give same error) No other events are logged in the system or event logs of the server or client I have tried: 1. netsh interface tcp set global autotuninglevel=disabled 2. Click Start – Control Panel – Programs – Trun Windows features on or off - Uncheck “Remote Differential Compression” and click OK. Reboot 3. All drivers are up to date 4. I have checked the article http://support.microsoft.com/kb/330174 (suggested in another post) and I don’t think this will resolve the issue because if I copy the large file from another computer to my win 7 machine over wifi it works just fine, i only receive the error when i try to copy the files off of my win 2003 server to my win 7 machine over wifi. 5. If i reboot the server I can usually copy 1 or 2 large files over before i start getting the error. Any help would be appreciated Thanks Andy

Hi, Based on my research, I would like to suggest the following: 1. Please try a wired connection on the network and see how it works. 2. If this is a domain environment, please also check the network connectivity between the DC and this Windows 7 client. 3. Boot the Windows 7 computer to Clean Boot environment to check the issue: How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7 4. Ensure the Windows 2003 Server and the Windows 7 client are all up-to-date. Hope this helps. Thanks. Nicholas Li - MSFT