NTP.org – The home for the NTP Project who provides support and additional development resources for the Official Reference Implementation of NTP.

NTP Project support pages

THE NTP pool – list of public servers

NPL – The National Physical Laboratory in the UK who control the MSF radio signal.

The University of Delaware and David Mills’ information page, Professor Mills is the original inventor and developer of NTP

David Mills’ list of Public NTP Time Servers a list of public NTP servers

National Institute of Standards and Technology (NIST) who operate the USA’s WWVB radio signal

Europe’s largest supplier of NTP server related products.

Galleon UK – NTP server products for the UK

ntp-time-server.com – one of the largest time and frequency suppliers in the United States

NTP – Wikipedia article on NTP

NTP server checker – free tool to ensure time server accuracy

Galleon’s free NTP Server Checker allows you to check the following items
* IP address – the time server you are checking.
* NTP Version
* Reference timestamp (the prime epoch ) used by NTP to work out the time from this set point
* Round trip delay (the time it takes request to arrive and come back in milliseconds)
* Local clock offset – time difference between host and client
* Leap indicator (if there is to be a leap second that day – normally only on 31 December)
* Mode 3 – indicates a client request
* Stratum level – which stratum level the NTP server is (a stratum 1 server receives the time from an atomic clock source a stratum 2 server receives the time from a stratum 1 server)
* Poll Interval (Will be 1 as only 1 requests is made by the SNTP client)
* Precision – how accurate in milliseconds
* Root Delay – This is a signed fixed-point number indicating the total roundtrip delay to the primary reference source at the root
* Root dispersion (in milliseconds)- The root dispersion is the maximum (worst case) difference between the local system clock and the root of the NTP tree (stratum 1 clock)
* Ref ID – the host name
* Originate time stamp (time before synchronisation request)
* Receive timestamp – the time the host got request
* Transmit timestamp – the time the host sends back to us
* Is response valid – synchronised or not

Please download from Galleon Systems

NTP - Network Time Protocol

SNTP – Simple Network Time Protocol

GPS – Global Positioning System

UTC – Coordinated Universal Time

MSF – Radio Time Signal for United Kingdom

WWVB – Radio Time Signal for American

DCF – Radio Time Signal for Germany

LAN – Local Area Network

UDP – User Datagram Protocol

TCP – Transmission Control Protocol

IP – Internet Protocol

TDF – Radio Time Signal for France

CHU – Radio Time Signal for Canada

JJY – Radio Time Signal for Japan

HBG – Radio Time Signal for Switzerland

USB – Universal Serial Bus

RTC – Real Time Clock

AM – Amplitude Modulation

APM – Automatic Power Management

DES – Data Encryption Standard

ESD – Electrostatic Discharge

FM – Frequency Modulation

IETF – Internet Engineering Task Force

IRIG – Inter-Range Instrumentation Group

MD5 – Message Digest

PPM – Part Per Million

PPS – Pulse Per Second

RFC – Request For Comments

SA – Selective Availability

TAI – International Atomic Time

SI – International System of Units

A public NTP Server is a time server on the Internet that, as the name suggests, members of the public can use as a timing source. The best location on the Internet to find a list of public NTP servers is the home of NTP – www.ntp.org

There are two lists of public NTP servers on ntp.org, one for primary servers and one for secondary servers. Primary servers have up to several hundred clients each. However, many primary servers are ‘closed access’ meaning that only agreed clients can access them. This is because if there is too much traffic attempting to receive a timing source from a primary source then it will clog the network making the server useless.

Primary servers are known as a stratum 1 server in that they get their timing source direct from an atomic clock often using the GPS or national time and frequency transmissions. Secondary NTP servers tend to be stratum 2 time servers, that is a time server that receives its timing source from a stratum 1 server.

Most users that require a public NTP server will find that most primary servers are closed access and that they will have to use a secondary NTP server. When using a public NTP server it is important that access policies are adhered to as many institutions require on these servers for timing information.

Network Time Protocol (NTP) is an Internet based protocol designed to distribute and synchronise time across a network.

NTP is in fact one of the oldest Internet protocols having been developed in the late 1980’s at Delaware University when the Internet was still in its infancy. It was devised by Professor David Mills and his team when they realised the need for accurate time synchronisation if computers were needed to communicate with each other.

A NTP server is a dedicated device that receives a single timing source and then distributes it amongst all network devices. A NTP server will receive the timing information through a number of ways but normally it is a UTC source (coordinated universal time) a global timescale based on the time as told by atomic clocks.

