From what I know, being the server behind a corporate router, it should then have a fixed IP and should be possible to:
In the server side, limit the traffic to the NTP, using the server's firewall, And tunnel the routers firewall for that IP, so that it can only "talked" to that specific NTP
Yes, my server does have a fixed IP. It is also config'd as a VLan (virtual lan? - if that matters - I don't know).
In the server side, limit the traffic to the NTP, using the server's firewall - this should be possible since it is my server (well for my product - server owned and managed by my client).
And tunnel the routers firewall for that IP, so that it can only "talked" to that specific NTP - here, they may have an issue - but I don't understand the (legitimate?) reason why... (cause I am network, router, implication stupid).
Thanks for your input and advice... everything helps - and
SOMETHING has to work!
It is imperative that the clocks be accurate - and they are not right now. Some could be off by seconds - other by days or weeks / months!
The devices are used to record production values (weight amount of product hauled). If product hauled today was time stamped as last week (or even yesterday) - the daily production report (for today) would not include this amount - and my ass will be new mowed grass!!!