Hi,

once I setup a NTP server on a hAP ac (tried v6.49 with ntp package and v7.1rc6), Windows Time Service (Windows 10 21H1) does not sync and throws an error, in UI and in cmd line with w32tm /resync. This persists also after restart of router and client.
A call with w32tm however works immediately after setup: Only after some time (~4 hours), the service syncs without issues.

Since I need to do this quite often, does anybody have an explanation/workaround for this weird behavior?

Thanks,
Daniel

Check status of NTP client on your Mikrotik. NTP server won't give out usable data unless client's status is "synchronized" and it is normal for NTP client (any, not only ROS) to become synchronized only after some (tens of) minutes after restart. Can take longer if device doesn't have RTC or if its time is not correct (AFAIK most if not all MT devices lack RTC).

Windows time client has its own gotchas ...