NTP handles the time in a different way to how humans perceive and deal with it. While we may split a time into seconds, minutes, hours, days, months and years; NTP regards time  as a single number which is the number of seconds since the ‘prime epoch’.

The prime epoch is a date set for when NTP began counting seconds. For NTP the prime Epoch is 00.01 on 1 January 1900 so that means on 1 January 2008 the time according to NTP will be 3405888000, which is the number of seconds since 1900.

The NTP server is now an essential part of the modern computer network. Without a dedicated NTP server administrators are forced to rely on unsecure and inaccurate Internet sources to synchronise their network clocks too.

The potential risks involved in this, namely leaving a hole open in the network firewall and the lack of the NTP security measure: authentication, means that networks that use an Internet based timing source are risking their system to attacks from malicious user and hackers.

It should also be noted that a survey of Internet based timing sources found less than a third were accurate to UTC time and those that were could still be too far away from client to make any useful synchronisation.

There are two types of dedicated NTP server, the GPS NTP server and the radio referenced NTP server. The difference between the two is based solely on the method they receive their UTC time source from. A GPS NTP server will use the signals broadcast from the GPS satellites above the Earth’s atmosphere. These signals are very reliable and can be picked up anywhere in the Worlds as long as the GPS antenna has a clear view of the sky.

The alternative is to use a dedicated NTP server that can receive a signal from the national time and frequency transmissions broadcast by several national physics laboratories. While not available in every country and quite vulnerable to interference these long-wave time signals are still an accurate and secure method of receiving UTC time. They are also ideally suited for network administrators who, for reasons of logistics can’t place a GPS antenna on the roof.

Network Time Protocol (NTP) is one of the Internet’s oldest protocols still in use. Developed by Dr David Mills from the University of Delaware, it has been in constant use and continually updated since 1985. NTP is a protocol designed to synchronize the clocks on computers and networks across the Internet or Local or Wider Area Networks (LANs/WANS).

In a modern global economy time synchronisation is essential for carrying out time sensitive transactions such as booking an airline ticket to bidding on an Internet auction site. If clocks were not synchronised to the same time you may find your airline seat sold after you had bought it and Ebay’s administrators would not be able to discover whose bid was the latest.

NTP is a multi-tiered system, each tier being called a stratum. Servers at each tier communicate with each other (peer) and provide time to lower strata. Servers at the top stratum, stratum 1 connect to an atomic clock either over the Internet or by a radio or GPS receiver while a stratum 2 server will connect to a stratum 1.

NTP uses an algorithm (Marzullo’s algorithm) to synchronise time on a network using time scales like UTC (Coordinated Universal Time or Temps Universel Coordonné) and can support such features as leap seconds – added to compensate for the slowing of the Earth’s rotation.

NTP (version 4 being the latest) can maintain time over the public Internet to within 10 milliseconds (1/100th of a second) and can perform even better over LANs with accuracies of 200 microseconds (1/5000th of a second) under ideal conditions.

NTP time servers work within the TCP/IP suite and rely on UDP (User Datagram Protocol). A less complex form of NTP called Simple Network Time Protocol (SNTP) that does not require the storing of information about previous communications, needed by NTP, is used in some devices and applications where high accuracy timing is not as important and is also included as standard in Windows software (although more recent versions of Microsoft Windows have the full NTP installed and the source code is free and readily available on the Internet).

The NTP program (known as a daemon on UNIX and a service on Windows) runs in the background and refuses to believe the time it is told until several exchanges have taken place, each passing a set of tests. If the replies from a server satisfy these ‘protocol specifications’, the server is accepted. It usually takes about five good samples (five minutes) until a NTP server is accepted as a source for synchronisation.

Synchronisation with NTP is relatively simple, it synchronises time with reference to a reliable clock source such as an atomic clock, although these are extremely expensive and are generally only to be found in large-scale physics laboratories, however NTP can use either the Global Positioning system (GPS) network or specialist radio transmission to receive UTC time from these clocks.

A simplified version of NTP called Simple Network Time Protocol (SNTP) exists that does not require the storing of information about previous communications as required by NTP. It is used in some devices and applications where high accuracy timing is not as important and is installed on older versions of Microsoft Windows. Windows since 2000 has included the Windows Time Service (w32time.exe) which uses SNTP to synchronise the computer clock. NTP is also available on UNIX and LINUX (download via NTP.org).

Computer networking is one of the most difficult aspects of information and communications technology (ICT). The logistics of connecting terminals, routers, printers and all the other devices can leave many administrators with a constant headache.
One of the most important aspects that often gets overlooked and can have disastrous consequences is that of time synchronization.

