J
Jeremy Heymann
Scratching my head on this one.
Have a domain composed of a mix of Server 2012 R2 and Server 2008 R2 systems, with 1 2008R2 DC and two 2012R2 DC's. I recently upgraded one of the DCs to Server 2012R2. Now, I have on 2012R2 member server that can't access that specific server by server name. Other servers can access the upgraded DC, and the member server can access shares on the other servers (including another Server 2012R2 DC).
On this member server:
Ping servername works.
Access \\servername\share doesn't work.
Access \\ipaddress\share does work
I've checked DNS, and it properly translates the name. I tried putting the name in the HOSTS file, no effect. I tried putting the name in the LMHOSTS file, also no effect.
I think this is something due to signing of SMB packets, and there might be some kind of certificate or security protocol issue, but I can't find it.
There aren't any relevant errors in either the system or application logs of either the DC or the member server.
I've seen the posts about disabling the signing, but that doesn't sound like the issue. We are going Windows to Windows, and same version of the OS, so it should work. I haven't been able to find any resources that would help diagnose the specific problem, as opposed to just working around it.
Any help that anyone can provide would be appreciated.
Thank you.
Jeremy Heymann Market Mentor Online
Continue reading...
Have a domain composed of a mix of Server 2012 R2 and Server 2008 R2 systems, with 1 2008R2 DC and two 2012R2 DC's. I recently upgraded one of the DCs to Server 2012R2. Now, I have on 2012R2 member server that can't access that specific server by server name. Other servers can access the upgraded DC, and the member server can access shares on the other servers (including another Server 2012R2 DC).
On this member server:
Ping servername works.
Access \\servername\share doesn't work.
Access \\ipaddress\share does work
I've checked DNS, and it properly translates the name. I tried putting the name in the HOSTS file, no effect. I tried putting the name in the LMHOSTS file, also no effect.
I think this is something due to signing of SMB packets, and there might be some kind of certificate or security protocol issue, but I can't find it.
There aren't any relevant errors in either the system or application logs of either the DC or the member server.
I've seen the posts about disabling the signing, but that doesn't sound like the issue. We are going Windows to Windows, and same version of the OS, so it should work. I haven't been able to find any resources that would help diagnose the specific problem, as opposed to just working around it.
Any help that anyone can provide would be appreciated.
Thank you.
Jeremy Heymann Market Mentor Online
Continue reading...