- 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:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanManWorkstation\Parameters
- 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 $trueOr, you run the following PowerShell command on the server:
Set-SmbServerConfiguration -EncryptData -RejectUnencryptedAccess $falseSet-SmbServerConfiguration -RequireSecuritySignature $true
- You create an SMB share on the server, and then you try to access the file share from the client computer.
Article ID: 2976995 - Last Review: 13 Oct 2014 - Revision: 1