Consider the following scenario:
You have a file server that’s running Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2.
You have a client computer that does not support Server Message Block (SMB) encryption. For example, the computer is running Windows 7 or an earlier version of Windows.
You configure the requirement of security signatures either on the SMB client or on the server.
On the client computer, you set the EnableSecuritySignature value to 1 in the following registry subkey:
On the server, you configure the SMB encryption as a requirement but allow for a fallback by running the following Windows PowerShell commands:
Set-SmbServerConfiguration -EncryptData $true
Set-SmbServerConfiguration -EncryptData -RejectUnencryptedAccess $falseOr, you run the following PowerShell command on the server:
Set-SmbServerConfiguration -RequireSecuritySignature $true
You create an SMB share on the server, and then you try to access the file share from the client computer.
In the scenario, you cannot access the file share.
To resolve this issue, install update rollup 2975719. For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:
2975719 August 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates