DC Stopped Working No DNS and No AD Changes
Posted on 2009-04-16
we have 4 DCs. the one that contains all the FSMO roles has stopped working properly.
it no longer works as a DNS and when i add a machine to the domain it no longer shows in the computers OU.
if i do an nslookup on the troubled DC that is having trouble it will provide a correct response from itself. however, if i do an nslookup on a workstation, it will return "DNS request timed out" and then resolve to the secondary DC which will return the correct response.
if i attempt to add a machine to the domain using the troubled DC it will prompt me for authentication and then respond with "the network path was not found". but, if i point the workstation to another DC it add the macine to AD and that will be propagated to the other 2 DCs, but not to the troubled DC.
i can ping the troubled DC just fine.