On Sat, 18 Jan 2025 10:27:37 +0000 Luis Peromarta via samba <samba at lists.samba.org> wrote:> This works. Hopefully it?ll help you. > > http://samba.bigbird.es/doku.php?id=samba:install-chrony >Have I ever said that I hate Windows ? Well, just in case I didn't: I HATE WINDOWS. Something as simple as providing a time server via DHCP doesn't appear to work very well (if at all) on Windows, it seems you have to use a GPO. I only run one Windows 10 computer and that is in a VM and only when I start it to test something. Well I started it to check its 'time' and found out that it wasn't using my pdc_emulator (address supplied by dhcp), it was using its internal clock. All my Linux clients do use the time server supplied via dhcp. To get it to use the pdc_emulator, I had to do this: open cmd prompt on the Windows PC and run as administrator net stop w32time then: w32tm /config /syncfromflags:manual /manualpeerlist:"rpidc1.samdom.example.com" net start w32time Running 'w32tm /query /status' still showed the 'local' clock as time source, so: w32tm /resync To force a sync from the pdc_emulator Running 'w32tm /query /status' again, now showed the pdc_emulator as the time source. Did I say that I hate Windows ? Rowland
It actually worked. But this seems to be a workaround for the problem. I noticed that in this configuration, Windows does not send the "Message Authentication Code" to the Chrony server. Without your proposed solution implemented, Windows also sends a request to Chrony, but Chrony does not respond. 12:12:30.491813 IP (tos 0x0, ttl 128, id 50564, offset 0, flags [none], proto UDP (17), length 148) ??? 192.168.45.14.123 > 192.168.45.9.123: NTPv3, Client, length 120 ??????? Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 17 (131072s), precision -23 ??????? Root Delay: 0.000000, Root dispersion: 1.000000, Reference-ID: (unspec) ????????? Reference Timestamp:? 3944713535.922032999 (2025-01-01T09:45:35Z) ????????? Originator Timestamp: 0.000000000 ????????? Receive Timestamp:??? 0.000000000 ????????? Transmit Timestamp:?? 3946187548.281043099 (2025-01-18T11:12:28Z) ??????????? Originator - Receive Timestamp:? 0.000000000 ??????????? Originator - Transmit Timestamp: 3946187548.281043099 (2025-01-18T11:12:28Z) ??????? (72 more bytes after the header) No response W dniu 18.01.2025 o?12:30, Rowland Penny via samba pisze:> On Sat, 18 Jan 2025 10:27:37 +0000 > Luis Peromarta via samba <samba at lists.samba.org> wrote: > >> This works. Hopefully it?ll help you. >> >> http://samba.bigbird.es/doku.php?id=samba:install-chrony >> > Have I ever said that I hate Windows ? > > Well, just in case I didn't: > > I HATE WINDOWS. > > Something as simple as providing a time server via DHCP doesn't appear > to work very well (if at all) on Windows, it seems you have to use a > GPO. > > I only run one Windows 10 computer and that is in a VM and only when I > start it to test something. > > Well I started it to check its 'time' and found out that it wasn't > using my pdc_emulator (address supplied by dhcp), it was using its > internal clock. All my Linux clients do use the time server supplied > via dhcp. > > To get it to use the pdc_emulator, I had to do this: > > open cmd prompt on the Windows PC and run as administrator > > net stop w32time > > then: > > w32tm /config /syncfromflags:manual /manualpeerlist:"rpidc1.samdom.example.com" > > net start w32time > > Running 'w32tm /query /status' still showed the 'local' clock as time source, so: > > w32tm /resync > > To force a sync from the pdc_emulator > > Running 'w32tm /query /status' again, now showed the pdc_emulator as > the time source. > > Did I say that I hate Windows ? > > Rowland >
I have the exact same problem with my Windows clients. Many of their clocks are drifting and I can't find a solution. I have a GPO according to the Samba Wiki page, but it doesn't work, apparently.> Running 'w32tm /query /status' still showed the 'local' clock as time source, so: > w32tm /resync > To force a sync from the pdc_emulatorI am not that lucky: w32tm /resync Sending resync command to local computer The computer did not resync because no time data was available But: w32tm /query /peers /verbose #Peers: 1 Peer: DC-2.mydomain.com State: Active Time Remaining: 26.6768908s Mode: 3 (Client) Stratum: 0 (unspecified) PeerPoll Interval: 0 (unspecified) HostPoll Interval: 6 (64s) Last Successful Sync Time: (null) LastSyncError: 0x800705B4 (Esta opera??o foi devolvida porque o tempo limite expirou. ) LastSyncErrorMsgId: 0x00000000 (Succeeded) AuthTypeMsgId: 0x0000009B (NtSignature ) Resolve Attempts: 0 ValidDataCounter: 1 Reachability: 2 w32tm /monitor DC-2.mydomain.com[xxx.xxx.xxx.8:123]: ICMP: 0ms delay NTP: +0.0003020s offset from DC-1.mydomain.com RefID: ntp04x.oal.ul.pt [194.117.9.136] Stratum: 3 DC-1.mydomain.com *** PDC ***[ xxx.xxx.xxx.2:123]: ICMP: 0ms delay NTP: +0.0000000s offset from DC-1.mydomain.com RefID: ntp04x.oal.ul.pt [194.117.9.136] Stratum: 3 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: 6 (64s) So, no deal.