What to do when Windows resync fails

After running command: w32tm /resync, you receive error: "The computer did not resync because no time data was available". A warning is also posted to the event log: "Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the PDC emulator"

SNTP port, ip address

First of all check your router settings. SNTP port should be forwarded to your domain controller IP address. Allow TCP and UDP packets to use SNTP Port.

The identification number of ntp port is 123

Restart windows service

to reinitialize windows ntp service simply use following batch script (Copy the text from following source code into your favorite text editor and save as "ntp-restart.bat")

net stop w32time

w32tm /unregister

w32tm /register

w32tm /config /manualpeerlist:192.43.244.18 /syncfromflags:MANUAL /reliable:YES

net start w32time

w32tm /config /update

w32tm /resync /rediscover

The first line stops the NTP service. You then unregister it and re-register it, recreating all the registry keys with default values, giving you a standard starting point. After that, you configure it, specifying an NTP server's ip address as a peer (this IP is time.nist.gov) and that it should synchronise from the peer list. Also mark this server as a reliable time server. start the w32tm service again, tell it to update its configuration, just in case, and then resynchronise again.

How to set NTP on windows 2003 server steps

In case the above script doesn't work or you want to specifically tinker with all the registry settings.

  1. Change Windows to use the NTP protocol for time synchronization

    Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type
    
    Value: Type
    
    Data: NTP
  2. Configure the AnnounceFlags value

    Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
    
    Value: AnnounceFlags
    
    Data: 5
  3. Enable the NTP server value:

    Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer
    
    Value: Enabled
    
    Data: 1
  4. Specify the NTP server to use

    Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\NtpServer
    
    Value: NtpServer
    
    Data: time.nist.gov,0×1
  5. Select the NTP polling interval:

    Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval
    
    Value: SpecialPollInterval
    
    Data: 900
  6. Configure the max time correction settings

    Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxPosPhaseCorrection
    
    Value: MaxPosPhaseCorrection
    
    Radix: Decimal
    
    Data: 3600
  7. Set minimum for time correction

    Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxNegPhaseCorrection
    
    Value: MaxNegPhaseCorrection
    
    Radix: Decimal
    
    Data: 3600

After this, stopping and restarting the NTP service should get you working. If it does not, check the value configured in step 4 – this being misconfigured is the only time I’ve seen errors in the Windows Time service like the ones you’ve posted, so it’s possible this is incorrect in your registry. I would also suggest using a time server OTHER than time.nist.gov, as it is a VERY busy time server and you are likely to miss one or two time syncs to it before you get a good one (when very accurate time is needed, you should use stratum-0 servers).

Or use another time server, preferrably a stratum-2 NTP server closer to you. You can find these listed here: List of stratum 2 ntp servers

Optional Stratum 0 NtpServer

While stratum-2 servers are easily configurable and can be found all across the globe, they do not provide as exact time representation as stratum 0 servers

These steps are easily replicable, if you have bought NtpServer from us. Only the time accuracy is far superior to stratum 2 servers.

All NtpServers are easy to use with Windows machines: