Unable to get time to sync on Server 2012 R2 DC
-
@ccwtech BIOs time is not the same as the OS time. The OS time will be affected by the BIOS time but not viceversa. So if there is a time difference between the OS and BIOS, BIOS will always win.
-
Interesting... this just popped up in the log as well:
Time Provider NtpClient: No valid response has been received from manually configured peer 3.pool.ntp.org,0x8 after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS name. The error was: The peer is unreachable.
-
@ccwtech change all the Ntp servers to known good addresses.
-
Just using pool.ntp.org now.
Getting this:
The system time has changed to 2017-07-26T03:59:47.234000000Z from 2017-07-26T03:59:47.247242200Z.But it's still 7 minutes behind...
-
I'm reading that if it is off only by a few minutes it slowly changes the clock to run faster until it 'catches up'.
Check again in the AM and report back.
Goodnight all.
-
@ccwtech said in Unable to get time to sync on Server 2012 R2 DC:
I'm reading that if it is off only by a few minutes it slowly changes the clock to run faster until it 'catches up'.
Check again in the AM and report back.
Goodnight all.
That's correct.
-
With the fact that it slowly 'catches up' last night I adjusted the time to be within 2 minutes of current time hoping that it would 'catch up' more quickly. As of this morning it's still at 2 minutes behind, so no joy....
-
When I've had time sync issues in the past to help I've just installed a atomic clock sync tool onto the server.
-
Check Group Policy setting in the default domain controller OU to make sure NTP/SNTP is not disabled. See this article:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/95733420-c3c8-456d-a5c1-b426ebafb53e/pdc-will-not-sync-with-external-time-source-ntp-using-w32time?forum=winserverNIS
Also, try an IP address instead of name. I use 132.163.4.103 and 129.6.15.29 for my testing, then set to pool.ntp.org when testing's complete. -
@hobbit666 I have tried a couple of those.
It's weird to me as it seems like it's able to sync the time, but no matter if it is 7 minutes late or 2 minutes late the server 'thinks' it's off by 0 ms so it doesn't change.
It's just odd.
-
@ccwtech as long as it is in between 5 minutes from the right time it should be okay.
-
@dbeato But it doesn't. I manually changed it from 7 behind to 2 behind to let it catch up. However I have set the time on this server (to correct time) manually a couple months ago and that is when the company called me and said it's off again.
-
@ccwtech Last thing to check is the actual server hardware clock then
-
@dbeato said in Unable to get time to sync on Server 2012 R2 DC:
@ccwtech as long as it is in between 5 minutes from the right time it should be okay.
Yeah. Two should be well within tolerance.
-
@ccwtech said in Unable to get time to sync on Server 2012 R2 DC:
@dbeato But it doesn't. I manually changed it from 7 behind to 2 behind to let it catch up. However I have set the time on this server (to correct time) manually a couple months ago and that is when the company called me and said it's off again.
Oh. This is a VM? Is the hypervisor and the VM the same?
-
@scottalanmiller said in Unable to get time to sync on Server 2012 R2 DC:
Oh. This is a VM? Is the hypervisor and the VM the same?
He said in a earlier post
Physical box (no VM).
-
@hobbit666 said in Unable to get time to sync on Server 2012 R2 DC:
@scottalanmiller said in Unable to get time to sync on Server 2012 R2 DC:
Oh. This is a VM? Is the hypervisor and the VM the same?
He said in a earlier post
Physical box (no VM).
Oh sorry, missed that.
-
I put a new CMOS battery in, made sure the time in BIOS was correct. It's now about 30 seconds behind. Seems like it gradually keeps slowing until manually entered again.
-
@ccwtech said in Unable to get time to sync on Server 2012 R2 DC:
I put a new CMOS battery in, made sure the time in BIOS was correct. It's now about 30 seconds behind. Seems like it gradually keeps slowing until manually entered again.
Maybe the clock has gone bad?
-
Is there any test for that? I would imagine the fix is a new motherboard, right?
