G
Gian99
Guest
I've been rattling my brain about a situation I have in my environment. We have 5 DCs in the in the environment. What is going on is if a end user machine does not have the PDCe listed as the peer, then time synchronization does not work. All of the DCs have the PDCe as their time source and time is synchronizing successfully among them. Please see some w32tm output below.
----
Client that is not synchronizing time
C:\Windows\system32>w32tm /query /peers
#Peers: 1
Peer: NON-PDCe
State: Active
Time Remaining: 291.7218809s
Mode: 3 (Client)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 10 (1024s)
C:\Windows\system32>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 1 (primary reference - syncd by radio clock)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s
Root Dispersion: 10.0000000s
ReferenceId: 0x4C4F434C (source name: "LOCL")
Last Successful Sync Time: 2/28/2019 3:37:18 PM
Source: Free-running System Clock
Poll Interval: 10 (1024s)
----
Some clients don't even show a peer:
C:\Users\user>w32tm /query /peers
#Peers: 1
Peer:
State: Pending
Time Remaining: 797.0196934s
Mode: 0 (reserved)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 0 (unspecified)
----
Output of client that time sync works:
C:\Users\user>w32tm /query /peers
#Peers: 1
Peer: PDCe
State: Active
Time Remaining: 12303.9146627s
Mode: 3 (Client)
Stratum: 14 (secondary reference - syncd by (S)NTP)
PeerPoll Interval: 15 (32768s)
HostPoll Interval: 15 (32768s)
C:\Users\user>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 15 (secondary reference - syncd by (S)NTP)
Precision: -23 (119.209ns per tick)
Root Delay: 0.0703662s
Root Dispersion: 0.4165810s
ReferenceId: 0x0A01013D (source IP: 10.1.1.61)
Last Successful Sync Time: 3/1/2019 9:51:35 AM
Source: PDCe
Poll Interval: 15 (32768s)
Why would a client not be able to sync time unless it has the PDCe as it's peer? Any help would be greatly appreciated.
Continue reading...
----
Client that is not synchronizing time
C:\Windows\system32>w32tm /query /peers
#Peers: 1
Peer: NON-PDCe
State: Active
Time Remaining: 291.7218809s
Mode: 3 (Client)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 10 (1024s)
C:\Windows\system32>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 1 (primary reference - syncd by radio clock)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s
Root Dispersion: 10.0000000s
ReferenceId: 0x4C4F434C (source name: "LOCL")
Last Successful Sync Time: 2/28/2019 3:37:18 PM
Source: Free-running System Clock
Poll Interval: 10 (1024s)
----
Some clients don't even show a peer:
C:\Users\user>w32tm /query /peers
#Peers: 1
Peer:
State: Pending
Time Remaining: 797.0196934s
Mode: 0 (reserved)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 0 (unspecified)
----
Output of client that time sync works:
C:\Users\user>w32tm /query /peers
#Peers: 1
Peer: PDCe
State: Active
Time Remaining: 12303.9146627s
Mode: 3 (Client)
Stratum: 14 (secondary reference - syncd by (S)NTP)
PeerPoll Interval: 15 (32768s)
HostPoll Interval: 15 (32768s)
C:\Users\user>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 15 (secondary reference - syncd by (S)NTP)
Precision: -23 (119.209ns per tick)
Root Delay: 0.0703662s
Root Dispersion: 0.4165810s
ReferenceId: 0x0A01013D (source IP: 10.1.1.61)
Last Successful Sync Time: 3/1/2019 9:51:35 AM
Source: PDCe
Poll Interval: 15 (32768s)
Why would a client not be able to sync time unless it has the PDCe as it's peer? Any help would be greatly appreciated.
Continue reading...