Ok, so ntpsec in bookworm has issues ntp_signd. That explains, why it stopped totally working. Now remaining issue is, why chrony did not respond time requests without registry change in windows side. Unfortunately Debian chrony is without debug log support. I'll try this specific issue with chrony mailing list also. -- Virgo P?rna virgo.parna at mail.ee
Some notes I?ve compiled over the years. With troubleshooting http://samba.bigbird.es/doku.php?id=samba:install-chrony On 19 Feb 2025 at 11:50 +0000, Virgo P?rna via samba <samba at lists.samba.org>, wrote:> Ok, so ntpsec in bookworm has issues ntp_signd. That explains, why it > stopped totally working. > Now remaining issue is, why chrony did not respond time requests > without registry change in windows side. Unfortunately Debian chrony is > without debug log support. > I'll try this specific issue with chrony mailing list also. > > > -- > Virgo P?rna > virgo.parna at mail.ee > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
On 19.02.2025 13:50, Virgo P?rna via samba wrote:> ????Ok, so ntpsec in bookworm has issues ntp_signd. That explains, why > it stopped totally working. > ????Now remaining issue is, why chrony did not respond time requests > without registry change in windows side. Unfortunately Debian chrony is > without debug log support. > ????I'll try this specific issue with chrony mailing list also. > >And feedback from Chrony list was, that it seems, that Windows was using "extended MS-SNTP authenticator", that they think is not supported by samba... After registry change it used classic MS-SNTP authenticator requests. -- Virgo P?rna virgo.parna at mail.ee