On Sun, 8 Feb 2026 09:41:17 +0100 Franta Hanzlík <[email protected]> wrote:
> I have chronyd running on Debian 12/Samba AD DC as NTP server for LAN > clients (mainly Windows 10/Windows 11). Chronyd itself is synced from > other ntpsec daemons on Linux machines in LAN without problems, timesync > on Linux clients with chrony as NTP client is also without problems. > > What doesn't work is the time synchronization of Windows clients. > Monitoring port 123 with tcpdump at this AD DC machine shows incoming > NTP request, but there is no response to it. > Chronyd Logging/debugging possibilities seems be very limited, in log > are not any info about interaction with clients. > ... > -- Ach, in chrony-users maillist archive at mail-archive.com I now see mail from Virgo Pärna, Feb 19 2025, which describe IMO same problem I have, with same scenario/configuration as mine. (I must have missed this thread before, while searching the tuxfamily.org archive). Sorry for duplicate question, I will continue search on Samba signing side. But - I would still like to know - is it possible to somehow increase the logging level on the chronyd side so that these problems can be read from there? That would be a significant help in troubleshooting... (now I have nothing in the system log except for a few lines from the chronyd startup) -- Thanks in advance, Franta Hanzlik -- To unsubscribe email [email protected] with "unsubscribe" in the subject. For help email [email protected] with "help" in the subject. Trouble? Email [email protected].
