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.
Discover the benefits of scalable backbone and network services for application and cloud providers.
Network automation is gaining momentum. Here's how you can drive this powerful technology to its full potential.
Subsea cable alternatives can provide a level of comfort for those concerned about disruptions. Realistically, they will continue to play a small, but critical role in the short term.
