Time synchronization may not work properly on domain controllers on the same site as the child domain PDC (297025)


The information in this article applies to:

  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2
This article was previously published under Q297025
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

If you have a Windows 2000 Active Directory forest with a parent domain and a child domain, the default time-synchronization mechanism may not work if a domain controller in the child domain is used for synchronization because it is closest, even though the parent domain controller is available for synchronization.

CAUSE

In this configuration, the domain controller to be used for time synchronization returns inconsistent data. The following items are returned:
  • The ID of the closest domain controller in the child domain to be used for synchronization
  • The name of the parent domain (instead of the name of the local domain, which is specified as a NULL)

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For more 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 P1 version of this P2 has the file attributes (or later file attributes) 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
   -----------------------------------------------------------------
   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

WORKAROUND

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

This problem is specific to time synchronization that is based on domain hierarchy (type NT5DS) and does not affect the synchronization from a manually configured source (type NTP). You can enable NTP time synchronization by setting the registry values under this registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

For more information about these registry values, click the following article number to view the article in the Microsoft Knowledge Base:

223184 Registry entries for the W32Time service

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows 2000 Service Pack 3.

MORE INFORMATION

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

249149 Installing Microsoft Windows 2000 and Windows 2000 hotfixes

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

265173 The Datacenter program and Windows 2000 Datacenter Server product

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

296861 How to install multiple Windows updates or hotfixes with only one reboot

Modification Type:MinorLast Reviewed:2/22/2006
Keywords:kbHotfixServer kbQFE kbbug kbDirServices kbfix kbWin2000PreSP3Fix kbWin2000sp3fix KB297025
©2004 Microsoft Corporation. All rights reserved.