How to manually sync time between domain client and local time server

Author:

Yuval Sinay MVP

COMMUNITY SOLUTIONS CONTENT DISCLAIMER

MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.

Tips

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.
गुण

आलेख ID: 555225 - पिछली समीक्षा: 14/02/2017 - संशोधन: 1

Microsoft Windows XP Professional, Microsoft Windows XP Tablet PC Edition, Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems, Microsoft Windows Server 2003, Datacenter Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Standard Edition (32-bit x86), Microsoft Windows Server 2003, Web Edition, Microsoft Windows NT Server 4.0, Terminal Server Edition

प्रतिक्रिया