Express Computing - Fast And Reliable System Administration Tools Contacts Articles Support Purchase Download Products

Latest News

September 20, 2007

Express Timesync 3.7.1479
Clock synchronization accuracy has been improved. More info

May 31, 2007

Express Timesync 3.7.1478
Limit log file size feature has been added. More info

December 04, 2006

Express Timesync 3.6.1469
This version includes e-mail notifications support. More info



More news...


Recent Articles

Understanding time synchronization concepts
Learn why your system clock loses accuracy and how time synchronization helps to keep it accurate.
Read the article

The importance of time synchronization
This article describes why it is so important to keep the accurate time on a computer.
Read the article



More articles...



Home > Books and Articles > Time Synchronization Protocols

Time Synchronization Protocols

Time synchronization protocols define standards for the combination of the timing request and the time code. The protocol must be able to read a server clock, transmit the reading to one or more clients, and adjust each client clock as required.

The time synchronization protocol along with factors such as clock frequency drift, clock resolution, and network delay determines how closely the server clock and the client clock are synchronized.

Network Time Protocol (NTP)

NTP, specified in RFC 1305, is a protocol for synchronizing computer clocks across a network to standard time. The NTP client software runs continuously as a background task that periodically receives updates from one or more servers. The client software ignores responses from servers that appear to be sending the wrong time and averages the results from those that appear to be correct.

With the appropriate hardware, NTP is capable of achieving synchronization to within microseconds, depending on the synchronization source and the network paths.

NTP synchronization is part of a software package that includes a full suite of NTP options and algorithms, which are relatively complex, real-time applications. The sheer size and complexity of the NTP suite is not appropriate for many environments that do not have stringent accuracy requirements.

 To the top

Simple Network Time Protocol (SNTP)

SNTP is a basic version of NTP. It provides a simplified access strategy for servers and clients that do not require the degree of accuracy of the NTP protocol. SNTP is meant to operate in a dedicated server configuration, that is, one in which the server provides only one function. With careful design and control of the various latencies that are typical in such network design, it is possible to deliver time accurate to the order of milliseconds.

Because the network packet formats of both protocols are identical, the two are interoperable. The main difference between the two is that SNTP does not have the error management and complex filtering systems that NTP provides. The SNTP protocol allows room for error and might not be suitable for some corporations such as those in the financial industry that have very strict accuracy requirements.

 To the top

Time Protocol (TIME)

TIME protocol, specified in RFC868, provides a site-independent, machine readable date and time. The Time service sends back to the originating source the time in seconds since midnight on January first 1900.

Since the TIME protocol sends timestamps in seconds, it can provide only ±1 second accuracy and should be used only when it is impossible to use SNTP.

 To the top

Daytime Protocol (DAYTIME)

DAYTIME protocol is widely used by small computers running MS-DOS and similar operating systems. The server responds to requests in either tcp/ip or udp/ip formats. DAYTIME timestamps are sent using standard ASCII character strings.


 To the top



Express Computing - Fast And Reliable System Administration Tools

© Copyright 2003-2006 Express Computing. All rights reserved.
Privacy Policy | Terms of Use