shouldbeq931 at gmail.com
Mon Aug 3 14:28:53 UTC 2020
On Sun, Aug 2, 2020 at 1:54 PM maurizio--- via users <users at ntpsec.org> wrote:
> Dear all,
> I've got an issue trying to use NTPsec to sync the clock of WIN machines
> to a DC running on a Raspberry PI-4.
> NTPsec works normally without the "mssntp" keyword; by this I mean that
> it sync to external NTP servers, disciplines the local clock, and acts
> as a local server for non-authenticathed clients. But if I add the
> "mssntp" keyword it stops answer to clients while it continues to
> disciplines the local clock to NTP servers.
> The logs do not show anything related to this issue, so I'm really
Windows will sync directly from most NTP servers
Enable the time service.
Configure the time service
w32tm /config /manualpeerlist:"ntp1.local.domain ntp2.local.dommain"
More information about the users