Dual DC Time Service
- by poconnor
I believe I'm having an issue with my Domain Controllers and Time Server. On my back up DC, I keep seeing a warning stating "The time service has stopped advertising as a time source because the local clock is not synchronized."
Does this mean that my backup DC believes it's a Time Server? My PDC should be the time server and I have gone through setting up the PDC as the time server.
I was not around for the original setup of the time server with the old PDC and Backup DC. But I believe the old PDC was the time server so I setup the new PDC as the new time server, when I decommissioned the old PDC. Is it possible that the Backup DC was setup as the time server and it still thinks it's suppose to be giving out time to everyone?
Registry for PDC has NTP
Registry for Backup has NT5D5
Results of w32tm /monitor
Getting AD DC list for default domain...
Analyzing:delayoffset from DC1.local..com
Stratum: 4
delayoffset from DC1.local..com
Stratum: 3
Warning:
Reverse name resolution is best effort. It may not be
correct since RefID field in time packets differs across
NTP implementations and may not be using IP addresses.
DC2.local..com[192.168.1.8:123]:
ICMP: 1ms
NTP: -0.6349491s RefID: DC1.local..com [192.168.1.9]
DC1.local..com *** PDC ***[192.168.1.9:123]:
ICMP: 0ms
NTP: +0.0000000s RefID: wwwco1test12.microsoft.com [65.55.21.20]
