Category: NTP configuration

Synchronising Computer Networks to an Atomic Clock

  |   By

Atomic clocks are well-known for being accurate. Most people may never have seen one but are probably aware that atomic clocks keep highly precise time. In fact modern atomic clock will keep accurate time and not lose a second in one hundred million years.

This amount of precision may seem overkill but a multitude of modern technologies rely on atomic clocks and require such a high level of precision. A perfect example is the satellite navigation systems now found in most auto cars. GPS is reliant on atomic clocks because the satellite signals used in triangulation travel at the speed of light which in a single second can cover nearly 100,000 km.

So it can be seen how some modern technologies rely on this ultra precise timekeeping from atomic clocks but their use doesn’t stop there. Atomic clocks govern the world’s global timescale UTC (Coordinated Universal Time) and they can also be used to synchronise computer networks too.

It may seem extreme to use this nanosecond precision to synchronise computer networks too but as many time sensitive transactions are conducted across the internet with such trades as the stock exchange where prices can fall or rise each and every second it can be seen why atomic clocks are used.

To receive the time from an atomic clock a dedicated NTP server is the most secure and accurate method. These devices receive a time signal broadcast by either atomic clocks from national physics laboratories or direct from the atomic clocks onboard GPS satellites.

By using a dedicated NTP server a computer network will be more secure and as it is synchronised to UTC (the global timescale) it will in effect be synchronised with every other computer network using a NTP server.

The World in Synchronisation

  |   By

Time synchronisation plays an ever more important role in the modern world with more and more technologies reliant on accurate and reliable time.

Time synchronisation is not just important but can also be crucial in the safe running of systems such as air traffic control that simply couldn’t function without accurate synchronisation. Think of the catastrophes that could happen in the air of aircraft were out of synchronisation with each other?

In global commerce too accurate and reliable time synchronisation is highly important. When the world’s stock markets open in the morning and traders from across the world buy stock on their computers. As stock fluctuates second by second if machines are out of synchronisation it could cost millions.

But synchronisation is also imperative in modern computer networking; it keeps systems secure and enables proper control and debugging of systems. Even if a computer network is not involved in any time sensitive transactions a lack of synchronisation can leave it vulnerable to malicious attacks and can also be susceptible to data loss.

Accurate synchronisation is possible in computer networking thanks to two developments: UTC and NTP.

UTC is a timescale -coordinated universal time, it is based on GMT but is controlled by an array of atomic clocks making it accurate to within a few nanoseconds.

NTP is a software protocol – Network Time Protocol, designed to accurately synchronise computer networks to a single time source. Both of these implementations come together in a single device which is relied upon the world over to synchronise computer networks – the NTP server.

An NTP time server or network time server is a device that receives the time from an atomic clock, UTC source and distributes it across a network. Because the time source is continually checked by the time server and is from an atomic clock it makes the network accurate to within a few milliseconds of UTC providing synchronisation on a global scale.

The Clocks to Spring Forward at the Weekend

  |   By

It’s that time of year again when we lose an hour over the weekend as the clocks go forward to British Summer Time. Twice a year we alter the clocks but in an age of UTC (Coordinated Universal Time) and time server synchronisation is it really necessary?

The changing of the clocks is something that was discussed just before World War I when London builder William Willet suggested the idea as a way of improving the nation’s health (although his initial idea was to advance the clocks twenty minutes on each Sunday in April).

His idea wasn’t taken up although it sowed the seed of an idea and when the First World War erupted it was adopted by many nations as a way to economise and maximise daylight although many of these nations discarded the concept after the war, several including the UK and USA kept it.

Daylight saving has altered over the years but since 1972 it has remained as British Summer Time (BST) in the summer and Greenwich Meantime in the winter (GMT). However, despite is use for nearly a century the changing of the clocks remains controversial. For four years Britain experimented without daylight changing but it was proved unpopular in Scotland and the North where the mornings were darker.

