F
Foley80
Hi Everybody,
We have a Windows 2016 Server (computer name: alma), which is a backup DC. There is an external time sync with the following settings:
C:\Users\Administrator.CAR>w32tm /query /peers
#Peers: 1
Peer: vega.cbk.poznan.pl,0x1
State: Active
Time Remaining: 1429.4648363s
Mode: 1 (Symmetric Active)
Stratum: 3 (secondary reference - syncd by (S)NTP)
PeerPoll Interval: 4 (16s)
HostPoll Interval: 4 (16s)
C:\Users\Administrator.CAR>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 4 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0683954s
Root Dispersion: 28.3264654s
ReferenceId: 0x96FEB70F (source IP: 150.254.183.15)
Last Successful Sync Time: 2018. 12. 17. 13:35:25
Source: vega.cbk.poznan.pl,0x1
Poll Interval: 10 (1024s)
I have realised that the time is usually not correct or just jump suddenly one or two minutes forward / backward. In order to find the problem I'm running continuously stripchart command in another domain machine (computer name: beta), see below:
w32tm /stripchart /computer:alma /period:5 /dataonly >> d:\stripchart.txt
In the result stripchart.txt I see many time problems, like:
08:25:53, +06.5606401s
08:25:58, +06.3156766s
08:26:03, +06.0816088s
08:26:08, +05.8571137s
08:26:13, +68.9255276s -> this is a big jump!
08:26:18, +68.9258212s
08:26:23, +68.9261180s
08:26:28, +68.9264664s
08:26:33, +68.9267983s
later:
08:27:36, +71.3378858s
08:27:41, +71.4851400s
08:28:57, -00.0091695s -> this is a big jump!
08:29:02, -00.0092129s
later:
08:33:24, -00.6354319s
08:33:29, -00.6475846s
08:33:34, -03.0636237s
08:33:39, -05.7633219s
08:33:44, -08.3384265s
08:33:49, -10.7999634s
08:33:54, -13.1558996s
08:33:59, -15.4084306s
08:34:04, -17.5656530s
08:34:09, -19.6281827s
08:34:14, -21.5999574s
08:34:19, -23.4803603s
08:34:24, -25.2800085s
08:34:29, -27.0038651s
08:34:34, -28.6520029s
08:34:39, -30.2278394s
08:34:44, -31.7345218s
08:34:49, -33.1752016s
08:34:54, -34.5525327s
I must note that there was no sync during the two big jump, so:
Last Successful Sync Time: 2018. 12. 17. 8:24:12 and
Last Successful Sync Time: 2018. 12. 17. 8:27:22
Is there anybody explain what happens in the alma machine? Why jump the time and why incorrect the time although the synchronization is running continuously?
I'm sure the time in "beta" machine is correct (I'm comparing it with my mobile phone).
Many thanks in advance!
Continue reading...
We have a Windows 2016 Server (computer name: alma), which is a backup DC. There is an external time sync with the following settings:
C:\Users\Administrator.CAR>w32tm /query /peers
#Peers: 1
Peer: vega.cbk.poznan.pl,0x1
State: Active
Time Remaining: 1429.4648363s
Mode: 1 (Symmetric Active)
Stratum: 3 (secondary reference - syncd by (S)NTP)
PeerPoll Interval: 4 (16s)
HostPoll Interval: 4 (16s)
C:\Users\Administrator.CAR>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 4 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0683954s
Root Dispersion: 28.3264654s
ReferenceId: 0x96FEB70F (source IP: 150.254.183.15)
Last Successful Sync Time: 2018. 12. 17. 13:35:25
Source: vega.cbk.poznan.pl,0x1
Poll Interval: 10 (1024s)
I have realised that the time is usually not correct or just jump suddenly one or two minutes forward / backward. In order to find the problem I'm running continuously stripchart command in another domain machine (computer name: beta), see below:
w32tm /stripchart /computer:alma /period:5 /dataonly >> d:\stripchart.txt
In the result stripchart.txt I see many time problems, like:
08:25:53, +06.5606401s
08:25:58, +06.3156766s
08:26:03, +06.0816088s
08:26:08, +05.8571137s
08:26:13, +68.9255276s -> this is a big jump!
08:26:18, +68.9258212s
08:26:23, +68.9261180s
08:26:28, +68.9264664s
08:26:33, +68.9267983s
later:
08:27:36, +71.3378858s
08:27:41, +71.4851400s
08:28:57, -00.0091695s -> this is a big jump!
08:29:02, -00.0092129s
later:
08:33:24, -00.6354319s
08:33:29, -00.6475846s
08:33:34, -03.0636237s
08:33:39, -05.7633219s
08:33:44, -08.3384265s
08:33:49, -10.7999634s
08:33:54, -13.1558996s
08:33:59, -15.4084306s
08:34:04, -17.5656530s
08:34:09, -19.6281827s
08:34:14, -21.5999574s
08:34:19, -23.4803603s
08:34:24, -25.2800085s
08:34:29, -27.0038651s
08:34:34, -28.6520029s
08:34:39, -30.2278394s
08:34:44, -31.7345218s
08:34:49, -33.1752016s
08:34:54, -34.5525327s
I must note that there was no sync during the two big jump, so:
Last Successful Sync Time: 2018. 12. 17. 8:24:12 and
Last Successful Sync Time: 2018. 12. 17. 8:27:22
Is there anybody explain what happens in the alma machine? Why jump the time and why incorrect the time although the synchronization is running continuously?
I'm sure the time in "beta" machine is correct (I'm comparing it with my mobile phone).
Many thanks in advance!
Continue reading...