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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

netlogon error event 5722

Status
Not open for further replies.

bookouri

IS-IT--Management
Feb 23, 2000
1,464
US
I have recently started getting dozens of errors on my PDC stating that :
computer xxxxx failed to authenticate the name of the account reference in the security database is xxxx$ the following error occurred: access is denied..

it is always the same pattern.. the workstation name computer1 is computer1$..???

the workstations seem to have no problem logging on, the only indicator i have that anything is going on is the listing of dozens of errors in my server event log...

i cant find the event id listed by microsoft anywhere and the problem seems to be getting worse.. it began weeks ago with one workstation, then two, now i have a half dozen or so that it happens to...

any suggestions would be appreciated..
 
Check out Microsoft article Q180114. I have experienced the same problem.
CAUSE:
Workstation and stand-alone server computer accounts are mistakenly treated as LanMan backup domain controllers (BDC) by the primary domain controller (PDC). LanMan BDCs are declared as such in a Windows NT domain by creating a special Windows NT global group called servers, creating user accounts that correspond to the computer names of the LanMan BDCs, and placing those user accounts in the servers group.
Authentication with the PDC fails when the accounts in the servers group are actually Windows NT workstations and servers. This is because Windows NT will use the secure channel account password against to authenticate with the PDC. The PDC finds a matching user account in the servers group for the Windows NT system and treats it as a LanMan BDC. During challenge/response authentication, the PDC uses the user account password instead of the secure channel password to authenticate the Windows NT system. This causes the errors noted in the summary.
RESOLUTION
If no LanMan BDCs exist, then remove the servers group and restart the Netlogon service on the PDC.
If LanMan BDCs exist, then remove the user accounts for the Windows NT systems experiencing this problem from the servers group. Restart the Netlogon service on the PDC.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top