Windows Server 2012 R2: Which version of the SMB protocol (SMB 1.0, SMB 2.0, SMB 2.1, SMB 3.0 or SMB 3.02) are you using?
Each version of Windows uses a different SMB version.
This may stop logon scripts working.
Powershell Commands to find SMB version
Use the Get-SmbConnection command – look at the “Dialect” used.
FileServ2 can use version 3.02. That means that both the client and the server support the latest version of the SMB protocol
Server 2012 – uses SMB Version 3.02 (but not SMB 1 by default)
Windows XP talks SMB 1.0 and that’s it. If this is not offered by the server (file server or domain controller) we have a problem. Now if you installed new Windows Server 2012 R2 servers they do not deploy the SMB 1.0 feature by default. If you upgraded from Windows 2008 R2 (perhaps even over Windows 2012) to get to Windows 2008 (R2) this feature kept in place. Other wise you’ll need to make sure SMB 1.0 is installed, it often (always?) is. Just check.
However there is a big change between Windows Server 2008 R2/Windows 2012. The LanmanServer service has a dependency set to SMB 2.0 and no longer to SMB 1.0
So we need to change that on Windows 2012 R2 to support Windows XP. We can do this in the registry. Navigate to
- Change SamSS Srv2 to SamSS Srv
- Restart the Server (Lanmanserver) service (it will restart the dependent services like netlogon, DFS Namespace, .. as well)
You’re XP clients should be able to authenticate again. You can test this by navigating to \\domaincontroller\Netlogon on a XP client. This should succeed.