Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Win2k AD Netlogon Error

Status
Not open for further replies.

simonigor

MIS
Jan 19, 2003
31
PH
Hi to all!

Our setup is previously NT4 then i upgraded it to Win2k AD.
we have a trust going to our branch domain which is also win2k AD(they were the first to implement AD).

the branch domain is xyz.abc.com(Win2k)=xyz(NT4)
our domain is abc.com(Win2k)=lfc(NT4)

i am now getting event id 5722(Netlogon error)on my domain controller.

Source: NETLOGON
Event ID: 5722
Description:
The session setup from the computer ODIN(a win2k dc on the branch domain) failed to authenticate. The name of the account referenced in the security database is xyz$.
The following error occured:
Access is denied.

 
NETDOM /RESET <servername>

The NetLogon service on the PDC logs this error message when the password is not synchronized between the COMputer and PDC. When a workstation joins the domain, a trust is created with the PDC along with a secured channel password on both machines. This password, by default, automatically changes every seven days. If for some reason the process of password change fails, this error will be generated. One may have to reset the machine account password (can be done with the NETDOM utility - from NT Resource Kit or for Windows 2000 from the Support Tools ). The password change is initiated by the workstation. This change can be disabled by altering the Registry (DisablePasswordChange on the workstation or RefusePassowrdChange on the server). See Q154501
This event may also mean that the computer does not have an account in the domain or has been deleted.

This event also occurs under Windows 2000, even though Microsoft does not mention it in the Q articles. In a mixed-mode windows 2000 domain, a standalone server may lose machine-password synchronization. In this case, if you are on mission-critical systems and do not want to remove and rejoin the COMputer to the domain, try the Win2000 ResKit utility NETDOM as follows:

NETDOM /RESET <servername>

The result should be succesful and the message contains the name of the DC the operation was processed with. This should resolve the problem.

greetz

nootgevallen

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top