Manual Sync as a Troubleshooting Step
One common reason to manually synchronize a computer�s time is as a troubleshooting step. For
example, if you notice System event log entries from the W32Time service, which indicate that time
synchronization failed, you might attempt to manually sync the time as a troubleshooting step.
Typically, failed time synchronization is the result of the computer being unable to contact a domain
controller, and you should troubleshoot that problem directly. Once the W32Time service fails to locate a
domain controller, it will reduce its activity to location attempts every 16 hours until restarted. You�ll see
System event log messages to this effect, with Event ID 64, whenever the service is unable to locate a
domain controller for a long period of time.
�
To manually synchronize time, open a command-line window, and run:
1. "net stop w32time".
2. "w32time �update"
3.�"net start w32time"
�
4. Optional Stage - "dsquery server -hasfsmo pdc" - The result will reflect if the client find
������������������������������the PDC (or PDC Emulator) server.
5. Check the System event log to ensure that the W32Time service has not logged additional error
������� messages.
example, if you notice System event log entries from the W32Time service, which indicate that time
synchronization failed, you might attempt to manually sync the time as a troubleshooting step.
Typically, failed time synchronization is the result of the computer being unable to contact a domain
controller, and you should troubleshoot that problem directly. Once the W32Time service fails to locate a
domain controller, it will reduce its activity to location attempts every 16 hours until restarted. You�ll see
System event log messages to this effect, with Event ID 64, whenever the service is unable to locate a
domain controller for a long period of time.
�
To manually synchronize time, open a command-line window, and run:
1. "net stop w32time".
2. "w32time �update"
3.�"net start w32time"
�
4. Optional Stage - "dsquery server -hasfsmo pdc" - The result will reflect if the client find
������������������������������the PDC (or PDC Emulator) server.
5. Check the System event log to ensure that the W32Time service has not logged additional error
������� messages.