Windows Server Reboots During Large File Copy

• Windows Server Reboot Command Line
• Windows Server Reboots During Large File Copy To Usb

Hello all,I am running windows server 2012 as dc with 2 clients connected both running win7 pro.This is a new setup (both server and clients) about 2 months old. I'm having major issues myself when Win 7 clients try to access files concurrently on Server 2012 R2 - Wireshark shows lots of SMB errors before the file eventually opens. Same files on a 2008 box open instantaneously. When I try accessing files from my Win 8 box, files open as quickly as they always have, Wireshark doesn't show nearly as many errors. Tried on physical Server 2012 box, as well as a VM with no anti-virus on it. Yet if a person opens files on their own and not concurrently, Windows 7 is pretty snappy, if not as fast as it was with 2008.My conclusion is that Server 2012's SMB implementation is a bit screwy and isn't handling SMB2 clients very well, or at least Windows 7's SMB client. I'm having major issues myself when Win 7 clients try to access files concurrently on Server 2012 R2 - Wireshark shows lots of SMB errors before the file eventually opens.

Same files on a 2008 box open instantaneously. When I try accessing files from my Win 8 box, files open as quickly as they always have, Wireshark doesn't show nearly as many errors. Tried on physical Server 2012 box, as well as a VM with no anti-virus on it.

Windows Server Reboot Command Line

Yet if a person opens files on their own and not concurrently, Windows 7 is pretty snappy, if not as fast as it was with 2008.My conclusion is that Server 2012's SMB implementation is a bit screwy and isn't handling SMB2 clients very well, or at least Windows 7's SMB client.Hey,Thanks for the reply. I just tried to disable SMB1 on the server through the powershell and it seems to be running normal now.

Windows Server Reboots During Large File Copy To Usb

But i think the speed is not yet optimal. There have been similar discussions on Edugeek already and the SMB does appear to be the source of the problem, but unfortunately it's tightly integrated with the OS and isn't something you can change.2008 R2 and Windows 7 will work perfectly as they use the same SMB version, whereas issues do seem to creep in as 2012 and Windows 8 use a newer version.In some cases, you can run 2008 R2 and 2012/2012 R2 in the same domain, with your file shares hosted on 2008 R2. It's a good compromise until Microsoft properly fix the issue.