It is imperative that all devices on a network are telling the same time as timestamps, the format a computer relays time to each other, are the only form of reference a computer can use to establish a sequence of events. If different machines on a network are telling different times then unforeseen consequences such as emails arriving before they have technically been sent and other anomalies will make the administrator’s headache even worse.

What’s more a computer network that is not synchronized is open to security threats and even fraud. Fortunately the NTP time server has been around for many years and can ease the headache of time synchronization .

NTP (Network Time Protocol) is one of the oldest protocols used by computer networks. Developed nearly three decades ago NTP is a protocol that checks the time on all devices on network and adds or subtracts enough time to ensure they are all synchronized.

NTP requires a time reference to synchronise the network’s clocks to. Whilst NTP can synchronize a network to any time an authoritative time source is obviously the best solution. UTC (Coordinated Universal Time) is a globally used timescale based on the time told by atomic clocks. As atomic clocks lose less than a second of time in over a thousand years, UTC is by far the best timing source to synchronize a network to. Not only will your network be perfectly synchronized together but also your network will be synchronized to the same time as millions of computer networks all from around the world.

A NTP server can receive a UTC time reference from several sources. The Internet is the most obvious source, however Internet timing sources are notoriously inaccurate and those that are not can be relatively useless if the distance is too far away. Also having placed your NTP server securely behind your firewall it does seem pointless to have to keep a hole open in it to allow the NTP server to poll the timing reference from across the web and leave the entire network vulnerable, particularly as NTP authentication (NTP’s own security measure) is not possible over the Internet.

There are two far more secure and accurate methods of receiving a UTC timing reference. The first is to utilise the national time and frequency transmissions that several countries broadcast from their national physics laboratories. These are usually broadcast via long wave which has an advantage of being able to be picked up inside a server room although many countries do not have such a signal.

However, many NTP servers can utilize the timing signal broadcast by the onboard atomic clocks of the GPS (Global Positioning System) satellites.  This signal is available everywhere but a GPS antenna is required that can get a clear view of the sky.

By utilizing a UTC timing source either through the GPS network of radio transmission a computer network can be synchronized to within a few milliseconds of UTC time.

Many network administrators boast that there networks are perfectly synchronised because they have an atomic clock as an NTP server. In actual fact as atomic clocks cost several millions of pounds and are quite vast in size it is doubtful the average server room contains such a timepiece.

What in fact they are referring to is that they have an NTP server that receives a timing source from an atomic clock. However, just because atomic clocks are the most accurate chronometers in the world, accurate to a few nanoseconds (billionth of a second) it doesn’t necessarily mean that a network using one as a timing source is receiving the same sort of accuracy

Atomic clocks work on the principle that certain atoms (in most atomic clocks the caesium -133 atom) oscillates at an exact frequency at certain energy levels. In the case of the caesium atom it resonates at exactly 9,192,631,770 every second.  Because of this exact resonance, atomic clocks lose less than a second in millions of years. In fact, the resonance of the caesium atom is so precise that the International System of Units has defined the second as exactly that number of oscillations of the caesium atom.

NTP servers can receive the time from an atomic clock through several sources. Obviously the Internet contains thousands of timing servers, some of which are hooked up to an atomic clock, others however, can be over ten seconds out of sync.

Furthermore, using an Internet timing source can leave a system open to abuse as the timing references cannot be authenticated. Also, the distance from a host, client and server can make dramatic differences in the accuracy.

The most accurate and effective way of receiving a timing source from an atomic clock is to use the national time and frequency broadcast that several country’s national physics laboratories transmit. Alternatively the American GPS (Global Positioning System) transmits the time from its own satellite’s atomic clocks. both methods can provide perfect synchronisation and accuracy to within a few milliseconds.

All computers are prone to drift and as accurate timing is essential for many time critical applications, Network Time Protocol has been developed to keep computers synchronized

NTP is installed on most versions of Windows (although a stripped down version called SNTP is in older versions) and Linux but regardless is open source an free to download from ntp.org.

To synchronise a network it is preferable to use a dedicated NTP server that receives a timing source from an atomic clock either from specialist national radio transmissions or the US GPS system, although Internet time references are available but some are more reliable than others (and none can be authenticated leaving a system open to attack).

NTP is hierarchical, it is arranged into stratum. Stratum 0 is a timing source (such as an atomic clock) while stratum 1 is a server connected to a stratum 0 server and a stratum 2 is a computer (or device) attached to a stratum 1 server.

