Windows 2008 R2 w32time configuration Clients off by two minutes
Posted on 2012-03-12
So, I spent a great deal of time getting my AD servers to sync to the Internet but now that they are, all my servers are still off from the AD Servers and I don't understand it.
On the AD Servers I configured them as such:
w32tm /config /manualpeerlist:"0.north-america.pool.ntp.org 1.north-america.pool.ntp.org 2.north-america.pool.ntp.org",0x8 /syncfromflags:MANUAL /reliable:YES /update
after restarting they sync just fine and I'm good to go.
On the member Servers in the domain I first did this:
w32tm /config /syncfromflags:DOMHIER /update
That didn't seem to do anything so I changed it to this below with the ips of the domain controllers:
w32tm /config /manualpeerlist:"10.0.0.10 10.0.0.11",0x8 /syncfromflags:MANUAL /update
Well, at that point the clock shifted it's time. But it did so about 1:45 seconds different from the AD servers. previously it was almost four minutes. So it did update, but it did so within 2 minutes instead of exact. I don't understand it!
I can't seem to figure out. I did a test on the server and this is the result:
w32tm /stripchart /computer:10.0.0.10 /dataonly
Tracking 10.0.0.10 [10.0.0.10:123].
The current time is 3/12/2012 6:03:45 PM.
Why is it off by so much?
Oh, and I made sure I had no Group Policy governing which servers to sync time with. I have that setup on my workstation OU and those computers are off by about 24 seconds.