Article ID: 821240
Article Last Modified on 2/20/2007
APPLIES TO
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Datacenter Server
- Microsoft Windows 2000 Service Pack 2
- Microsoft Windows 2000 Service Pack 3
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Service Pack 1
- Microsoft Windows 2000 Service Pack 2
- Microsoft Windows 2000 Service Pack 3
SYMPTOMS
If a domain trust in the trusted domain automatically resets, the next time a trusting Windows 2000 domain controller tries to update the password, the authenticating domain controller in the trusted domain may log an event ID 5722 event message similar to the following event message:
Event Source: NETLOGON Event Category: None Event ID: 5722 Date: 05/06/yyyy Time: 1:35:21 PM User: N/A Computer: TRUSTED_DC Description: The session setup from the computer TRUSTING_DC failed to authenticate. The name(s) of the account(s) referenced in the security database is TRUSTING_DOMAIN$. The following error occurred: Access is denied. Data: 0000: 22 00 00 c0 "..A
This problem typically occurs when a Windows NT 4.0 domain trusts a Windows 2000 domain. For details about related netlogon logging, see the "More Information" section of this article.
CAUSE
Under these conditions, Event ID 5722 event messages that the trusting domain controller logs are only noise because the trusts are operational. When you reset the trust passwords manually, they automatically reset again within a day (plus a random interval).
The Windows NT 4.0 domain sends the new password to the Windows 2000 domain, and the new password does not work. The Windows NT 4.0 domain then sends the old password. The old password succeeds. Windows 2000 logs the event message because the initially presented password did not work.
RESOLUTION
Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
You must restart your computer after you apply this hotfix.
Hotfix Replacement Information
This hotfix does not replace any other hotfixes.
File Information
The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ---------------------------------------------------------- 16-Jul-2003 06:56 5.0.2195.6748 124,688 Adsldp.dll 16-Jul-2003 06:56 5.0.2195.6748 132,368 Adsldpc.dll 16-Jul-2003 06:56 5.0.2195.6748 63,760 Adsmsext.dll 16-Jul-2003 06:56 5.0.2195.6761 381,712 Advapi32.dll 16-Jul-2003 06:56 5.0.2195.6753 69,392 Browser.dll 16-Jul-2003 06:56 5.0.2195.6680 134,928 Dnsapi.dll 16-Jul-2003 06:56 5.0.2195.6780 96,528 Dnsrslvr.dll 16-Jul-2003 06:56 5.0.2195.6753 47,376 Eventlog.dll 16-Jul-2003 06:56 5.0.2195.6759 148,240 Kdcsvc.dll 18-Jun-2003 06:43 5.0.2195.6758 205,072 Kerberos.dll 26-Mar-2003 10:37 5.0.2195.6695 71,888 Dsecdd.sys 13-Jul-2003 17:17 5.0.2195.6779 509,712 Lsasrv.dll 13-Jul-2003 17:17 5.0.2195.6779 33,552 Lsass.exe 15-Jul-2003 08:39 5.0.2195.6782 109,840 Msv1_0.dll 16-Jul-2003 06:56 5.0.2195.6601 311,568 Netapi32.dll 16-Jul-2003 06:56 5.0.2195.6783 360,720 Netlogon.dll 16-Jul-2003 06:56 5.0.2195.6781 931,088 Ntdsa.dll 16-Jul-2003 06:56 5.0.2195.6742 392,464 Samsrv.dll 16-Jul-2003 06:56 5.0.2195.6737 131,344 Scecli.dll 16-Jul-2003 06:56 5.0.2195.6737 306,448 Scesrv.dll 15-Jul-2003 11:08 5.0.2195.6776 4,858,368 Sp3res.dll 16-Jul-2003 06:56 5.0.2195.6601 51,472 W32time.dll 16-Aug-2002 02:32 5.0.2195.6601 57,104 W32tm.exe 16-Jul-2003 06:56 5.0.2195.6741 126,224 Wldap32.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Microsoft Windows Server 2003.
MORE INFORMATION
Sample Netlogon.log Contents
05/06 13:35:21 [SESSION] NetrServerAuthenticate entered: TRUSTING_DC on account TRUSTING_DOMAIN$ (Negot: 1ff) 05/06 13:35:21 [CRITICAL] NetrServerAuthenticate: Bad password 0 for TRUSTING_DC on account TRUSTING_DOMAIN$ 05/06 13:35:21 [CRITICAL] NetrServerAuthenticate: Bad password 1 for TRUSTING_DC on account TRUSTING_DOMAIN$ 05/06 13:35:21 [CRITICAL] NetrServerAuthenticate: Failed to authenticate TRUSTING_DC on account TRUSTING_DOMAIN$ 05/06 13:35:21 [MISC] Eventlog: 5722 (1) "TRUSTING_DC" "TRUSTING_DOMAIN$" 0xc0000022 c0000022 "... 05/06 13:35:24 [SESSION] NetrServerAuthenticate entered: TRUSTING_DC on account TRUSTING_DOMAIN$ (Negot: 1ff) 05/06 13:35:24 [CRITICAL] NetrServerAuthenticate: Bad password 0 for TRUSTING_DC on account TRUSTING_DOMAIN$ 05/06 13:35:24 [CRITICAL] NetrServerAuthenticate: Bad password 1 for TRUSTING_DC on account TRUSTING_DOMAIN$ 05/06 13:35:24 [SESSION] NetrServerAuthenticate returns Success: TRUSTING_DC on account TRUSTING_DOMAIN$ (Negot: 1ff) 05/06 13:35:25 [SESSION] NetrServerPasswordSet: Comp=TRUSTING_DC Acc=TRUSTING_DOMAIN$ Entered 05/06 13:35:25 [SESSION] NetrServerPasswordSet: Comp=TRUSTING_DC Acc=TRUSTING_DOMAIN$ Changing password locally 05/06 13:35:25 [SESSION] Setting Password of '05/06' to: ######## ######## ######## ######## ................ 05/06 13:35:25 [SESSION] Current OWF Password of 'TRUSTING_DOMAIN$' is: ######## ######## ######## ######## ................ 05/06 13:35:25 [SESSION] Previous OWF Text Password of 'TRUSTING_DOMAIN$' is: ######## ######## ######## ######## ................ 05/06 13:35:25 [CHANGELOG] DeltaType AddOrChangeUser (5) SerialNumber: ## ###### Rid: 0x#### Name: 'TRUSTING_DOMAIN$' 05/06 13:35:25 [CHANGELOG] NlSendChangeLogNotification: sent 0 for TRUSTING_DOMAIN$ Rid:0x#### Obj Guid:00000004-0000-0000-0000-000000000000 05/06 13:35:25 [MISC] NlMainLoop: Notification to replicate immediately 05/06 13:35:25 [MISC] NlMainLoop: Notification that trust account added (or changed) TRUSTING_DOMAIN$ 0x#### 4 05/06 13:35:25 [SESSION] NetrServerPasswordSet: Comp=TRUSTING_DC Acc=TRUSTING_DOMAIN$ returns 0x0 05/06 13:35:25 [CHANGELOG] NlSendChangeLogNotification: sent 2 for Sid:S-1-5-21-#########-#########-######### 05/06 13:35:25 [MISC] NlMainLoop: Notification that TDO added or deleted. 05/06 13:35:25 [DOMAIN] Domain thread started 05/06 13:35:25 [DOMAIN] Domain thread started doing update trust list NOTE: The '4' at the end of the 'NlMainLoop: Notification' entry indicates a trusted domain secure channel
For additional information about how hotfix packages are named , click the following article number to view the article in the Microsoft Knowledge Base:
816915 New Naming Schema for Microsoft Windows Hotfix Packages
For additional information about netlogon logging, click the following article number to view the article in the Microsoft Knowledge Base:
109626 Enabling Debug Logging for the Netlogon Service
Additional query words: 5722 trusted PDC
Keywords: kbbug kbfix kbqfe kbwin2000presp5fix kbhotfixserver KB821240
