And it is not just your own network you need to synchronize to either. With so many networks talking to each other, it is important that all networks synchronize to the same time-scale.

UTC (Coordinated Universal Time) is just such a global timescale. It is controlled by an international constellation of atomic clocks and enables computers all over the world to talk to each other in perfect synchronicity.

But how do you sync to UTC?

The internet is awash with sources of internet time. Most modern operating systems, especially in the Windows flavour, are set up to do this automatically (just by clicking the time/date tab on the clock menu). The computer will then regularly check the time server (usually at Microsoft or NIST, although others can be used) and adjust the computer to ensure its time matches.

Most internet time servers are known as stratum 2 devices. This means they take the time from another device but where does that get the time from?

NTP time servers

The answer is that somewhere on the stratum tree there will be a stratum 1 device. This will be a time server that receives the time direct from an atomic clock source. Often this is by GPS but there are radio referenced alternatives in several countries. These stratum 1 NTP (Network Time Protocol) time servers then provide the stratum 2 devices with the correct time – and its these devices we get our internet time from.

Drawbacks to Internet time

There are several drawbacks to relying on the Internet for time synchronisation. Accuracy is one consideration. Normally, a stratum 2 device will provide ample enough precision for most networks; however, for some users who require high levels of accuracy or deal in a lot of time sensitive transactions a stratum 2 time server may not be accurate enough.

Another problem with internet time servers is that they require an open port in the firewall. Keeping the NTP access on UDP port 123 open all the time could lead to security issues, especially as internet time sources can’t be authenticated or guaranteed.

Using a Stratum 1 NTP Time server

Stratum 1 NTP time servers are easily installed on most networks. Not only will they provide a higher accurate source of time but as they receive the time externally (from GPS or radio) they are highly secure and can’t be hijacked by malicious users or viral software.

Using Internet Time for Computer Synchronization is a post from: Galleon Systems written by Richard N Williams - About the Author: Richard N Williams is a technical author and a specialist in the telecommunications and network time synchronisation industry helping to develop dedicated NTP clocks. Please visit us for more information about NTP or other network time server solutions.

Many of us have been glued to the love football coverage that is being broadcast by a multitude of different broadcasters and TV companies to nearly all countries across the globe.

But nearly all the technologies that enable this mass global live transmission: from the communication satellites that beam the signal across the globe, to the receivers that distribute them to our dishes, cable boxes and aerials.

And with online broadcasting now part and parcel of the whole live sporting event package – accurate time is even more important.

NTP time servers

With signals being bounced from football stadiums to satellites and then to our homes, it is essential that all the technologies involved are synchronised as accurately as possible. Failure to do so could cause the signals to get lost, create interferences or cause a qhole host of other problems.

Most technologies rely on time servers to ensure accuracy and synchronisation. Most time synchronisation servers use the protocol NTP (Network Time Protocol) to distribute time across technology networks.

These devices use a single time source, often acquired from an external atomic clock that is used to set all system clocks on devices to.

Most modern computer networks have a NTP time server that controls the time. These devices are simple to set up and in a modern, global world, are a must have for anybody conscious about accuracy and security (Many security and malicious network attacks are caused due to a lack of synchronisation).

A single NTP time server can keep a network of hundreds and even thousands of machines accurate to within a few milliseconds to the world’s global timescale UTC (Coordinated Universal Time).

The World Cup and the NTP Server is a post from: Galleon Systems written by Richard N Williams - About the Author: Richard N Williams is a technical author and a specialist in the telecommunications and network time synchronisation industry helping to develop dedicated NTP clocks. Please visit us for more information about NTP or other network time server solutions.

Timestamps are the only method that a computer has to establish if an event has occurred, is meant to occur or shouldn’t 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.

However for computer networks that have to communicate with each other, relying in individual system clocks can cause untold problems:

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.

For these reasons, time servers 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 (Network Time Protocol) which is designed to provide a method of synchronising time on a network.

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.

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.

Ensuring the NTP time server 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.

In most parts of the world there are two methods that can provide a secure and reliable source of time:

