Recently we had a client who diligently updated their 2012 R2 DC’s to U1 as part of their normal patching cycle – and found afterwards that their 2003 servers were experiencing some “odd” behaviour.
After having a look, sure enough, networking was fine, RPC was fine, all services were fine, but when trying to connect to netlogon, the error: “The specified network name is no longer available” was thrown.
A short amount of searching later, turned up this article:
http://workinghardinit.wordpress.com/2014/04/25/windows-xp-clients-cannot-execute-logon-scripts-against-a-windows-server-2012-r2-domain-controller-workaround/
Our experience of the issue was slightly different – in that it did not occur when the 2012 R2 DC’s were first upgraded, only when U1 was applied, in addition, the 2003 clients could connect to the file server which was running 2012 R2 (not u1) without any issues, but had trouble to any file shares on 2012 R2 u1 servers. It is also worth noting that all of these servers had been upgraded from 2008 R2/2012 – none were fresh builds.
The registry change documented in the article worked and all was good with the world. In this instance, the client only had a small number of servers still running 2003 – and this has given them a bit of a hurry up to sort out the apps on these servers.
*edit 24/11/2015 * – The original article seems to have become unavailable… so the changes are:
- Install the feature “SMB 1.0/CIFS file sharing support”
- Navigate HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer
- Edit DependOnService and change
- SamSS Srv2
- to
- SamSS Srv Srv2
- Restart