From scratch and migrated over
From scratch and migrated over
Researching this issue, I wonder if it has anything to do with the SMB protocol?
Windows 7 and 2008 R2 uses SMB 2.1
Windows 8 and 2012 uses SMB 3.0
And Windows 8.1 and 2012 R2 uses SMB 3.02
I bet this is why we're seeing it on 2012, but not for those of you who've upgraded to 2012 R2.
If I'm right, it would be interesting to see if Windows 8 (with a long uptime), suffers from the same problem if it were used as a print server or a file server for a limited number of users.
This happened to me today and it always seems to be on a Friday between 12 and 2pm! Nothing in the logs.
Touch wood, I have a pair of 2012 file servers in a DFS-R mirror, these were in-place updated from 2008 R2 to get de-dupe support - they haven't done this to me. Just got my 2012 R2 licenses in to VLSC so I can upgrade them easily, but wouldn't fancy it happening before they're done.
Did an upgrade a few days ago to Server 2012 R2 and its done the same 2x since - so no luck there
Built a new server and using DFS-R to replicate data over before switching over the name space.
Weird issue to be sure!
I must admit, it does put a big downer on deploying 2012 or 2012 R2 Servers until Microsoft fix this issue!
what's the client os?
Running Windows 7 and Windows 8 (not yet 8.1) here.
The following KB article might be of some use if it is SMB-related however.
For windows 7, have you installed the the updates recommended in this article: An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1
For Windows 8 server 2012 have you installed the latest Cumulative Updates?
For windows 7 here is a List of currently available hotfixes for the File Services technologies in Windows Server 2008 and in Windows Server 2008 R2 probably worth deploying them to your machines.
Here is an interesting hotfix that contains euphamisms that gernerally mean "it completely stops working properly" for Windows 2012 machines.... oddly it describes that the problem is resolved by a reboot of the server... yet the update only contains new versions of client side components... might be worth a shot on your windows 8 / 2012 machines. Hotfix corrects SMB error codes that differ from SMB protocol documentation in Windows 8 and Windows Server 2012
Last edited by psydii; 1st December 2013 at 10:13 PM.
For 2012, SRV2.sys contains the SMB 3.x server code as well as that for SMB2.x. It was quite late in the development cycle that SMB 2.2 became SMB 3.0. If there is a bug in the smb 3 code that caused the server component to die... then SMB 2 capabilities die with it.
Last edited by psydii; 1st December 2013 at 10:16 PM.
Well today we had our 2012 r2 server stop letting shares be accessed, or if they could be accessed taking 5-10 mins. This was both through unc path and ip address. Has anyone else had anything similar on R2 and has anyone found a fix as a reboot isn't really good enough for a server os!!
Happened again today seems to be once a week. I wondering if it could be anything to do with WSUS. I'm just about to dive into some logs.
There are currently 2 users browsing this thread. (0 members and 2 guests)