ntp_response Error: unable to contact host
search cancel

ntp_response Error: unable to contact host


Article ID: 4163


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)


NTP_Response Error: unable to contact host, You might want to try with type = SNTP.





UIM: 8.3, 8.4, 8.51 or later
NTP_Response: 1.40, 1.41


This can happen if the local host or remote NTP server ip address is not being updated in the /etc/ntp.conf file.


Type SNTP: Configured probe on client and you can only monitor “Response time exceeds” and “No contact with server” for this. 

Type NTP: Configured probe on server and you can enable monitoring for below monitors.

  • Response time exceeds
  • Offset exceeds
  • Jitter exceeds
  • No contact with server
  • Server is not updated from any peer
  • Server is not fully initialized 

1) If the machine where ntp_response probe is deployed is an NTP client (NTP service running on server) and synchronizing with NTP server, "SNTP type" would work. 

2) If the machine where ntp_response probe is deployed is an NTP server, then NTP type will work.

Once the probe is deployed and adding the required host profile for ntp_response, please follow the below mentioned steps.

  1. Login to NTP Server with root user (Eighter it could be local host or remote host)
  2. Open /etc/ntp.conf file and add the below lines and save it.
    • restrict
    • restrict -6 ::1
    • restrict <IP Address of Probe Machine>
    • restrict <IP Address of Local Machine>
    • Note: The -6 option is required before an IPv6address. So only third line will be enough in case NTP server and client (probe machine) are different.
  3. Restart the NTP service by running the command. "service ntpd restart"
  4. Confirm the service is running using command "ps -eaf | grep -i ntp.
  5. "Test the connectivity on ntp_response probe and confirm whether it works or not.

Additional Information

ntp_response probe documentation:

Reference Documents from Redhat:




The ntp_response probe does not currently support chrony ( If the device is a NTP v4 - RFC5905)

Check if the server is running the chrony daemon rather than the ntp daemon.