On a Microsoft Windows domain controller, the following event is logged in the system log:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5722
The session setup from the computer ComputerName failed to
authenticate. The name of the account referenced in the
security database is AccountName$.
The following error occurred:
Access is denied.
In a Microsoft Windows domain, starting with Windows 2000, a discrete communication channel helps provide a more secure communication path between the domain controller and the member servers or workstations. This channel is known as a secure channel
. When you join a computer to a domain, a computer account is created, and a password is shared between the computer and the domain. By default, this password is changed every 30 days. The secure channel's password is stored together with the computer account on the primary domain controller (PDC). The password is replicated to all replica domain controllers.
Event 5722 is logged in the following scenarios:
- When a computer updates its computer account password with a domain controller, the event is logged in the system log of the authenticating domain controller.
In this scenario, the computer's secure channel with the authenticating domain controller is still valid.
- When you join a computer to a domain by using a name that is already in use by another computer, or when an existing computer account is reset. An existing computer account may be reset by using Active Directory Users and Computers or by using the Netdom.exe utility.
In this scenario, the computer's account password does not match the password on the domain controller, and you cannot set up a secure channel from the original computer to the domain controller.
If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
To resolve this problem, first determine which scenario is the cause of the problem. To do this, follow these steps:
- Note the date and the time that the event was logged in the system log.
- Click Start, point to Programs, point to Resource Kit, and then click Tools Management Console.
- In the console tree, click Tools A to Z.
- In the details pane, click ADSI Editor.
Note ADSI Edit is included with the Windows Support Tools. You can install the Windows Support Tools from the Support\Tools folder of the Windows 2000 Server CD-ROM.
For additional information about how to install the Windows Support Tools for Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:
To install ADSI Edit on computers running Windows Server® 2003 or Windows® XP operating systems, install Windows Server 2003 Support Tools from the Windows Server 2003 product CD or from the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=100114
). For more information about how to install Windows Support Tools from the product CD, see Install Windows Support Tools (http://go.microsoft.com/fwlink/?LinkId=62270
How to install the Windows 2000 Support Tools to a Windows 2000 Server-based computer
On servers running Windows Server 2008 or Windows Server 2008 R2, ADSI Edit is installed when you install the Active Directory Domain Services (AD DS) role to make a server a domain controller. You can also install Windows Server 2008 Remote Server Administration Tools (RSAT) on domain member servers or stand-alone servers. For specific instructions, see Installing or Removing the Remote Server Administration Tools Pack (http://go.microsoft.com/fwlink/?LinkId=143345
To install ADSI Edit on computers running Windows Vista® with Service Pack 1 (SP1) or Windows 7, you must install RSAT. For more information and to download RSAT, see article 941314 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkID=116179
- In ADSI Edit, locate and then right-click the computer that is causing the problem.
- Click Properties.
- In Select which properties to view, click Both.
- In Select a property to view, click PwdLastSet.
- Copy the value that appears in the Value(s) box to the clipboard.
- Click Start, point to Programs, point to Accessories, and then click Calculator.
- On the View menu, click Scientific.
- Click Dec to set the numbering system to decimal.
- Paste the value from the clipboard into Calculator.
- To change the value from decimal to hexadecimal decimal numbering system, click Hex.
- On the Edit menu, click Copy.
- Paste the hexadecimal number from the clipboard to a file in Notepad.
- Count eight characters from the right most character of the hexadecimal string, and then press SPACEBAR.
Note This action splits the hexadecimal string into two hexadecimal strings.
- If the hexadecimal string on the left side contains only seven characters, add a zero to the beginning of the string.
- At a command prompt, type
Nltest /time:RightSideHexadecimalstringLeftSideHexadecimalStringYou will receive output that is similar to the following:
C:\>nltest /time:a25cc370 01c294bc
a25cc370 01c294bc = 11/25/2002 13:55:41
The command completed successfully.
- Note the decoded date and time.
- Check whether the date and time that you noted in step 1 and the decoded date and time that you noted in step 20 match.
- If the date and time that event 5722 was logged and the decoded date and time match, check whether the computer that is causing the problem has a secure channel established with a domain controller by typing the following command at a command prompt:
Nltest /server:ComputerName /sc_query:DomainNameIf the problem computer has a valid secure channel established with a domain controller, you receive output that is similar to the following:
If the problem computer does not have a valid secure channel established with a domain controller, you receive output that is similar to the following:
C:\>Nltest /server:computer1 /sc_query:DomainNameFlags: 30
Trusted DC Name \\homenode1.myhouse.comTrusted DC Connection Status Status = 0 0x0 NERR_SuccessThe command completed successfully.
C:\>nltest /server:machine1 /sc_query:DomainNameFlags: 0
Trusted DC Name
Trusted DC Connection Status Status = 5 0x5 ERROR_ACCESS_DENIEDThe command completed successfully.
If the date and time of event 5722 and the decoded date and time do not match, the problem computer's account password may not match the password that is on the domain controller. This can occur under either of the following circumstances:
- An administrator resets a computer account by using Active Directory Users and Computers or another tool such as Netdom.exe.
- A new computer is joined to the domain by using a name that already exists in the domain.
If Netlogon service logging is turned on for the domain controller, you confirm this scenario by checking for a Netlogon.log entry that is similar to the following:
05/06 13:35:25 [MISC] NlMainLoop: Notification that trust account added (or changed) TRUSTING_DOMAIN$ 0x#### 4
This message is not logged if a computer updates its own computer account password.
To resolve problems that are related to duplicate computer names, rejoin the original computer to the domain.
You can ignore event 5722 if both of the following conditions are true:
- If the date and time of event 5722 and the decoded date and time match.
- A valid secure channel is established between the problem computer and a domain controller.
When both of these conditions are true, event 5722 is logged on the domain controller when the computer tries to authenticate with a domain controller during the computer account update process.
Administrators can also query Active Directory information from any computer in the domain by using Ldp.exe. The version of Ldp.exe that is included in the Windows XP Service Pack 2 Support Tools can also be used to decode the PwdLastSet value.
For additional informationabout Windows XP Service Pack 2 Support Tools, click the following article number to view the article in the Microsoft Knowledge Base:
Windows XP Service Pack 2 Support Tools
You can also use the Windows XP utility W32tm.exe to decode the PwdLastSet value.
For additional information about enabling debug logging , click the following article numbers to view the articles in the Microsoft Knowledge Base:
How to enable user environment debug logging in retail builds of Windows
enabling debug logging for the Net Logon service