I have a network i have started to manager i need some assistance with an issue.

I have 3 sites each with their own DC/ one of my sites i suspect i am having a dns issue. I have students on this site that had HOME Drives mapped but as of yesterday the drives dont map[ by \servername\share. If i map via \ipaddress\share they map.

I have checked the local DC and this is what i see in the DNS Event: The DNS server was unable to open Active Directory. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code.

can anyone assist???

3 Spice ups

Please review your event logs for replication problems, ensure that the DC/DNS server can reach the other domain controllers by name amd address, you may need to set the DNS client om that sites DC/DNS server to a DC in another site.

Check the error code referenced I’m the message you posted, that might help.

dcdiag will be a tool you’ll have to use, but I wouldn’t bother until you can get the local DC resolving names in the other sites.

is network connectivity up? Can you ping the DNS server?

Also, do a NSLookup with bot the DNS name, and Ip address.

Connectivity is up i can do an nslookup and ping the DNS server

dcdiag /test:replications

While you may be able to salvage this setup, I would probably just recommend demoting this DC and Re-promoting it instead.

If the DC has any FSMO roles, I would force the demotion, seize the roles from another DC, then repro more the DC.

It has no FSMO roles on it so should i just demote and re-promote it?

Do i need to do any metadata cleanup?

Should you? All I can say is that if I was in your position, that is what I would do. It may not be the text book answer, but I see it as the most expedient.

Because you’re not properly replicating/communicating with the other DCs the standard demotion will probably not go smoothly and you’ll be forced to use a /forceremoval with the dcpromo - I would disconnect it from the network before doing that, just to be safe.

Because it a) won’t be on the network or b) will be, but will be a forced removal, you will have to do the metadata cleanup on one of the other DCs. Here’s an excellent reference for the procedure: http://www.petri.co.il/delete_failed_dcs_from_ad.htm

1 Spice up