UNC-Hardening Fileserver

Mutual Authentication
If the fully-patched Windows 7 client, ADSWK7, requests file share access to Windows Sever 2003 server “ADSFP01” and that request includes “RequireMutualAuthentication=1”, this request must use Kerberos authentication since NTLM is not supported for mutual authentication by default (Windows Server 2008 R2 supports additional Security Support Providers, SSPs, that could provide mutual authentication for other auth types). Assuming the SMB connect request communication includes Kerberos auth for the user, the connection to the file share should be successful.
This setting seems to result in the same behavior whether the destination server SMB share is patched or not or is Windows Server 2003 or a newer OS version.

Integrity
If the fully-patched Windows 7 client, ADSWK7, requests file share access to Windows Sever 2003 server “ADSFP01” and that request includes “RequireIntegrity =1”, this request requires SMB signing for the SMB communication for this session. However, SMB v1 doesn’t support per session SMB signing, SMB v2 does. Windows 2003 R2 and earlier only support SMB v1. This means that if there is an existing SMB (v1) connection to a share on the server that doesn’t require integrity, this secondary request to another file share will fail and the client will not be able to connect to the new file share.
This setting may cause issues when clients connect to a SMB share with RequireIntegrity=1. The workaround is to set Windows Server 2003 servers to always require security signatures which enforces SMB signing for all SMB connections.