Event ID: 5723, 5722, 5805 - A computer can't logon domain

Event ID: 5723, 5722, 5805 - A computer can't logon domain

Situation: A computer can't logon domain with this message: "Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear, contact your system administrator for assistance."
Also the Domain Controller has these event logs:

Event ID: 5805
Description: The session setup from the computer 2284 failed to authenticate. The following error occurred: Access is denied.

Event ID: 5723
Description: The session setup from computer '2284' failed because the security database does not contain a trust account '2284$' referenced by the specified computer. USER ACTION If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. Otherwise, the following steps may be taken to resolve this problem: If '2284$' is a legitimate machine account for the computer '2284', then '2284' should be rejoined to the domain. If '2284$' is a legitimate interdomain trust account, then the trust should be recreated. Otherwise, assuming that '2284$' is not a legitimate account, the following action should be taken on '2284': If '2284' is a Domain Controller, then the trust associated with '2284$' should be deleted. If '2284' is not a Domain Controller, it should be disjoined from the domain.

Event ID: 5722
Description: The session setup from the computer 2284 failed to authenticate. The name(s) of the account(s) referenced in the security database is 2284$. The following error occurred: Access is denied.

Troubleshooting: Followed this link:Event ID 5723

Event ID – 5723 - The session setup from the computer <computer name> failed ...
Event ID: 2011 - Not enough server storage is available to process this ...
www.chicagotech.net/troubleshooting/e...

to remove the computer and rejoin it to the domain. However, that doesn't fix it.After checking the event log and laptop settings, we found the laptop was using 2284$ hostname to access the domain. However, the AD doesn’t have 2284$ as Computer account. We also found the laptop tag # is 2288 instead of 2284. We believed that the laptop 2288 takes HD from laptop tag # 2284. When the laptop joined the domain, it is using 2284$. That is why the laptop doesn’t logon domain.

The resolution is removing the 2284 account from the laptop and re-join to the domain using 2288 account. The 2284 may need to do the same to logon the domain.

Post your questions, comments, feedbacks and suggestions

Contact a consultant