But I don't use DHCP, and on my system, Windows sends a request to the
PDC, but according to what I see in the TCP dump, it doesn't respond. It
started responding when I applied your workaround. I noticed that when I
applied your workaround, Windows doesn't send a "Message Authentication
Code" in the request. Chrony should support "Message Authentication
Code"
W dniu 18.01.2025 o?12:58, Rowland Penny via samba
pisze:> On Sat, 18 Jan 2025 12:51:02 +0100
> Programnet via samba <samba at lists.samba.org> wrote:
>
>> It actually worked. But this seems to be a workaround for the
>> problem. I noticed that in this configuration, Windows does not send
>> the "Message Authentication Code" to the Chrony server.
>>
>> Without your proposed solution implemented, Windows also sends a
>> request to Chrony, but Chrony does not respond.
>>
> I know I supplied a workaround, the proper fix is to use a GPO to get
> the clients to use the pdc_emulator as their timeserver, I suggest you
> search the internet for more information.
>
> This isn't a Samba, Chrony or DHCP problem, Linux can easily use
> timeservers supplied via dhcp, Windows, seemingly, cannot.
>
> Rowland
>