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

Troubleshooting steps

  1. Verify the current server IP address and basic reachability from the affected client.
  2. Confirm UDP port 123 is permitted between client and server. Ping alone does not verify NTP traffic.
  3. Confirm standard client mode. Some Masterclock devices do not support authentication or symmetric active modes; check the documentation for the model in use.
  4. Check Output Control and reference status. Confirm the device is configured to serve NTP and is not reporting an alarm state that causes the client to reject it.

Related articles

Time Dissemination During Reference Outages

Article ID: KB-NTP-001
KB Version: