Unable to login to DC and DCDIAG errors

After restarting our primary DC, we are not able to login to the server with Domain Admin account. From a second DC, DCDIAG gives the following error (Windows Svr 2008):
         Role Schema Owner = CN=NTDS Settings,CN=LEASVRDCO02,CN=Servers,CN=Defa
lt-First-Site-Name,CN=Sites,CN=Configuration,DC=LEALGROUP,DC=LOCAL
         [LEASVRDCO02] DsBindWithSpnEx() failed with error -2146893022,
         The target principal name is incorrect..
         Warning: LEASVRDCO02 is the Schema Owner, but is not responding to DS
         RPC Bind.
         [LEASVRDCO02] LDAP bind failed with error 8341,
         A directory service error has occurred..
         Warning: LEASVRDCO02 is the Schema Owner, but is not responding to
         LDAP Bind.
         Role Domain Owner = CN=NTDS Settings,CN=LEASVRDCO02,CN=Servers,CN=Defa
lt-First-Site-Name,CN=Sites,CN=Configuration,DC=LEALGROUP,DC=LOCAL
         Warning: LEASVRDCO02 is the Domain Owner, but is not responding to DS
         RPC Bind.
         Warning: LEASVRDCO02 is the Domain Owner, but is not responding to
         LDAP Bind.
         Role PDC Owner = CN=NTDS Settings,CN=LEASVRDCO02,CN=Servers,CN=Default
First-Site-Name,CN=Sites,CN=Configuration,DC=LEALGROUP,DC=LOCAL
         Warning: LEASVRDCO02 is the PDC Owner, but is not responding to DS RPC
         Bind.
         Warning: LEASVRDCO02 is the PDC Owner, but is not responding to LDAP
         Bind.
         Role Rid Owner = CN=NTDS Settings,CN=LEASVRDCO02,CN=Servers,CN=Default
First-Site-Name,CN=Sites,CN=Configuration,DC=LEALGROUP,DC=LOCAL
         Warning: LEASVRDCO02 is the Rid Owner, but is not responding to DS RPC
         Bind.
         Warning: LEASVRDCO02 is the Rid Owner, but is not responding to LDAP
         Bind.
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=LEASVRDCO02,CN=
ervers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=LEALGROUP,DC=LOC
L
         Warning: LEASVRDCO02 is the Infrastructure Update Owner, but is not
         responding to DS RPC Bind.
         Warning: LEASVRDCO02 is the Infrastructure Update Owner, but is not
         responding to LDAP Bind.
LealITAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
LealITConnect With a Mentor Author Commented:
The solutions above were of no help. We resolved our issue by having to seize the FSMO roles as per the article below.

http://www.petri.co.il/seizing_fsmo_roles.htm#
0
 
VirastaRUC Tech Consultant Commented:
Hi,

Check this..similar kind of scenario

Replication between two DC's is broken during 5 month, how to restore it?
http://social.technet.microsoft.com/Forums/windowsserver/en-US/bb0c1b17-ffff-4cbc-b33e-7f85b0ebdbd3/replication-between-two-dcs-is-broken-during-5-month-how-to-restore-it

Replication Issue: The target principal name is incorrect
http://www.experts-exchange.com/Networking/Windows_Networking/Q_22447953.html

Hope that helps :)
0
 
LealITAuthor Commented:
This was the only solution that worked for us.
0
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.