Knowledge Base

Event ID 56 Cites W32Time as Source and Reports That the DC Returned an Incorrectly Signed Time Stamp

Article ID: 294834

Article Last Modified on 1/31/2007

APPLIES TO

Microsoft Windows 2000 Service Pack 1
Microsoft Windows 2000 Service Pack 2
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Service Pack 1
Microsoft Windows 2000 Service Pack 2

This article was previously published under Q294834

SYMPTOMS

When you try to gain access to resources in a trusted domain, you may receive an "Access Denied" error message and the System Event log may display the following information:

Event Type: Warning
Event Source: W32time
Event Category: None
Event ID: 56
Date:
Time:
User: N/A
Computer:
Description:
The Domain Controller domain controller name in domain name returned an incorrectly signed time stamp. If this DC is from the machine's parent domain, then the trust link between the domains may be broken and must be fixed. If the DC is from this machine's own domain, then the machine password for this machine is incorrect and should be corrected.

CAUSE

This behavior can occur if a client computer in the trusting domain performs a secure time synchronization with a domain controller (DC) in the trusted domain by using an expired trust password.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:

   Date         Time   Version        Size     File name
   -----------------------------------------------------------------
   18-Jul-2001  20:55  5.0.2195.3858  355,088  Advapi32.dll
   18-Jul-2001  20:55  5.0.2195.3649  135,440  Dnsapi.dll
   18-Jul-2001  20:55  5.0.2195.3649   94,992  Dnsrslvr.dll
   18-Jul-2001  20:55  5.0.2195.3817  142,608  Kdcsvc.dll
   17-Jul-2001  20:08  5.0.2195.3872  197,392  Kerberos.dll
   26-Jun-2001  23:16  5.0.2195.3781   69,456  Ksecdd.sys
   17-Jul-2001  19:52  5.0.2195.3870  501,520  Lsasrv.dll 128-bit
   17-Jul-2001  19:52  5.0.2195.3870  501,520  Lsasrv.dll 56-bit
   17-Jul-2001  19:52  5.0.2195.3870   33,552  Lsass.exe
   18-Jul-2001  20:55  5.0.2195.3776  306,448  Netapi32.dll
   18-Jul-2001  20:55  5.0.2195.3776  357,648  Netlogon.dll
   18-Jul-2001  20:55  5.0.2195.3868  909,072  Ntdsa.dll
   18-Jul-2001  20:55  5.0.2195.3868  382,224  Samsrv.dll
   18-Jul-2001  20:55  5.0.2195.3781  128,784  Scecli.dll
   18-Jul-2001  20:55  5.0.2195.3649  299,792  Scesrv.dll
   18-Jul-2001  20:55  5.0.2195.3649   48,400  W32time.dll
   29-May-2001  12:26  5.0.2195.3649   56,080  W32tm.exe

Apply this hotfix to all domains, and to all domain controllers within the domain, if you experience this problem.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Windows 2000. This problem was first corrected in Windows 2000 Service Pack 3.

MORE INFORMATION

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173 Datacenter Program and Windows 2000 Datacenter Server Product

For additional information on how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:

296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Additional query words: kbDirServices

Keywords: kbbug kbfix kbwin2000presp3fix kbqfe kbwin2000sp3fix kbdirservices kbhotfixserver KB294834

Microsoft KB Archive/294834

Contents