We have an ESXi server running VMWare. There are 13 machines on the VMServer, one of which is the Active Directory PDC, running Windows Server 2003 R2 Standard Edition SP2. It is running smoothly and is up to date. It had DNS and DHCP on it, and then points out the gateway. Computers can join the domain and users can login to other machines using it as the PDC.
On Saturday one of the machines ("hostN", also Windows Server 2003 R2 Standard Edition SP2) on that nextwork segment and on the same VM host, decided it was time to go off the network.
I can still login to hostN via the VSphere software running on the backup server on the network. The backup server uses the PDC for auth.
For some reason, hostN doesn't want to get a connection - it wont connect to the PDC during boot for AD perms, doesn't recognise the gateway, the DHCP server or the DNS server.
And that's with the IP details set correctly in the network card config. I tried adding a new network card and leaving that as DHCP, but it didn't work either. I'm stumped. The only error message I get during boot of hostN is that a service hasn't started properly. when I read the message it says
Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 5719 Date: 11/06/2013 Time: 12:34:32 PM User: N/A Computer: HOSTN Description: This computer was not able to set up a secure session with a domain controller in domain FDS2 due to the following: The remote procedure call failed. This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
And on the PDC gets:
Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 5805 Date: 11/06/2013 Time: 12:41:01 PM User: N/A Computer: FS1 Description: The session setup from the computer HOSTN failed to authenticate. The following error occurred: Access is denied.
I'm getting the feeling that this is a little deeper than a plain network issue - everything is set up exactly as it should be.
The Gateway is 192.168.0.1 The PDC is at 192.168.0.5 as DNS, DHCP, AD hostN is at 192.168.0.143 (statically assigned with the above values) hostN has a second NIC using DHCP which ends up with a 169.x.x.x address Other computers can connect to the PDC fine. The PDC can ping google. (and has been updated and rebooted). It has a DNS for hostN, it has a DHCP reservation (tried with both NICs via MAC Address) for hostN hostN cannot connect to anything. What the hell? It doesn't make any sense.
I tried removing the computer from the domain, adding it to "WORKGROUP" to add it back to the domain. But instead it will not now join the domain. For some reason the PDC is invisible from the hostN machine? (no pings to it nor the firewall.)
What could I try next?