4 ms·
I've got equipment racks that haven't been connected to a network in years. It's absolutely obnoxious when everything is a few minutes off from eachother. I jus
by moftz 5y ago
I've got equipment racks that haven't been connected to a network in years. It's absolutely obnoxious when everything is a few minutes off from eachother. I just figured out how to set up one Windows box as an NTP server to keep everything else sane. The time doesn't have to be exactly right but it just needs to be consistent across everything. It's very confusing when a log file has a creation timestamp inside from one machine that is widely off from the Date Created timestamp on the network drive. We've got a nice rubidium source for the test equipment but I don't have any way to feed that to a Windows box.
- evv555 5y agoIn my case it was Active Directory having the time service fall into a bad state and propagating throughout the system. AWS instances don't have a proper clock and will fall out of sync by minutes within a day. Installing Meinberg's NTP works better than Windows Time out of the box.
- newman314 5y agoWindows 10 has improvements for time accuracy but has strict requirements for achieving them. See https://docs.microsoft.com/en-us/windows-server/networking/windows-time-service/support-boundary https://docs.microsoft.com/en-us/windows-server/networking/w...