"Event ID: 64" error message on a computer that is running Windows Server 2003 or Windows XP Professional in a Windows NT 4.0 domain (314345)
The information in this article applies to:
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows XP Professional
This article was previously published under Q314345 IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry
SYMPTOMS On a Microsoft Windows Server 2003-based or a Microsoft Windows XP Professional-based computer that is a member of a
Microsoft Windows NT 4.0-based domain, you may receive the following event in
the System event log: Source: W32Time Type:
Warning Event ID: 64 Description: Because of repeated network
problems, the time service has not been able to find a domain controller to
synchronize with for a long time. To reduce network traffic, the time service
will wait 960 minutes before trying again. No synchronization will take place
during this interval, even if network connectivity is restored. Accumulated
time errors may cause certain network operations to fail. To tell the time
service that network connectivity has been restored and that it should
resynchronize, execute "w32tm /s" from the command line.
CAUSE This behavior may occur because Windows XP Professional and Windows Server 2003 use a
time-synchronization service called W32Time to synchronize the date and time on
computers in a Microsoft Windows 2000-based or Microsoft Windows Server 2003-based
network. A Windows Server 2003-based computer tries to synchronize its time
with a Windows 2000-based or Windows Server 2003-based domain controller. If the Windows
Server 2003-based computer cannot find a Windows 2000-based or Windows Server
2003-based domain controller in the domain, it cannot synchronize the time.
RESOLUTION If there is an existing time-synchronization hierarchy in
your Windows NT 4.0-based domain that uses W32Time, and you want the Windows XP-based, Windows Server 2003-based, or Windows 2000-based computers to participate, follow these steps:
- On a Windows NT 4.0-based domain controller that is running
W32Time, edit the %SystemRoot%\W32time.ini file by setting the LocalNTP value to yes, as follows:
- On the same domain controller, type the following three
commands at the command prompt (be sure to press ENTER after each command):
net stop w32time
w32time -update
net start w32time - On the Windows XP-based computer, type the following at a
command prompt (where domain controller is the
domain controller that you modified in steps 1 and 2)
net time /setsntp:domain controller and then press ENTER. NOTE: If you are using Timeserv on the Windows NT 4.0-based domain,
you must upgrade to the W32Time service before you use this procedure. Timeserv
does not support local NTP server functionality.
Modification Type: | Major | Last Reviewed: | 11/16/2004 |
---|
Keywords: | kbenv kberrmsg kbprb kbTimeServ KB314345 |
---|
|