This timescale hopping does cause confusion (I for one will miss that hour extra in bed on Sunday) but as the world of commerce adopts the global civil timescale (which fortunately is the same as GMT as UTC is adjusted with leap seconds to ensure GMT is unaffected by the slowing of the Earth’s rotation) is it still necessary?

The world of time synchronisation certainly doesn’t need to adjust for daylight saving. UTC is the same the world over and thanks to devices such as the NTP server can be synchronised so the entire world runs the same time.

NTP Synchronization and FAQ

  |   By

With a variety of acronyms and timescales the world of time synchronisation can be quite confusing here are some frequently asked questions we hope will help enlighten you.

What is NTP?

NTP is a protocol designed to synchronize computer networks across the internet or LAN (Local Area Networks). It is not the only time synchronization protocol available but it is the most widely used and the oldest having been conceived in the late 1980’s.

What are UTC and GMT?

UTC or Coordinated Universal Time is a global timescale, it is controlled by highly accurate atomic clocks but kept the same as GMT (Greenwich Meantime) by the use of leap seconds, added when the Earth’s rotation slows down. Strictly speaking GMT is the old civil timescale and based on when the sun is above the meridian line, however, as the two systems are identical in time thanks to leap seconds, UTC is often referred to as GMT and vice versa.

And a NTP Time Server?

These are devices that synchronize a computer network to UTC by receiving a time signal and distributing it with the protocol NTP which ensures all devices are running accurately to the timing reference.

Where to get UTC time from?

There are two secure methods of receiving UTC. The first is to utilize the long wave time signals broadcast by NIST (WWVB) NPL in the UK (MSF) and the German NPL (DCF) The other method is to use a the GPS network. GPS satellites broadcast an atomic clock signal that can be utilised and converted to UTC by the GPS NTP server.

The Hidden Cost of Free Time

  |   By

If you are reading this then you are probably aware of the importance time plays in IT systems and computer networks. Most computer administrators appreciate that precise time and accurate synchronisation are an important aspect of keeping a computer network error free and secure.

And yet, despite its importance many network administrators still rely on the Internet as a source of UTC time for their networks (UTC – Coordinated Universal Time), primarily because they see it as a quick and more importantly a free method of time synchronisation.

However, the drawbacks in using these free services may cost a lot more than the money saved on a dedicated NTP time server.

NTP (Network Time Protocol) is now present on nearly all computers and it is NTP that is used to synchronise computer systems. However, if an Internet time source is used then the source is outside the network firewall and this creates a serious vulnerability. Any external time source will require a port to be left open in the firewall to allow the time information packets through and this opening is too easy a way to exploit a network which can become victim to a DDOS attack (Distributed Denial of Service) or even allow malicious programmes through to take control of the machines themselves.

Another problem is the availability of stratum 1 time sources across the internet. Most online time sources come from stratum 2 time servers. These are devices that receive the time from a time server (stratum 1) that originally gets the information from an atomic clock (stratum 0).  While stratum 2 devices can be just as accurate as stratum 1 time servers, across the internet without NTP authentication the actual accuracy can not be guaranteed.

Furthermore, internet time sources have never been considered accurate or precise with surveys showing over half being inaccurate by over a second and the rest dependent on the distance from client as to whether they can provide any useful accuracy. Even organisations such as NIST publish  advisory notices on their time server pages about it unable to guarantee security or accuracy and yet millions of networks are still receiving time from across the internet.

With the decline in cost of dedicated radio referenced NTP time servers or GPS NTP server there has never been a better time to get one. And when you consider the cost of a computer breach or crashed network the NTP server will have paid for itself many times over.

Step by Step Installing A Dedicated NTP Time Server

  |   By

A time server is a crucial piece of kit for any network. Time synchronisation is imperative in keeping a network secure and reliable. Time synchronisation, however, need not be the headache many administrators assume it is going to be.

Most of the difficulties of time synchronisation have been taken care of thanks to the protocol NTP (Network Time Protocol). Whilst NTP is not the only time synchronisation software available it is by far the most widely used (due mainly to the fact that it has been around since the 1980’s and is still being developed today).

