The strangest thing has happened.
We have had a server 2012 R2 DC server in play for several months now and initially the XP Pro PC's had no issues with it.
This week all the XP workstations are no longer able to communicate with the server.
DNS is ok, we can ping the server by name and FQDN and get a response and proper resolution.
When calling \\servername we get a permission denied, when calling \\servername\share we get permission denied.
I found one solution that seemed to match our issue and changed the Server2012 VM to a VMXNET3 adapter, but no change.
I suspected a patch issue, but so far have not found any suspect patches. One XP station gets permission denied, another gets "Specified Network Name is No Longer Available" but on both systems DNS resolution is working, there are no Kerberos events logged on workstation or server.
What really has me scratching my head is they can talk to our Server 2012 R2 Server that is a member server just fine.....
Anyone experienced this before? I would like to get it going, but in the meantime we are replacing our XP's systems, but this has put a halt on my data migration as the XP systems need share access so I have to leave most of our shares on the Server 2003 box.
We have the following setup
Server 2012 R2 PDC(FSMO holder) - Virtual on VMware Esxi 5.5
Server 2003 R2 DC - Physical box
Server 2012 R2 - Member Server - WSUS and SharePoint on VMware
All VM's running with the VMXNET3 Adapter
