This works. Hopefully it?ll help you. http://samba.bigbird.es/doku.php?id=samba:install-chrony On 18 Jan 2025 at 08:49 +0000, Programnet via samba <samba at lists.samba.org>, wrote:> I noticed a problem with time synchronization on all Windows endpoints. > I am using Samba 4.21.3 and Chrony 4.3-2. > > When I run the following command in Windows: > > w32tm /monitor > dc1.xxxx.pl *** PDC ***[192.168.45.10:123]: > ICMP: 1ms delay > NTP: +0.0000000s offset from dc1.xxxx.pl > RefID: time.cloudflare.com [162.159.200.123] > Stratum: 4 > dc2.xxxx.pl[192.168.45.9:123]: > ICMP: 1ms delay > NTP: -0.0001207s offset from dc1.xxxx.pl > RefID: ntp1.orange.pl [80.50.102.114] > Stratum: 2 > > 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. > > But when I run: > > w32tm /resync > Sending resync command to local computer > The computer did not resync because no time data was available. > > When I check on the DC servers with the |tcpdump| program, there is an > incoming packet, but no outgoing packet. > > I am sure this worked previously. It likely stopped working after > upgrading to Samba version 4.21.1. > > I configured Chrony based on the example: > https://samba.tranquil.it/doc/en/samba_config_server/debian/server_install_ntp_debian.html > <https://samba.tranquil.it/doc/en/samba_config_server/debian/server_install_ntp_debian.html> > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
Unfortunately, this does not solve the problem. When I run the command: w32tm /monitor I can see both the request and response in tcpdump NTPv1. 12:12:15.230555 IP (tos 0x0, ttl 128, id 50559, offset 0, flags [none], proto UDP (17), length 76) ??? 192.168.45.14.58655 > 192.168.45.9.123: NTPv1, Client, length 48 ??????? Leap indicator:? (0), Stratum 0 (unspecified), poll 0 (1s), precision 0 ??????? Root Delay: 0.000000, Root dispersion: 0.000000, Reference-ID: (unspec) ????????? Reference Timestamp:? 0.000000000 ????????? Originator Timestamp: 0.000000000 ????????? Receive Timestamp:??? 0.000000000 ????????? Transmit Timestamp:?? 3946187533.020913599 (2025-01-18T11:12:13Z) ??????????? Originator - Receive Timestamp:? 0.000000000 ??????????? Originator - Transmit Timestamp: 3946187533.020913599 (2025-01-18T11:12:13Z) 12:12:15.230763 IP (tos 0x0, ttl 64, id 34850, offset 0, flags [DF], proto UDP (17), length 76) ??? 192.168.45.9.123 > 192.168.45.14.58655: NTPv1, Server, length 48 ??????? Leap indicator:? (0), Stratum 3 (secondary reference), poll 0 (1s), precision -25 ??????? Root Delay: 0.021835, Root dispersion: 0.002899, Reference-ID: 0xd47f5fda ????????? Reference Timestamp:? 3946187516.138654557 (2025-01-18T11:11:56Z) ????????? Originator Timestamp: 3946187533.020913599 (2025-01-18T11:12:13Z) ????????? Receive Timestamp:??? 3946187535.230308235 (2025-01-18T11:12:15Z) ????????? Transmit Timestamp:?? 3946187535.230492444 (2025-01-18T11:12:15Z) ??????????? Originator - Receive Timestamp:? +2.209394635 ??????????? Originator - Transmit Timestamp: +2.209578844 However, when I execute: w32tm /resync tcpdump shows only the NTPv3 request, as if Chrony is not responding. 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) W dniu 18.01.2025 o 11:27, Luis Peromarta via samba pisze: > This works. Hopefully it?ll help you.
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