• GPS time signals
• Radio referenced time signals

GPS signals are available anywhere on the planet and are based on GPS time which is generated by atomic clocks onboard the satellites.

Radio referenced signals like MSF and WWVB are broadcast on long wave from physics laboratories like NIST and NPL.

When Time Servers go Bad is a post from: Galleon Systems written by Richard N Williams - About the Author: Richard N Williams is a technical author and a specialist in the telecommunications and network time synchronisation industry helping to develop dedicated NTP clocks. Please visit us for more information about NTP or other network time server solutions.

While an atomic clock will not lose even a second in time in thousands upon thousands of years, you’re average digital watch will perhaps lose a second in just a few days which after a few weeks or months will mean your watch is running slow or fast by several minutes.

The same can also be said for the system clock that controls your computer the only difference is that computers rely even more heavily on time than we ourselves do.

Nearly everything a computer does is reliant on timestamps, from saving work to performing applications, debugging and even emails are all reliant on timestamps which can be a problem if the clock on your computer is running too fast or slow as errors can quite often occur, especially if you are communicating with another computer or device.

Fortunately, most PCs are easily synchronized to an atomic clock meaning they can be accurate as these powerful time keeping devices so any tasks performed by your PC can be in perfect synchronicity with whatever device you are communicating with.

In most PC operating systems an inbuilt protocol (NTP) allows the PC to communicate with a time server that is connected to an atomic clock. In most versions of Windows this is accessed through the date and time control setting (double clicking the clock in the bottom right).

However, for business machines or networks that require secure and accurate time synchronization, online time servers are just not secure or accurate enough to ensure your network is not vulnerable to security flaws.

However, NTP time servers that receive the time direct from atomic clocks are available that can synchronize entire networks. These devices receive a broadcasted timestamp distributed by either national physics laboratories or via the GPS satellite network.

NTP servers enable entire networks to all have exactly synchronized time which is as accurate and secure as is humanly possible.

Synchronizing a PC to an Atomic Clock is a post from: Galleon Systems written by Richard N Williams - About the Author: Richard N Williams is a technical author and a specialist in the telecommunications and network time synchronisation industry helping to develop dedicated NTP clocks. Please visit us for more information about NTP or other network time server solutions.

Both unintentional interference such as from pirate radio stations or intentional deliberate ‘jamming’ by criminals is still rare but as technology that can hamper GPS signals becomes more readily available, the situation is expected to get worse.

And while the effects of signal failure of the GPS system may have obvious results for people who use it for navigation (ending up in the wrong location or getting lost) it could have more serious and profound repercussions for the technologies that rely on GPS for time signals.

As so many technologies now rely on GPS timing signals from telephone networks, the internet, banking and traffic lights and even our power grid any signal failure no matter how briefly, could cause serious problems.

The main problem with the GPS signal is that it is very weak and as it comes from space bound satellites, little can be done to boost the signal so any similar frequency being broadcast in a local area can easily drown out GPS.

