[Samba] Time synchronization problem. Chrony, ntp
Peter Milesson
miles at atmos.eu
Mon Jan 20 15:09:51 UTC 2025
On 20.01.2025 15:14, Sonic via samba wrote:
> On Mon, Jan 20, 2025 at 5:53 AM Rowland Penny via samba <
> samba at lists.samba.org> wrote:
>
>> I cannot get Chrony to work with MS-SNTP from a Windows client, now
>> this could be a Samba problem....
>>
> The reason I think it's a Samba issue is that it worked perfectly with
> 4.19.3 but no longer works with 4.21.1 (or 4.21.3).
> I guess it is possible that all of the Windows' systems were updated to
> some unworkable state but it would take setting up a test case with 4.19.3
> to verify. I did try starting up an old copy at one site but the systems
> wouldn't let me logon, most likely the secrets changed and I didn't want to
> mess anything up further.
Hi Sonic,
I have tested with Windows 7 Pro (SP1), Windows 10 Pro (22H2), and
Windows 11 Pro (24H2). All those clients report CMOS clock as time
source. I also suspect that something broke in Samba since I posted
about this problem on 9 August 2023. Then I was using Samba 4.17.9,
which worked when I switched from ntpsec to chrony.
Maybe I will try to set up a test domain and install a DC from Bookworm,
without backports. That will be Samba 4.17.12. The Windows 7 client
should probably work with that one. The latest Windows 10 and 11, will
probably not work, due to several changes since then. But that will
probably have to wait until the weekend.
Best regards,
Peter
More information about the samba
mailing list