{"id":711,"date":"2010-05-01T15:10:17","date_gmt":"2010-05-01T15:10:17","guid":{"rendered":"https:\/\/galsys.co.uk\/news\/?p=711"},"modified":"2018-05-08T13:16:47","modified_gmt":"2018-05-08T13:16:47","slug":"when-time-servers-go-bad","status":"publish","type":"post","link":"https:\/\/www.galsys.co.uk\/news\/when-time-servers-go-bad\/","title":{"rendered":"When Time Servers go Bad"},"content":{"rendered":"

\u201cTime is what prevents everything from happening at once,\u2019 said eminent physicist John Wheeler<\/a>. And when it comes to computers his words couldn\u2019t be any more relevant.<\/p>\n

Timestamps are the only method that a computer has to establish if an event has occurred, is meant to occur or shouldn\u2019t be occurring just yet. For a home PC, the computer relies on the inbuilt clock that displays the time on the corner of your operating system, and for most home uses this is satisfactory enough.<\/p>\n

However for computer networks that have to communicate with each other, relying in individual system clocks can cause untold problems:<\/p>\n

All clocks drift, and computer clocks are no different and problems occur when two machines are drifting at different rates as the time does not match up. This poses a conundrum for a computer as it is unsure of which time to believe and time critical events can fail to occur and even simple tasks like sending an email can cause time confusion on a network.<\/p>\n

For these reasons, time servers<\/a> are commonly used to receive the time from an external source and distribute it around the network. Most of these devices use the protocol NTP<\/a> (Network Time Protocol) which is designed to provide a method of synchronising time on a network.<\/p>\n

However, time servers are only as good as the time source that they rely on and when there is a problem with that source, synchronisation will fail and the problems mentioned above can occur.<\/p>\n

The most common cause for time server failure or inaccuracy is the reliance on internet based sources of time. These can neither be authenticated by NTP nor guaranteed to be accurate and they can also lead to security issues with firewall intrusion and other malicious attacks.<\/p>\n

Ensuring the NTP time server<\/a> continues to get a source of highly accurate time is fairly straight forward and is all a matter of choosing an accurate, reliable and secure time source.<\/p>\n

In most parts of the world there are two methods that can provide a secure and reliable source of time:<\/p>\n