search for: ntpv3

...has 10.1.0.3 tell 10.1.0.111, length 46 ARP, Reply 10.1.0.3 is-at 00:0c:29:07:39:8e, length 28 IP 10.1.0.111.5060 > 10.1.0.3.5060: SIP, length: 926 IP 10.1.0.111.5060 > 10.1.0.3.5060: SIP, length: 926 IP 10.1.0.111.5060 > 10.1.0.3.5060: SIP, length: 926 IP 10.1.0.111.123 > 10.1.0.3.123: NTPv3, Client, length 48 IP 10.1.0.3.123 > 10.1.0.111.123: NTPv3, Server, length 48 IP 10.1.0.111.5060 > 10.1.0.3.5060: SIP, length: 926 IP 10.1.0.111.5060 > 10.1.0.3.5060: SIP, length: 926 IP 10.1.0.111.5060 > 10.1.0.3.5060: SIP, length: 926 IP 10.1.0.111.123 > 10.1.0.3.123: NTPv3, Client...

Hi, I configured my NTP server in samba 4 according to the article " https://wiki.samba.org/index.php/Time_Synchronisation" however I verified that the NTP server does not respond to requests from Windows NTPv3 clients, it only responds to NTPv4. Following my ntp.conf: # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help driftfile /var/lib/ntp/ntp.drift # Enable this if you want statistics to be logged. #statsdir /var/log/ntpstats/ statistics loopstats peerstats clockstats filegen loopstats...

...un 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, Client, length 68 Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 17 (131072s), precision -23 Root Delay: 0.017257, Root dispersion: 16.000000, Reference-ID: (unspec) ??Reference Timestamp:??3916459101.490509499 (2024-02-09T09:18:21Z) ??Originator Timestamp: 0.0000000...

...y result: -------------------------- # tcpdump -v -i eth0 port 123 tcpdump: listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes 10:23:07.468629 IP (tos 0x0, ttl 128, id 22607, offset 0, flags [none], proto UDP (17), length 96) 192.168.0.53.ntp > mail.hprs.local.ntp: NTPv3, Client, length 68 Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 7 (128s), precision -23 Root Delay: 0.000000, Root dispersion: 1.000000, Reference-ID: (unspec) Reference Timestamp: 3916127270.315146199 (2024-02-05T13:07:50Z) Originat...

...---------------- > # tcpdump -v -i eth0 port 123 > tcpdump: listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes > 10:23:07.468629 IP (tos 0x0, ttl 128, id 22607, offset 0, flags [none], proto UDP (17), length 96) > 192.168.0.53.ntp > mail.hprs.local.ntp: NTPv3, Client, length 68 > Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 7 (128s), precision -23 > Root Delay: 0.000000, Root dispersion: 1.000000, Reference-ID: (unspec) > Reference Timestamp: 3916127270.315146199 (2024-02-05T13:07:50Z)...

On Thu Jan 4 19:46:02 2024 Mark Foley via samba <samba at lists.samba.org> wrote: > > I've added a Windows 10 domain member to my Domain. I'm now following the > procedure in https://wiki.samba.org/index.php/Time_Synchronisation#Configuring_Time_Synchronisation_on_a_Windows_Domain_Member. > > [deleted] The above references the first in a long thread I started having

...o Bacci via samba < samba at lists.samba.org> wrote: > Hi, > > I configured my NTP server in samba 4 according to the article " > https://wiki.samba.org/index.php/Time_Synchronisation" however I verified > that the NTP server does not respond to requests from Windows NTPv3 > clients, it only responds to NTPv4. > > Following my ntp.conf: > > # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help > driftfile /var/lib/ntp/ntp.drift > # Enable this if you want statistics to be logged. > #statsdir /var/log/ntpstats/ > statistics loops...