search for: referenceid

...itself, but all syncronize to the same NTP servers. Here's a typical output on a windows workstation: # w32tm /query /status Leap Indicator: 0(no warning) Stratum: 3 (secondary reference - syncd by (S)NTP) Precision: -23 (119.209ns per tick) Root Delay: 0.0030693s Root Dispersion: 0.2549162s ReferenceId: 0xC0A8B105 (source IP: 192.168.177.5) Last Successful Sync Time: 10.08.2023 20:42:45 Source: ntp.tls.msk.ru,0x9 Poll Interval: 15 (32768s) All this is run with ntpsec now (on debian bookworm). Local NTP servers at different locations also syncronize with each other. There's no (zero) proble...

..."time.nrc.ca time.chu.nrc.ca" /syncfromflags:ALL And when I check the status with w32tm /query /status then I see this: Leap Indicator: 0(no warning) Stratum: 3 (secondary reference - synced by (S)NTP) Precision: -6 (15.62ms per tick) Root Delay: 0.0313721s Root Dispersion: 0.2973346s ReferenceId: 0x84F60BE3 (source IP: 132.246.11.227) Last Successful Sync Time: 2017-01-30 11:46:22 Source: time.nrc.ca Poll Interval: 11 (2048s) And if I do this: w32tm /resync /rediscover Sending resync command to local computer The computer did not resync because no time data was available. I am afraid th...

...t; > And when I check the status with > > w32tm /query /status > > then I see this: > > Leap Indicator: 0(no warning) > Stratum: 3 (secondary reference - synced by (S)NTP) > Precision: -6 (15.62ms per tick) > Root Delay: 0.0313721s > Root Dispersion: 0.2973346s > ReferenceId: 0x84F60BE3 (source IP: 132.246.11.227) > Last Successful Sync Time: 2017-01-30 11:46:22 > Source: time.nrc.ca > Poll Interval: 11 (2048s) > > And if I do this: > > w32tm /resync /rediscover > Sending resync command to local computer > The computer did not resync because...

...at computer, I get: C:\Users\Administrator.HPRS>w32tm /query /source Free-running System Clock C:\Users\Administrator.HPRS>w32tm /query /status Leap Indicator: 3(not synchronized) Stratum: 0 (unspecified) Precision: -23 (119.209ns per tick) Root Delay: 0.0000000s Root Dispersion: 0.0000000s ReferenceId: 0x00000000 (unspecified) Last Successful Sync Time: unspecified Source: Free-running System Clock Poll Interval: 10 (1024s) Some Windows computers come back with "Free-running System Clock", most with "Local CMOS Clock", not sure what the difference is. However, the interesti...

...HPRS>w32tm /query /source > Free-running System Clock > > C:\Users\Administrator.HPRS>w32tm /query /status > Leap Indicator: 3(not synchronized) > Stratum: 0 (unspecified) > Precision: -23 (119.209ns per tick) > Root Delay: 0.0000000s > Root Dispersion: 0.0000000s > ReferenceId: 0x00000000 (unspecified) > Last Successful Sync Time: unspecified > Source: Free-running System Clock > Poll Interval: 10 (1024s) > > Some Windows computers come back with "Free-running System Clock", most with > "Local CMOS Clock", not sure what the differenc...

...n the DC, also per advice, but I don't think chrony vs. ntpd is the problem. On Windows I get: C:\Users\Administrator.HPRS>w32tm /query /status Leap Indicator: 3(not synchronized) Stratum: 0 (unspecified) Precision: -23 (119.209ns per tick) Root Delay: 0.0000000s Root Dispersion: 0.0000000s ReferenceId: 0x00000000 (unspecified) Last Successful Sync Time: unspecified Source: Local CMOS Clock Poll Interval: 10 (1024s) As I've mentioned, this time synchromization worked perfectly well when this same Windows domain member was connected to the Samba 4.8.2 domain. Does anyone have any idea how I...

Are your clients talking to the DCs re. Time at all ? This is an example in one of my DCs: Run tcpdump on your DC: root at dwing:~# tcpdump??port 123 -v tcpdump: listening on enp1s0, link-type EN10MB (Ethernet), snapshot length 262144 bytes 10:20:41.655081 IP (tos 0x0, ttl 128, id 32113, offset 0, flags [none], proto UDP (17), length 96) ?? ?192.168.3.52.ntp > dwing.mad.mater.int.ntp: NTPv3,