I am seeing this error in SCOM for one of my DCs:
Time Provider NtpClient: No valid response has been received from manually configured peer 126.96.36.199 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.
When I run ping -a 188.8.131.52
it resolves to tick.usnogps.navy.mil. Cool except I was not pointing at tick.
On the DC if I run w32tm /query /source it responds with time.windows.com,0x9, which is the value of HKEY_LOCAL_MACHINE\SYSTEM\
eters is set to another DC in another forest.
So this leaves me confused: I thought the time source
is set using HKEY_LOCAL_MACHINE\SYSTEM\
erver. Why is w32tm returning time.windows.com. and why was NtpClient looking at tick? Is peer different that source? And why is the server trying to contact tick at all? Is that a built in fallback to when time.windows.com fails?
Thanks in advance.