However, GPS is not the only accurate and secure method of receiving the time from an atomic clock source. Many national physics laboratories from across the globe broadcast atomic clock signals via radio waves (usually long wave). In the USA these signals are broadcast by NIST (National Institute for Standards and Time (known as WWVB) whilst in the UK, it’s MSF signal is broadcast by NPL (National Physical Laboratory).

Dual time servers that can receive both signals are available and are a safer bet for any high technology company that can’t afford to risk losing a time signal.

The Vulnerability of GPS is a post from: Galleon Systems written by Richard N Williams - About the Author: Richard N Williams is a technical author and a specialist in the telecommunications and network time synchronisation industry helping to develop dedicated NTP clocks. Please visit us for more information about NTP or other network time server solutions.

• Be vulnerable to malicious attacks
• Susceptible to data loss
• Unable to conduct time sensitive transactions
• Difficult to debug

Fortunately ensuring a computer network is accurately synchronized is relatively straight forward. There different methods of synchronizing a network to the global timescale UTC (Coordinated Universal Time) but occasionally some common issues do arise.

My dedicated time server is unable to receive a signal

Dedicated NTP time servers receive the time from either long wave transmissions or GPS networks. If using a GPS NTP server then a GPS antenna needs to be situated on a roof to obtain a clear view of the sky. However, a NTP radio receiver does not need a roof mounted aerial although the signal can be vulnerable to interference and the correct angle toward the transmitter should be attained.

I AM using a public time server across the Internet but my devices are not synchronised.

As public time servers can be used by anyone they can receive high levels of traffic. This can cause problems with bandwidth and mean that your time requests can’t get through. Public NTP servers can also fall victim to DDoS attacks and some high profile incidents of NTP vandalism have occurred.

Internet time servers are also stratum 2 devices, in other words they themselves have to connect to a time server to receive the correct time and because of this some online time references are wildly inaccurate.

*NB – internet time servers are also incapable of being authenticated to allow NTP to establish if the time source is coming from where it claims to be, combined with the problem of ensuring the firewall is open to receive the time requests, can mean that internet time servers present a clear risk to security.

The time on my computer seems to be off by a second to standard UTC time

You need to check if a recent leap second has been added to UTC. Leap seconds are added once or twice a year to ensure UTC and the Earth’s rotation match. Some time servers experience difficulties in making the leap second adjustment.

Common Issues in Time Synchronisation is a post from: Galleon Systems written by Richard N Williams - About the Author: Richard N Williams is a technical author and a specialist in the telecommunications and network time synchronisation industry helping to develop dedicated NTP clocks. Please visit us for more information about NTP or other network time server solutions.

But atomic clocks are not practical pieces of equipment to have around the office or home. They are bulky, expensive and require laboratory conditions to operate effectively. But making use of an atomic clock is straightforward enough especially as atomic time keepers like NIST (National Institute of Standards and Time) and NPL (National Physical Laboratory) broadcast the time as told by their atomic clocks on short wave radio.

NIST transmits its signal, known as WWVB from Boulder, Colorado and it is broadcast on an extremely low frequency (60,000 Hz). The radio waves from WWVB station can cover all of the continental United States plus much of Canada and Central America.

The NPL signal is broadcast in Cumbria in the UK and it is transmitted along similar frequencies. This signal, known as MSF is available throughout most of the UK and similar systems are available in other countries such as Germany, Japan and Switzerland.

Radio controlled atomic clocks receive these long wave signals and correct themselves according to any drift the clock detects. Computer networks also take advantage of these atomic clocks signals and use the protocol NTP (Network Time Protocol) and dedicated NTP time servers to synchronise hundreds and thousands of different computers.

Radio Controlled Clocks – Atomic Clocks on Shortwave is a post from: Galleon Systems written by Richard N Williams - About the Author: Richard N Williams is a technical author and a specialist in the telecommunications and network time synchronisation industry helping to develop dedicated NTP clocks. Please visit us for more information about NTP or other network time server solutions.

Atomic clocks use the unchanging resonance of atoms during different energy states to measure time providing an atomic tick that occurs nearly 9 billion times a second in the case of the caesium atom. In fact the resonance of caesium is now the official definition of a second having been adopted by the International System of Unit (SI).

Atomic clocks are the base clocks used for the international time, UTC (Coordinated Universal Time). And they also provide the basis for NTP servers to synchronise computer networks and time sensitive technologies such as those used by air traffic control and other high level time sensitive applications.

Finding an atomic clock source of UTC is a simple procedure. Particularly with the presence of online time sources such as those provided by Microsoft and the National Institute for Standards and Time (windows.time.com and nist.time.gov).

However, these NTP servers are what are known as stratum 2 devices that mean they are connected to another device which in turn gets the time from an atomic clock (in other words a second-hand source of UTC).

While the accuracy of these stratum 2 servers is unquestionable, it can be affected by the distance the client is from the time servers, they are also outside the firewall meaning that any communication with an online time server requires an open UDP (User Datagram Protocol) port to allow the communication.

This can cause vulnerabilities in the network and are not used for this reason in any system that requires complete security. A more secure (and reliable) method of receiving UTC is to use a dedicated NTP time server. These time synchronisation devices receive the time direct from atomic clocks either broadcast on long wave by places like NIST or NPL (National Physical Laboratory – UK). Alternatively UTC can be derived from the GPS signal broadcast by the constellation of satellites in the GPS network (Global Positioning System).

Atomic Clocks – the Key to Network Synchronisation is a post from: Galleon Systems written by Richard N Williams - About the Author: Richard N Williams is a technical author and a specialist in the telecommunications and network time synchronisation industry helping to develop dedicated NTP clocks. Please visit us for more information about NTP or other network time server solutions.

There is a certain irony that the computer that sits on your desktop and may have cost as much as month’s salary will have a clock onboard that is less accurate than a cheap wristwatch bought at a petrol or gas station.

The problem is not that computers are in particularly made with cheap timing components but that any serious timekeeping on a PC can be achieved without expensive or advanced oscillators.

The onboard timing oscillators on most PCs are in fact just a back up to keep the computer clock synchronised when the PC is off or when network timing information is unavailable.

Despite these inadequate onboard clocks, timing on a network of PC’s can be achieved to within millisecond accuracy and a network that is synchronised to the global timescale UTC (Coordinated Universal Time) shouldn’t drift at all.

The reason this high level of accuracy and synchronicity can be achieved without expensive oscillators is that computers can use Network Timing Protocol (NTP) to find and maintain the exact time.

NTP is an algorithm that distributes a single source of time; this can be generated by the onboard clock of a PC – although this would see every machine on the network drift as the clock itself drifts – A far better solution is to use NTP to distribute a stable, accurate source of time, and most preferably for networks that conduct business across the internet, a source of UTC.

The simplest method of receiving UTC – which is kept true by a constellation of atomic clocks around the globe – is to use a dedicated NTP time server. NTP servers use either GPS satellite signals (Global Positioning System) or long wave radio broadcasts (usually transmitted by national physics laboratories like NPL or NIST).

Once received the NTP server distributes the timing source across the network and constantly checks each machine for drift (In essence the networked machine contacts the server as a client and the information is exchanged via TCP/IP.

This makes the onboard clocks of the computers themselves obsolete, although when the machines are initially booted up, or if there has been a delay in contacting the NTP server (if it is down or there is a temporary fault), the onboard clock is used to maintain time until full synchronisation is again achievable.

Network Time Protocol – When Time Matters is a post from: Galleon Systems written by Richard N Williams - About the Author: Richard N Williams is a technical author and a specialist in the telecommunications and network time synchronisation industry helping to develop dedicated NTP clocks. Please visit us for more information about NTP or other network time server solutions.

The inclusion of these automatic synchronisation tools on the latest operating systems is an indication of how important timing information has become and when you consider the types of applications and transactions that are now conducted on the internet it is of no surprise.

Internet banking, online reservations, internet auctions and even email can be reliant on accurate time. Computers use timestamps as the only point of reference they have to identify when and if a transaction has occurred. Mistakes in timing information can cause untold errors and problems, particularly with debugging.

The internet is full of time servers with over a thousand time sources available for online synchronisation however; the accuracy and usefulness of these online sources of UTC time do vary and leaving a TCP/IP open in the firewall to allow the timing information through can leave a system vulnerable.

For network systems where timing is not only crucial but where security is also a paramount issue then the internet is not a preferred source for receiving UTC information and an external source is required.

Connecting a NTP network to an external source of UTC time is relatively straightforward if a network time server is used. These devices that are often referred to as NTP servers, use the atomic clocks onboard GPS (Global Positioning System) satellites or long wave transmissions broadcast by places such as NIST or NPL.

Time Servers and the Internet is a post from: Galleon Systems written by Richard N Williams - About the Author: Richard N Williams is a technical author and a specialist in the telecommunications and network time synchronisation industry helping to develop dedicated NTP clocks. Please visit us for more information about NTP or other network time server solutions.