How to Fix Computer Time Synchronization Problems
Published 2026-10-16 · Marion Remote Fix
Your computer is supposed to keep accurate time automatically by periodically synchronizing with internet time servers. When this synchronization fails, the system clock drifts — sometimes by seconds, sometimes by minutes or hours — creating problems with secure websites, two-factor authentication, email timestamps, and file synchronization services. Time sync failures are frustrating because the feature is supposed to work invisibly in the background, and when it stops, there is rarely an obvious error message telling you why.
How time sync works
- Your computer uses NTP (Network Time Protocol) to communicate with time servers — dedicated computers with highly accurate clocks, usually synchronized to atomic clocks
- On Windows, the Windows Time Service (w32time) handles synchronization. It contacts a time server (time.windows.com by default), compares the server time to the local clock, and adjusts the local clock to match
- On Mac, the timed daemon handles synchronization using time.apple.com as the default server
- Synchronization happens periodically — Windows defaults to once per week, macOS syncs more frequently. Between syncs, the hardware clock runs independently and drifts naturally
- NTP uses UDP port 123 for communication. Both the request to the time server and the response use this port
Diagnosing sync failures
Check if sync is enabled
- Windows: Open Settings, Time and Language, Date and Time. Verify that Set Time Automatically is toggled on. If it is off, the computer makes no attempt to sync
- Mac: Open System Settings, General, Date and Time. Verify Set Date and Time Automatically is checked
- If the toggle is on but time is still wrong, the sync attempts are failing — proceed to the next steps
Try a manual sync
- Windows: In the same Date and Time settings, click Sync Now. Watch for a message that says the time was successfully synchronized or an error message
- A successful sync that does not persist suggests the time is being reset by something — a conflicting program, a failing CMOS battery, or another time source overriding the correction
- A failed sync indicates a connectivity or configuration problem between your computer and the time server
Check the Windows Time Service
- Open the Services application (press Windows key, type services.msc, press Enter)
- Scroll to Windows Time. Check the Status column — it should say Running. Check the Startup Type — it should be Automatic or Automatic (Trigger Start)
- If the service is stopped, right-click it and select Start. If the startup type is Disabled, right-click, select Properties, and change the startup type to Automatic
- If the service will not start or keeps stopping, the service registration may be corrupted. Open an elevated Command Prompt (right-click Start, select Terminal as Administrator or Command Prompt as Administrator) and run these commands in sequence: net stop w32time, then w32tm /unregister, then w32tm /register, then net start w32time, then w32tm /resync
Common causes of sync failure
Firewall blocking NTP
- NTP requires UDP port 123 to be open for outbound communication. If a firewall is blocking this port, sync requests never reach the time server or the response never comes back
- Check Windows Firewall: open Windows Security, Firewall and Network Protection, Advanced Settings. Look for outbound rules blocking UDP port 123
- Third-party security software (Norton, McAfee, Bitdefender, Kaspersky, etc.) may have their own firewall rules that block NTP independently of Windows Firewall. Check the security software firewall settings for rules related to NTP, UDP 123, or the w32time service
- Corporate networks may restrict NTP traffic to specific internal time servers. If your work computer cannot sync with time.windows.com, the network may require you to use an internal server instead. Contact your IT department
Time server unreachable
- The default time server (time.windows.com) is occasionally unreachable due to server load, maintenance, or routing issues
- Try switching to a different time server. In Windows: Settings, Time and Language, Date and Time, scroll to Related Settings, Additional Date, Time, and Regional Settings, then Set the Time and Date (under Date and Time in Control Panel), Internet Time tab, Change Settings. Replace time.windows.com with an alternative like time.nist.gov, pool.ntp.org, or time.google.com
- On Mac: System Settings, General, Date and Time. Change the time server from time.apple.com to an alternative
- pool.ntp.org is a pool of thousands of volunteer time servers worldwide and is generally the most reliable option for home users
DNS resolution problems
- If your computer cannot resolve the time server hostname to an IP address, the sync request never initiates. This happens when DNS is not working correctly on your network
- Test DNS resolution: open a Command Prompt and type nslookup time.windows.com. If this returns an error or times out, DNS resolution is the problem, not NTP specifically
- Try using the IP address of a time server directly instead of the hostname. The NIST time servers have well-known IP addresses that can be used as a temporary workaround while DNS issues are resolved
VPN or proxy interference
- Some VPN configurations route NTP traffic through the VPN tunnel where it may be blocked or delayed. If time sync works when the VPN is disconnected but fails when connected, the VPN is the cause
- Some proxy servers do not pass UDP traffic, which NTP requires. If your network uses a proxy for internet access, NTP may not function through it
- Solution: configure the VPN or proxy to allow UDP port 123 traffic, or set up a split-tunnel VPN configuration that keeps NTP traffic on the local network
Group Policy overriding settings
- On domain-joined computers (corporate environments), Group Policy may control time sync configuration. Your personal settings may be overridden by domain policy
- Domain-joined computers typically sync time from the domain controller rather than public time servers. If the domain controller time is wrong, all domain computers will be wrong
- If you manage the domain: verify the Primary Domain Controller Emulator (PDCe) is configured to sync with an external NTP source. If not, time can drift for the entire organization
Increasing sync frequency on Windows
The default Windows sync interval of one week allows significant drift on computers with inaccurate hardware clocks. You can increase the frequency:
- Open Registry Editor (regedit). Navigate to HKEY_LOCAL_MACHINE, SYSTEM, CurrentControlSet, Services, W32Time, TimeProviders, NtpClient
- Find the SpecialPollInterval value. The default is 604800 (seconds in one week). Change it to a smaller value: 3600 for hourly sync, 21600 for every six hours, or 86400 for daily
- Restart the Windows Time Service after making the change for it to take effect
- More frequent syncing keeps the clock more accurate but generates more network traffic. For home use, hourly or daily is reasonable
When sync works but time keeps drifting
- If the clock is correct immediately after syncing but drifts noticeably between syncs, the hardware clock oscillator is inaccurate. This is normal for cheap crystal oscillators but the drift should be small — a few seconds per day at most
- Large drift between syncs (minutes per day) suggests a hardware issue. The CMOS battery may be failing (affecting the clock circuit power), or the motherboard clock circuit may have a component issue
- Increasing the sync frequency compensates for faster hardware clock drift. If the clock drifts one minute per day but syncs hourly, the maximum error is about 2.5 seconds — imperceptible for most uses
Verifying sync is working
- Open Command Prompt and run w32tm /query /status. This shows the last sync time, the time source, and the current offset from the reference
- The Stratum field shows the quality of the time source. Stratum 1 is an atomic clock. Stratum 2 syncs from stratum 1. Most public time servers are stratum 1 or 2. Your computer will typically be stratum 3 or 4, which is perfectly adequate
- The Root Delay and Root Dispersion values show the network delay and uncertainty. Large values indicate a slow or unreliable connection to the time server
Need help with time sync?
If your computer time synchronization is failing despite troubleshooting, there may be a firewall configuration, service corruption, or network issue that requires deeper investigation. Marion Remote Fix can remotely diagnose your time sync configuration, check service status and network connectivity, and resolve the issues preventing your clock from staying accurate.