There is an understanding that if using a public Internet based time server, stratum 0 servers are not used by most applications as too many requests would disable them. Instead NTP should be configured to receive a timing reference from several stratum 1 and stratum 2 servers (it is good housekeeping to use more than one as it is possible one server could go down).

The most accurate and secure way of synchronising a network is to use a dedicated NTP server. These can receive a timing reference from either the GPS network (as each GPS satellite contains an atomic clock and broadcasts the signal) or a specialist national radio transmission. Both of these signals come from a stratum 0 source and both provide accuracy to within a few milliseconds.

Network Time Protocol (NTP) has been around for nearly 25 years. It is one of the Internet’s oldest protocols and is still widely used and under constant development.

NTP was developed and designed in 1985 by Professor David Mills from the University of Delaware in the United States. Its success owes much to the fact that it was one of the first ever protocols on the Internet and was first used when the World Wide Web was in its infancy.

The importance of NTP on modern computer networks cannot be stressed highly enough, without NTP and NTP servers many of the applications and processes that we conduct over the Internet and now take for granted

Internet auction sites, email and global trading all require accurate time synchronisation. Just imagine booking an airline ticket only to discover your seat was resold after you had purchased it because the buyer had a slower clock on their computer?

Confusion and problems such as these would be commonplace without NTP and NTP servers, just think of the hysteria around the millennium bug!

NTP servers allow not only computers on a particular network to be perfectly synchronised but as most NTP servers are set to receive time from a UTC time source, computers around the entire globe can be synchronised together. UTC or Coordinated Universal Time is a global time scale based on the time told by atomic clocks.

NTP servers can receive a timing reference from the Internet, although this is fairly inaccurate, or from dedicated time and frequency radio signals or the GPS network.

Currently an NTP server receiving an authoritative timing source can provide accuracy over the Internet to within a few hundred nanoseconds (a nanosecond is 1 second every billion years.)

An NTP server (network time protocol) is a device to ensure all machines on a computer network are running the exact same time. Without an NTP server time would be inconsistent between devices which could problems for the network, seconds could be lost here or gained there which could cause major confusion as well as leaving your network vulnerable.

Time, in the form of timestamps, provides the only frame of reference between all devices on a network and the way an NTP server works is pretty straightforward. The timestamp relayed to the server is in the form of an ever increasing number that started from a set point in time, this is known as the prime epoch and for most systems this started on 1 January, 1900.

The NTP server checks the time stamp from an authoritative source, normally a UTC source (Coordinated Universal Time, a global timescale based on the time told by atomic clocks), from either the Internet, a radio transmission or via the GPS network.

The NTP server uses the timestamp to calculate if the network clocks are drifting and adds or subtracts a second to match the reference clock. The NTP server will do this at set intervals, normally every fifteen minutes to ensure perfect accuracy.

NTP is accurate to within 1/100th of a second (10 milliseconds) over the public Internet and can perform even better over LANs and WANS with accuracies of 1/5000th of a second (200 microseconds) not unheard of.

To ensure further accuracy the NTP service (or daemon on Linux) which runs in the background and does not believe the time it is told until after several exchanges and each one has passed a protocol specification (a test), the server is then considered. It usually takes about five good samples) until a NTP server is accepted as a timing source.

Time is essential for modern computer networks, as the majority of applications and processes conducted by a PC are  reliant on a timestamp, from sending an email, debugging a server to preventing fraud, therefore, accurate time and synchronisation is vital.

NTP (Network Time Protocol) is an Internet protocol designed for the synchronisation of computer networks. NTP servers are used by millions of system administrators to ensure their networks are keeping accurate time.

However, just as a computer is only as a good as the software it is running, a NTP server is only as good as the timing source it receives.

Despite the hundreds and probably thousands of possible timing references on the Internet, administrators should be aware of some of the possible pitfalls in selecting a timing reference.

A survey conducted by the Massachusetts Institute of Technology (MIT) discovered that not only were half of Internet timing sources inaccurate by over a ten seconds (a lifetime if we are attempting millisecond accuracy) but many were too far away to be provide any useful accuracy.

If an Internet timing source is to be used then not only should the accuracy of the server be checked but also the closest host should be selected to ensure the best accuracy.

Another consideration in using an Internet timing source is to be aware that they cannot be authenticated which means that your system could be vulnerable to malicious attacks and it is recommended by Microsoft and Novell that an external hardware source should be used.

The most secure and accurate method of receiving a timing source is to use a dedicated NTP server that can receive either a national time and frequency transmission (such as WWVB in the US or MSF in the UK). Alternatively a timing source can be received from the GPS network (Global Positioning System), both methods are authenticated and can provide millisecond accuracy.