NTP uses a single time source and distributes it from machine-to-machine checking each PC or device for drift then adjusting for it. NTP is normally installed on Windows and Linux systems (or at least a simplified version called SNTP) although it is freely downloadable from the NTP homepage. While NTP can quite easily receive any time source from the Internet this can cause major security issues no to mention a lack of accuracy that many online NTP servers suffer from.

The most accurate and secure method is to use an external network time server as these sit within the firewall. They also receive a UTC (Coordinated Universal Time) reference direct from an atomic clock which makes them stratum 1 devices. Most internet time servers are stratum 2 servers. NTP uses strata to define how far away a server is from the source so an atomic clock is a stratum 0 device while a computer that receives time direct from a NTP server becomes a stratum 2 device and so on.

The only decision that really needs to be made when installing a dedicated NTP time server is which time reference is best. There are two main methods of receiving a secure, accurate and authenticated UTC time reference; the GPS network (Global Positioning System) or national physics laboratories long wave radio transmissions.

The latter system is not available in every country although the USA, UK and Germany have strong signals known as WWVB, MSF and DCF respectively. These can often be picked up outside the borders of these countries although the signals are vulnerable to interference, outages and local topography.

A GPS NTP server system is less vulnerable to these things and as long as there is a clear view of the sky (such as a rooftop or open window) the GPS time signal can be picked up anywhere on the globe.

Using Time and Frequency Transmissions to Synchronise a Computer Network

  |   By

Computer network synchronisation is often perceived as a headache for many system administrators but keeping accurate time is essential for any network to remain secure and reliable. Failing to have an accurate synchronised network can lead to all sorts of errors when dealing with time sensitive transactions.

The protocol NTP (Network Time Protocol) is the industry standard for time synchronisation. NTP distributes a single time source to an entire network ensuring all machines are running the exact same time.

One of the most problematic areas in synchronising a network is in the selection of the time source. Obviously if you are spending time getting a network synchronised then the time source would have to be a UTC (Coordinated Universal Time) as this is the global timescale used by computer networks all over the world.

UTC is available across the internet of course but internet time sources are not only notoriously inaccurate but using the internet as a time source will leave computer system open to security threats as the source is external to the firewall.

A far better and secure method is to use a dedicated NTP time server. The NTP server sits inside the firewall and can receive a secure time signal from highly accurate sources. The most commonly used these days is the GPS network (Global Positioning System) this is because the GPS system is available literally anywhere on the planet. Unfortunately it does require a clear view of the sky to ensure the GPS NTP server can ‘see’ the satellite.

There is another alternative however, and that is to use the national time and frequency transmissions broadcast by several national physics laboratories. These have the advantage in that being long wave signals they can be received indoors. Although it must be noted these signals are not broadcast in every country and the range is finite and susceptible to interference and geographical features.

Some of the main transmissions broadcast are known as: the UK’s MSF signal, Germany’s DCF-77 and the USA’s WWVB.

Using GPS to Synchronise Network Time

  |   By

The global positioning system has been around since the 1980’s. It was designed and built by the United States Military who wanted an accurate positioning system for battlefield situations. However, following the accidental shooting down or a Korean airliner, the then US president (Ronald Reagan) agreed that the system should be allowed to be used by civilians as a way of preventing such a disaster from occurring again.

From then on the system has broadcast in to two frequencies L2 for the US Military and L1 for civilian use. The system works by using ultra precise atomic clocks that are on board each satellite. The GPS transmission is a timecode produced from this clock combined with information such as the position and velocity of the satellite. This information is then picked up by the satellite navigation receiver that calculates how long the message took to reach it and therefore how far from the satellite it is.

By using triangulation (use of three of these signals) the exact position on Earth of the GPS receiver can be ascertained. Because the speed of the transmissions, like all radio signals, travels at the speed of light it is highly important that the GPS clocks are ultra-precise. Just one second of inaccuracy is enough to make the navigational unit inaccurate to over 100,000 miles as light can travel such vast distances in such a short space of time.

