A reachable NTP server can still fail to synchronize with Windows Time for several documented reasons:
- Windows may be using the wrong request mode for that server
Windows domain controllers use symmetric active mode by default when sending time synchronization requests. Some non-Windows NTP servers respond only to client mode requests. In that case, the server is reachable, but synchronization still fails. Use client mode with:
Thew32tm /config /manualpeerlist:<NTP_server_IP_Address>,0x8 /syncfromflags:MANUAL net stop w32time net start w32time w32tm /resync0x8flag sets Windows Time to use client mode. - SpecialPollInterval can prevent correction in some cases
If the client is configured with a manual NTP server and uses SpecialPollInterval, and the time offset is greater than LargePhaseOffset, the client can enter SPIKE state and not correct its time even after waiting. A workaround is to use MinPollInterval/MaxPollInterval instead ofSpecialPollInterval, and avoid the0x1flag in/manualpeerlist. Example:w32tm /config /update /manualpeerlist:NTP_server_IP_Address,0x8 /syncfromflags:MANUAL - Large SpecialPollInterval values may be ignored or delay sync unexpectedly
On workgroup computers, largeSpecialPollIntervalvalues can cause synchronization to occur at longer intervals than expected. One workaround is to set a smallerSpecialPollIntervalvalue betweenMinPollIntervalandMaxPollInterval, such as3600seconds, or switch to automatic polling by changing the peer flag from0x9to0x8. - The system may have lost its Windows Time configuration
After certain in-place upgrades, Windows Time settings can revert to defaults. For example:- upgraded domain members may start syncing with
time.windows.cominstead of the domain hierarchy - a PDC emulator can lose its external time source configuration
- a server may stop advertising as a time server
- upgraded domain members may start syncing with
- The root or authoritative server may not be trusted
If the root of the synchronization hierarchy is not set to NoSync and cannot synchronize with another source, clients do not trust the packets it sends. Only time servers identified as reliable are trusted by clients even if they have not synchronized with another source. - UDP port 123 must be available to Windows Time
Windows Time uses UDP 123 for both NTP and SNTP. If another product needs that port, Windows Time must be disabled because Windows reserves UDP 123 while the service is running.
In short, reachability alone is not enough. Common causes are protocol mode mismatch, polling configuration issues, lost configuration after upgrade, trust/authoritative state problems, or UDP 123 conflicts.
References:
- Time synchronization may not succeed when you try to synchronize with a non-Windows NTP server
- When SpecialPollInterval is used as a polling interval, the Windows Time service does not correct the time if the service gets into Spike state
- W32Time: Sync: SpecialPollInterval may be ignored on workgroup computers
- Windows Time Service settings aren't preserved during an in-place upgrade to Windows Server 2016 or Windows 10 Version 1607
- How the Windows Time Service works