Windows 7 or Windows Server 2008 R2 fails to respond to an SMB1 oplock break on a stream file

Van toepassing: Windows 7 ProfessionalWindows 7 UltimateWindows 7 Service Pack 1

Symptoms


Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1 clients that are configured for SMB1 don't respond to oplock break requests on stream files. This causes file access problems and application issues. A stream file is identified by the "file:stream" notation, as in the following example: 

f1:s1
Because Windows Server platforms do not support oplocks on stream files, this problem occurs only during a connection attempt to a non-Microsoft SMB product that does support oplocks on stream files over SMB1. 

This issue does not occur when you're using SMB2, the default Server Message Block (SMB) protocol that's negotiated by Windows 7 and Windows Server 2008 R2). Additionally, this problem does not occur with Windows clients that natively use SMB1, such as Windows XP and Windows Server 2003.

Cause


This problem occurs because the Windows 7 and Windows Server 2008 R2 SMB1 client does not respond correctly to an oplock break request on a stream file. 

Resolution


There is no resolution for this issue for Windows 7 and Windows Server 2008 R2 clients. To work around this issue, re-enable support for SMB2. SMB2 does not trigger this issue.

Microsoft was made aware of this issue after mainstream support for Windows 7 and Windows Server 2008 R2 had already ended. Only security-related hotfixes are being released by Microsoft for these platforms. For more information, see Microsoft Support Lifecycle.