Forst Root Domain Controller Issues

[Xemus]

We had a glitch yesterday in which our forest root DC flatlined. After replacing the motherboard, the server is back up and running. However, during the rebuild process, the second NIC was plugged in, and I believe the DC has been replicated as existing twice in the domain. No other computers are able to access this computer (it is our print server) except Windows 98 machines.
The error I get when I try to connect is "Logon failure: The target account name is incorrect". I can terminal server into the server, but I would like to know if anyone has run accross this or could point me in the right direction.
Thanks in advance. MCSE, A+

 

[GlenJohnson]

What os's can't get there? Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com


"What really happens is trivial in comparison to what could occur."
Robert von Musil (1880-1942); Austrian author.

 

[Xemus]

Windows 2000 and Windows XP machines, which is about 95% of our network. From Win2K, I get the same error, with "System Error 1396 has occured".
Event viewer is showing this on a Windows XP machine.
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server 2K-2$. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (here.LOCAL), and the client realm. Please contact your system administrator.
MCSE, A+

 

[GlenJohnson]

Event ID: 1396
No information found. If you have additional information about this event, please send it to us.
The submitted events will be forwarded to Altair Technologies consultants for analysis.
We recommend however, that you first check the EventID.Net Processing Queue to see if the event was already submitted by another contributor. This is what I found on

http://www.eventid.com

Strange that they wouldn't know about it.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/system_error_codes.asp

Shows system logon error. 1396 Logon Failure: The target account name is incorrect. ERROR_WRONG_TARGET_NAME
Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com


"What really happens is trivial in comparison to what could occur."
Robert von Musil (1880-1942); Austrian author.

 

[Xemus]

Problem solved. We did a non-authoritative restore (in safe mode, directory services restore mode) on the DC and it's back to funtioning like it was. Thanks. MCSE, A+