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.

driftedAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mike ThomasConsultantCommented:
Use a different time source I used these before and had simillar issues so I changed to a better time provider.
0
driftedAuthor Commented:
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?
0
Mike ThomasConsultantCommented:
Is it possible that maybe another DC is picking up bad time from somewhere?
0
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

TripyreCommented:
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\CurrentControlSet\Services\W32Time\Parameters\Type In the right pane, right-click Type, and then click Modify. In Edit Value, type NTP in the Value data box, and then click OK.
Set AnnounceFlags to 5. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags In the right pane, right-click AnnounceFlags, and then click Modify. In Edit DWORD Value, type 5 in the Value data box, and then click OK.
Enable NTPServer. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer In the right pane, right-click Enabled, and then click Modify. In Edit DWORD Value, type 1 in the Value data box, and then click OK.
Specify the time sources. To do this, follow these steps: Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters In the right pane, right-click NtpServer, and then click Modify. In Edit Value, type Peers in the Value data box, and then click OK.

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\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval In the right pane, right-click SpecialPollInterval, and then click Modify. In Edit DWORD Value, type TimeInSeconds in the Value data box, and then click OK.

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\CurrentControlSet\Services\W32Time\Config\MaxPosPhaseCorrection In the right pane, right-click MaxPosPhaseCorrection, and then click Modify. In Edit DWORD Value, click to select Decimal in the Base box. In Edit DWORD Value, type TimeInSeconds in the Value data box, and then click OK.

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\CurrentControlSet\Services\W32Time\Config\MaxNegPhaseCorrection In the right pane, right-click MaxNegPhaseCorrection, and then click Modify. In Edit DWORD Value, click to select Decimal in the Base box. In Edit DWORD Value, type TimeInSeconds in the Value data box, and then click OK.

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.

0
driftedAuthor Commented:
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.
0
driftedAuthor Commented:
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.
0
Mike ThomasConsultantCommented:
Would you mind humoring me and enter this into the command prompt? ;)

w32tm /config /manualpeerlist: "ntpl1.npl.co.uk, 0x1 ntpl2.npl.co.uk, 0x1" /syncfromflags:manual /reliable:yes /update

(even if you still have an issue you will be using better time servers and it will certainly rule that out)
0
driftedAuthor Commented:
Mojo: It wouldnt accept that command, I had to modify it to:

w32tm /config /manualpeerlist:ntpl1.npl.co.uk,ntpl2.npl.co.uk /syncfromflags:manual /reliable:yes /update

It then allowed the entry. However this hasnt resolved the issue.
0
driftedAuthor Commented:
Figured out the issue. I was being a bit stupid; the clock I was changing was of  Virtual Machine and not the Host Server. Changed the time on the Host and Boom! all working.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mike ThomasConsultantCommented:
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.
0
Darius GhassemCommented:
I would remove the TimeSync setting on the VM so it won't sync with the Host it should be sync through the Domain.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.