Daniel Müller
2024-Feb-16 13:20 UTC
[Samba] samba 4.19 Windows 11 clients Time sync problem
Dear all,
We just have a samba 4.19 domain running. And what i recognized ist hat some
windows 10/11 clients does not sync time with the dc. The time is not the
real time as on the dc, about 10 minutes back or several minutes in the
future.
Is this a bug or did spmething chance in the behaviour of samba?
My ntp.conf/ Debian11:
driftfile /var/lib/ntp/ntp.drift
server 127.127.1.0
fudge 127.127.1.0 stratum 10
leapfile "/usr/share/zoneinfo/leap-seconds.list"
ntpsigndsocket /var/lib/samba/ntp_signd <--- rights are set
listen xxx.xxx.xxx.xxx
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
pool 0.debian.pool.ntp.org iburst
pool 1.debian.pool.ntp.org iburst
pool 2.debian.pool.ntp.org iburst
pool 3.debian.pool.ntp.org iburst
restrict -4 default kod notrap nomodify nopeer noquery mssntp
restrict -6 default kod notrap nomodify nopeer noquery mssntp
restrict 127.0.0.1
restrict ::1
restrict source notrap nomodify noquery
ntp is working:
root at dommaster:~# ntpq -p
remote refid st t when poll reach delay offset
jitter
============================================================================
LOCAL(0) .LOCL. 10 l 39d 64 0 0.000 +0.000
0.000
0.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000
0.000
1.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000
0.000
2.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000
0.000
3.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000
0.000
+mx.ae9.eu 237.17.204.95 2 u 1578 1024 352 27.597 -0.442
4.748
*178.215.228.24 36.224.68.195 2 u 1616 1024 316 18.896 -1.582
1.654
+time.cloudflare 10.97.8.67 3 u 1859 1024 236 19.943 -2.323
1.808
+mail.kpprs.de 185.248.189.10 2 u 757 1024 137 24.486 -1.520
1.706
+httphost1.skyte 131.188.3.220 2 u 1478 1024 236 26.967 -1.293
2.372
root at dommaster:~# service ntp restart
root at dommaster:~# ntpq -p
remote refid st t when poll reach delay offset
jitter
============================================================================
LOCAL(0) .LOCL. 10 l 2 64 1 0.000 +0.000
0.000
0.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000
0.000
1.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000
0.000
2.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000
0.000
3.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000
0.000
Greetings
Daniel
Luis Peromarta
2024-Feb-16 17:00 UTC
[Samba] samba 4.19 Windows 11 clients Time sync problem
Hi there. A few NTP experts around here lately. We need more info. Distro, and wether your are using NTP (nrpsec) or Chrony. Regards. LP On 16 Feb 2024 at 14:37 +0100, Daniel M?ller via samba <samba at lists.samba.org>, wrote:> Dear all, > > We just have a samba 4.19 domain running. And what i recognized ist hat some > windows 10/11 clients does not sync time with the dc. The time is not the > real time as on the dc, about 10 minutes back or several minutes in the > future. > Is this a bug or did spmething chance in the behaviour of samba? > > My ntp.conf/ Debian11: > driftfile /var/lib/ntp/ntp.drift > > server 127.127.1.0 > fudge 127.127.1.0 stratum 10 > leapfile "/usr/share/zoneinfo/leap-seconds.list" > > ntpsigndsocket /var/lib/samba/ntp_signd <--- rights are set > listen xxx.xxx.xxx.xxx > statistics loopstats peerstats clockstats > filegen loopstats file loopstats type day enable > filegen peerstats file peerstats type day enable > filegen clockstats file clockstats type day enable > pool 0.debian.pool.ntp.org iburst > pool 1.debian.pool.ntp.org iburst > pool 2.debian.pool.ntp.org iburst > pool 3.debian.pool.ntp.org iburst > restrict -4 default kod notrap nomodify nopeer noquery mssntp > restrict -6 default kod notrap nomodify nopeer noquery mssntp > restrict 127.0.0.1 > restrict ::1 > restrict source notrap nomodify noquery > > ntp is working: > root at dommaster:~# ntpq -p > remote refid st t when poll reach delay offset > jitter > ===========================================================================> => LOCAL(0) .LOCL. 10 l 39d 64 0 0.000 +0.000 > 0.000 > 0.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000 > 0.000 > 1.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000 > 0.000 > 2.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000 > 0.000 > 3.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000 > 0.000 > +mx.ae9.eu 237.17.204.95 2 u 1578 1024 352 27.597 -0.442 > 4.748 > *178.215.228.24 36.224.68.195 2 u 1616 1024 316 18.896 -1.582 > 1.654 > +time.cloudflare 10.97.8.67 3 u 1859 1024 236 19.943 -2.323 > 1.808 > +mail.kpprs.de 185.248.189.10 2 u 757 1024 137 24.486 -1.520 > 1.706 > +httphost1.skyte 131.188.3.220 2 u 1478 1024 236 26.967 -1.293 > 2.372 > root at dommaster:~# service ntp restart > root at dommaster:~# ntpq -p > remote refid st t when poll reach delay offset > jitter > ===========================================================================> => LOCAL(0) .LOCL. 10 l 2 64 1 0.000 +0.000 > 0.000 > 0.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000 > 0.000 > 1.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000 > 0.000 > 2.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000 > 0.000 > 3.debian.pool.n .POOL. 16 p - 64 0 0.000 +0.000 > 0.000 > > Greetings > Daniel > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
On Fri, Feb 16, 2024 at 8:38?AM Daniel M?ller via samba <samba at lists.samba.org> wrote:> We just have a samba 4.19 domain running. And what i recognized ist hat some > windows 10/11 clients does not sync time with the dc. The time is not the > real time as on the dc, about 10 minutes back or several minutes in the > future.I had one system that previously used a different time server via a GPO, but for some reason didn't start using the DC for NTP once the GPO was removed and I had to reset its time service. Do this in an elevated prompt: =========================net stop w32time w32tm /unregister w32tm /register net start w32time ========================= Chris