Upcoming Events

Cloud Connect
Santa Clara
Feb 13-16, 2012

Cloud Connect brings together the entire cloud eco-system to better understand the transformation we're experiencing and promises to be the defining event of the cloud computing industry. Learn about the latest cloud technologies and platforms from thought leaders in Cloud Connect’s comprehensive conference.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up
Network + Systems Infrastructure
W O R K S H O P  
Keeping Time With Your Network

  July 10, 2003
  By Mike Fratto


>> continued from previous page

Step by Step

TOC Issue TOC
Printer Print full article
Printer Print this page
Printer Download as PDF
E-Mail E-Mail this URL
Discuss Discuss this article
flame author Flame the author
 
  In this article
arrow
Introduction
arrow
Setting Your NTP Time Model
arrow
Step by Step

1. Download the production Unix tarball and patches. Those are available from www.ntp.org/downloads.html.

2. Unzip and untar the archive. Follow the directions in the readme file to compile and install the programs.

3. Get a list of public time servers on the Internet (www.eecis.udel.edu/~mills/ntp/servers.html). Follow the access policies of the public servers located here.

4. Use traceroute (tracert on Windows) to locate time servers on the Internet that are close to your time servers. That will ensure the shortest round-trip time or fewest number of hops (usually the same thing).

5. Enter the time servers in /etc/ntp.conf. Use multiple servers for greater reliability. Use the "prefer" keyword to select a preferred time server.

6. Start the NTP daemon. To check if the daemon is running, use the ntpq utility and enter "pe." If NTP is working properly, you'll see output for your peers that looks like the graphic on the left.

The "reach" column should show 377 for reachable servers.

7. Wait for the NTP daemon to synchronize. If you're in a big hurry, fire up packet sniffing using tcpdump udp Port 123 and look for traffic to and from your NTP peers. If you don't see traffic to and from the NTP servers, there could be several reasons for the failure, such as no domain-name resolution or firewall problems.


start top   Setting Your NTP Time Model Step by Step

Research and Reports

Hypervisor Derby
August 2011

Network Computing: August 2011

TechWeb Careers