Windows 2008 server not syncing to NTP correctly
I have tried messing around with the w32tm service in order to get the time syncing up with an NTP server (pool.ntp.org) but the time is always out by at least 8 minutes, sometimes more. The time service is definately up and running and when i manually change the time, it automatically changes to the fast time after 5 or so seconds. This is really starting to mess things up on our network and I need a fix asap.
It definately seems like it is syncing to the external NTP, but I dont know why the time is always out.
It definately seems like it is syncing to the external NTP, but I dont know why the time is always out.
Mike Thomas
Use a different time source I used these before and had simillar issues so I changed to a better time provider.
ASKER
Tried that, no luck. I noticed that whenever i manually do an NTP update, the time does change to the correct time! But the time keeps jumping back to the faster time automatically... Any ideas why this could be happening?
Is it possible that maybe another DC is picking up bad time from somewhere?
Configuring the Windows Time service to use an external time source
To configure an internal time server to synchronize with an external time source, follow these steps: Change the server type to NTP. To do this, follow these steps: Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Set AnnounceFlags to 5. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Enable NTPServer. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Specify the time sources. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Note Peers is a placeholder for a space-delimited list of peers from which your computer obtains time stamps. Each DNS name that is listed must be unique. You must append ,0x1 to the end of each DNS name. If you do not append ,0x1 to the end of each DNS name, the changes made in step 5 will not take effect.
Select the poll interval. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Note TimeInSeconds is a placeholder for the number of seconds that you want between each poll. A recommended value is 900 Decimal. This value configures the Time Server to poll every 15 minutes.
Configure the time correction settings. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Note TimeInSeconds is a placeholder for a reasonable value, such as 1 hour (3600) or 30 minutes (1800). The value that you select will depend upon the poll interval, network condition, and external time source. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Note TimeInSeconds is a placeholder for a reasonable value, such as 1 hour (3600) or 30 minutes (1800). The value that you select will depend upon the poll interval, network condition, and external time source.
Quit Registry Editor. At the command prompt, type the following command to restart the Windows Time service, and then press ENTER: net stop w32time && net start w32time
Troubleshooting
For the Windows Time service to function correctly, the networking infrastructure must function correctly. The most common problems that affect the Windows Time service include the following: There is a problem with TCP/IP connectivity, such as a dead gateway. The Name Resolution service is not working correctly. The network is experiencing high volume delays, especially when synchronization occurs over high-latency wide area network (WAN) links. The Windows Time service is trying to synchronize with inaccurate time sources.
We recommend that you use the Netdiag.exe utility to troubleshoot network-related issues. Netdiag.exe is part of the Windows Server 2003 Support Tools package. See Tools Help for a complete list of command-line parameters that you can use with Netdiag.exe. If your problem is still not solved, you can turn on the Windows Time service debug log. Because the debug log can contain very detailed information, we recommend that you contact Microsoft Product Support Services when you turn on the Windows Time service debug log.
To configure an internal time server to synchronize with an external time source, follow these steps: Change the server type to NTP. To do this, follow these steps: Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Set AnnounceFlags to 5. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Enable NTPServer. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Specify the time sources. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Note Peers is a placeholder for a space-delimited list of peers from which your computer obtains time stamps. Each DNS name that is listed must be unique. You must append ,0x1 to the end of each DNS name. If you do not append ,0x1 to the end of each DNS name, the changes made in step 5 will not take effect.
Select the poll interval. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Note TimeInSeconds is a placeholder for the number of seconds that you want between each poll. A recommended value is 900 Decimal. This value configures the Time Server to poll every 15 minutes.
Configure the time correction settings. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Note TimeInSeconds is a placeholder for a reasonable value, such as 1 hour (3600) or 30 minutes (1800). The value that you select will depend upon the poll interval, network condition, and external time source. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\
Note TimeInSeconds is a placeholder for a reasonable value, such as 1 hour (3600) or 30 minutes (1800). The value that you select will depend upon the poll interval, network condition, and external time source.
Quit Registry Editor. At the command prompt, type the following command to restart the Windows Time service, and then press ENTER: net stop w32time && net start w32time
Troubleshooting
For the Windows Time service to function correctly, the networking infrastructure must function correctly. The most common problems that affect the Windows Time service include the following: There is a problem with TCP/IP connectivity, such as a dead gateway. The Name Resolution service is not working correctly. The network is experiencing high volume delays, especially when synchronization occurs over high-latency wide area network (WAN) links. The Windows Time service is trying to synchronize with inaccurate time sources.
We recommend that you use the Netdiag.exe utility to troubleshoot network-related issues. Netdiag.exe is part of the Windows Server 2003 Support Tools package. See Tools Help for a complete list of command-line parameters that you can use with Netdiag.exe. If your problem is still not solved, you can turn on the Windows Time service debug log. Because the debug log can contain very detailed information, we recommend that you contact Microsoft Product Support Services when you turn on the Windows Time service debug log.
ASKER
We have 2 domain controllers which both point to the same NTP server (uk.pool.ntp.org). There are no other applications running on either DC that are syncing time. Just to eliminate one of the domain controllers, I shutdown one and tried solely using one DC, but the same problem happened.
ASKER
Tripyre: you just pulled that from the results of a google search, i've see that site already and tried it, but to no avail.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Mojo: It wouldnt accept that command, I had to modify it to:
w32tm /config /manualpeerlist:ntpl1.npl.
It then allowed the entry. However this hasnt resolved the issue.
w32tm /config /manualpeerlist:ntpl1.npl.
It then allowed the entry. However this hasnt resolved the issue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Haha, this is very common, if you had mentioned they were VM Guests I bet you would have 50 replies suggesting that you check the host time.
Glad you got it going though.
Glad you got it going though.
I would remove the TimeSync setting on the VM so it won't sync with the Host it should be sync through the Domain.