Why is my NTP server returning wrong time

I’m back on this issue.. Set date & time

apparently something is wrong. I am able to set the CPU date and time to a specific date, and this is correctly displayed by AS (note that I set as date 11th of november and a random time):

I also enabled NTP server in the cpu configuration:

but still it does not work!

when a client connects to the ntp server the connection is ok, but the returned date and time is another one!

This is the result on the client.

that corresponds to 04:51 of the 6th of november.

what am I doing wrong??

I tried also with a lower stratum (as noted on another thread) but the problem persists.

thanks

I found the answer, I post it here if it can be helpful. the problem was the timezone difference.

Since on the CPU I left the default value (GMT) while on the client for some strange reason there was a timezone set to GMT + 8, the visualization had the reported offset, which is the difference between the 2 timezones.

Regarding the wrong date: I noticed that if the set date is too far from the current one set on windows, it has some issues with the sync. so I had to manually force it with

w32tm /resync /force

2 Likes

Although this is “solved” I would like to mention that your NTP server is running a “stratum” of 14 which is really a high number

The straum defines the accuracy of a NTP servers time. 14 is probably way to high for any NTP client. Try to set it to 3 and I might think that the client will probably accept the time

best regards

Oliver

thanks for your feedback Oliver! As I mentioned above I had already tried with lower stratum values but the sync problem still persisted if the set date was too far from the current one set on windows..

Which is rather strage tbh but thanks for clearing that