Because GPS clocks have such a high level of accuracy it means they also have another use. The GPS signal, being available anywhere on the planet, is a highly efficient means of getting a time signal to synchronise a computer network too. A dedicated GPS time server will receive the GPS signal then convert the atomic time signal from it (known as GPS time) and convert it to UTC (Coordinated Universal Time) which is simple to do as both timescales are based on International Atomic Time (TAI) and the only difference being GPS time does not account for leap seconds meaning it is ‘exactly’ 15 seconds faster.

A GPS time server will most likely use the protocol NTP (Network Time Protocol) to distribute the time to a network. NTP is by far the most commonly used network time protocol and is installed in most dedicated time servers and a version is also included in most Windows and Linux operating systems.

UTC and Global Synchronisation

  |   By

A global economy has many benefits allowing trade and commerce to be conducted relatively pain free from the other sides of the planet. But conducting business with other countries can have its problems most notably time differences.

We are used to the fact that when we go to bed in Europe, those in Australasia are jest getting up and for many businesses, knowing the time in the country that you trade in is essential. However many global transactions are now conducted online and quite often completely automated.

For this reason computers need to know the exact time too, particularly if they are selling products and services that have a limited quantity and any miscalculation in the time can cause untold errors. For instance, if people across the globe wish to buy an airline ticket from an American broker then the computer needs to know who ordered the seat first otherwise there could be a risk of double-booking.

For this reason a global timescale has been developed allowing the whole world to synchronise to one timescale. This global timescale is commonly known as UTC (Coordinated Universal Time) and is based onthe old timescale GMT (Greenwich Meantime) although it accounts for the slowing of the Earth due to tidal and lunar forces.

UTC is kept accurate by atomic clocks that boast an accuracy of a second every 100 million years, however, atomic clocks are highly expensive to own, operate and run and are therefore impractical for a business that just wants to keep accurate UTC.

For this reason the dedicated NTP time server has been developed that can receive a transmitted time signal from an atomic clock and synchronise an entire computer network to it.

The NTP time server can receive a time signal directly from a physic laboratory using a long wave receiver or more conveniently using the GPS signals that are transmitted by satellites 30,000 km above the Earth.

By using a NTP time server a business network can be kept to within a few milliseconds of UTC (thousandth of seconds) ensuring that they can trade and do business with complete and accurate synchronisation.

Selecting a Time Source for a Network Time Server

  |   By

UTC – Coordinated Universal Time (from the French: Universel Temps Coordonné) is a global timescale based on Greenwich Meantime (GMT – from the Greenwich Meridian line where the sun is above at 12 noon). But accounts for the natural slowing of the Earth’s rotation. It is used globally in commerce, computer networks via a NTP server, air-traffic control and the World’s stock exchanges to name but a few of its applications.

UTC is really the only solution for time synchronisation needs. While it is just as possible to synchronise a computer network with an NTP server to a time other than UTC it is pointless. As UTC is utilised by computer networks all across the globe by using a UTC time source that means your network can synchronise with every other network in the world that is synchronised to UTC.

UTC is most commonly received from across the Internet, however, this can only be recommended for small network users where either accuracy or security is an issue. An Internet based UTC source is external to the firewall so will leave a potential hole for malicious users to exploit.

Two secure methods of receiving UTC are commonly available. These are either the GPS network (Global Positioning System) or specialist radio transmission broadcast on long wave from several of the world’s national physics laboratories. The two methods have both advantages and disadvantages which need to be ascertained before a method is selected.

A radio transmission such as the UK’s MSF, the German DCF-77 or the USA’s WWVB signal are vulnerable to local topography although many of these signals can be picked up indoors. Whilst not every country transmits a UTC radio signal around the neighbouring countries that do it is possible to still receive it.

GPS on the other hand is available literally anywhere on the globe. The signal comes directly from above and as long as the antenna has a good clear view of the sky it can be received anywhere. However, as the antenna has to be on a roof looking up this can have logistical problems (particularly for very tall buildings).

Specialist dedicated network time servers are available that can actually receive both methods of UTC but whether using GPS or a radio transmissions synchronisation of a network to within a few milliseconds is possible.