Emergency! Can't logon to DC!

Hi all,

I have a massive problem - users are no longer able to logon to the domain, and I can no longer log on to the primary DC!

One particular error is weird:

Event Type:      Error
Event Source:      NTDS Replication
Event Category:      DS RPC Client
Event ID:      2087
Date:            11/02/2009
Time:            12:42:55 PM
Computer:      DOMAIN-BKP-SVR-1
Active Directory could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources.
Source domain controller:
Failing DNS host name:
NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur.  To log all individual failure events, set the following diagnostics registry value to 1:
Registry Path:
HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client
User Action:
 1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498.
 2) Confirm that the source domain controller is running Active directory and is accessible on the network by typing "net view \\<source DC name>" or "ping <source DC name>".
 3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on http://www.microsoft.com/dns 
  dcdiag /test:dns
 4) Verify that that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows:
  dcdiag /test:dns
 5) For further analysis of DNS error failures see KB 824449:
Additional Data
Error value:
 11004 The requested name is valid, but no data of the requested type was found.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The following DC

Source domain controller:

Has been gone from the domain for over a year? Should I remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498?

Who is Participating?
ChiefITConnect With a Mentor Commented:
How are things progressing?

Removing the metadata of any servers that no longer exist is a good idea. However, you should still be able to boot to DC1.

How many DCs do you currently have that can log onto, and what do your backups look like?

You might consider disconnecting DC1 from the LAN, then moving the FSMO roles to DC2 until we can fix DC1.
Mike KlineConnect With a Mentor Commented:
More on your error here
If domain-server1 has been gone from the domain for a year and you still see traces of it in AD then yes a metadata cleanup is a good idea.
That 216498 article is how to do it.
Daniel Petri also has directions here:
It is 2am here so I'm going to get some sleep but some of the guys from Europe will be on soon to help.  I'll be back in a few hours.
Chris HudsonConnect With a Mentor Cloud Security ArchitectCommented:
If the DC "domain-server1 " is no longer there you should do metadata cleanup and remove that server.
Do you have any additional DC in which you can login??
login to any of the client with local admin credentials and run following commands
nslookup>set q=srv
>_ldap._tcp.<FQDN of domain Name>
>_kerberos._tcp.<FQDN of domain Name>
>_gc._tcp..<FQDN of domain Name>
The above command should give the IPs of all Ur DCs
If it fails then it's DNS issue.Point to another DNS and check same thing
let me know the status aftethis check

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Chris HudsonCloud Security ArchitectCommented:
http://support.microsoft.com/kb/216498 --->For metadata cleanup
the-wavesAuthor Commented:
This is now looking pretty good - will award points at end of week if everything is OK.
the-wavesAuthor Commented:
It's all looking good - phew!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.