July 27, 2008 - 2 Comments

Windows Server 2008 or Vista - Large file copy from a network share and network freeze

If you try to copy a large file from a network share sometimes Windows Server 2008 or Vista freezes the network connection although you have Service Pack 1 installed. After that you have to reboot in order to get your network connection to work.

You can find some discussions without any solution. I had the same problem and this workaround works for me:

1. Never click at the "More information" button which is calculating the speed. Since I don't look at the information even file copies of 26GB are working - up and down.

2. Copy large files one by one using the crtl+c key combination.

3. Don't drag and drop files or folders.

I hope it works for somebody too.

Get updates

Google+

Get SharePoint tutorial updates by RSS feed.

Get SharePoint tutorial updates by Twitter

Follow @sptutorial

Installing SharePoint Server 2010 on Windows Server 2008 R2 and SQL Server 2008 R2 - Part 2: Windows Server 2008 R2 software requirements Installing SharePoint Server 2010 on Windows Server 2008 R2 and SQL Server 2008 R2 - Part 7: SQL Server 2008 R2 installation and configuration Installing SharePoint Server 2010 on Windows Server 2008 R2 and SQL Server 2008 R2 - Part 3: Windows Server 2008 R2 configuration Installing SharePoint Server 2010 on Windows Server 2008 R2 and SQL Server 2008 R2 - Part 6: SQL Server 2008 R2 software requirements

Comments (2) -

8/21/2009 10:59:04 PM #

Do you happen to have any idea what the difference between Ctrl+C and dragging a file is?  I also have tried using robocopy, and i get it to freeze, requiring a hard reset of my entire box.  This is the same thing that happens on my Vista laptop where I'm trying to copy an 18 gig VHD file to a server.

I tried disabling auto-tuning, and then heuristics automatically forced it back on again. I forced of heuristics, and it got 87% of the way through, then froze my host, requiring a hard reset.

I'm not superstitious, and I'm sure you're not either, so can you perahps offer some kind of reasoning behind why you think a Ctrl+C might operate differently? I mean, are there different api methods called in these cases?  Even robocopy failed me :/ I had to resort to using 7zip to chop it up into 4 gig files to move it.  Not a fun afternoon.

dave Reply

8/22/2009 1:22:01 PM #

I have to admit that I don't know if there is a different API call... maybe it was just coincidence that the described steps worked for me.

Last month I had trouble again since I had to install Windows Server 2008 R2 Release Candidate and the copy process worked but only with 8MB per second. After updating the network driver it didn't change anything and some days later I download with around 40MB.
Yesterday I upgraded to RTM and I'm wondering what will happen this week. Maybe it has nothing to do with the client...

Andreas Glaser Reply