Knowledge Base / Clients cannot sync to the NTP server

Clients cannot sync to the NTP server

When clients cannot sync to a Masterclock NTP server, common causes include routing/firewall issues, client mode mismatch, or server policy during reference loss.

Applies to: GMR, NTP100
Back to search
Symptoms
Causes
Suggested solutions or troubleshooting steps
  1. Confirm the server is reachable from the client.
  2. Verify the client is pointed at the correct server address.
  3. Check any dissemination or compatibility settings that could affect client acceptance.
Checks
  1. From the client, verify basic reachability (ping/routing) to the NTP server IP.
  2. Ensure UDP port 123 is permitted between the client and server.
  3. Ensure the client is configured for standard client mode. Some Masterclock devices do not support authentication or symmetric active modes.
  4. Verify the server is configured to serve NTP (Output Control) and is not in an alarm state that causes clients to reject it.
Related articles

Time Dissemination During Reference Outages

Article ID: KB-NTP-001
KB Version:

FOOTER | Colophon -->