Disabling SMB2 on Windows Server 2008

While I don't know the specific cause, it appears that the problem has already been noted in EMC circles. According to them, you'll need the newest Celerra release you can get your hands on.

I suspect the core of the problem is that Windows 8 uses SMB2.2, and one of two things is happening:

1. Celerra isn't fully implementing the protocol it negotiates with the Win8 box.
2. Protocol negotiation is failing to come to a correct agreement; perhaps it's suggesting it can do SMB2.2, when in fact it can't and is caught out later.

This is most likely a defect in the directory cache feature that was introduced with Windows Server 2008/SMB2. There are three different caches utilized by the client SMB network redirector if SMB 2.0 is the negotiated protocol. File Information Cache, File Not Found Cache, and Directory Cache.

You may be able to localize this further by only disabling the directory cache on the client.

SMB2 Client Redirector Caches Explained
http://technet.microsoft.com/en-us/library/ff686200%28v=ws.10%29.aspx

You may want to try updating your mrxsmb20.sys on the client, although I would update all of the files in 2473205 on both the clients and the servers.

"STATUS_OBJECT_NAME_NOT_FOUND" error message when you open a newly-created file in a shared folder in Windows 7 or in Windows Server 2008 R2
http://support.microsoft.com/kb/2628582

SMB2 directory cache is not updated correctly if a file is deleted in Windows 7 or in Windows Server 2008 R2
http://support.microsoft.com/kb/2646563

Most recent version:

http://support.microsoft.com/kb/2778834