N-able N-central service Connectivity Status is not Normal

Last Modified

Thu May 25 18:33 GMT 2023

Description

  • N-able N-central Connectivity service is Failed or Stale

Environment

  • N-able N-central

Solution

  • The N-able N-central Connectivity service is an ICMP query from the monitoring appliance to the monitored network address.
  • If monitored by N-able N-central :
  1. Update the device network address if it is incorrect.
  2. Go to the device view for the problem device, then to Settings > Properties > Network Address:...
  3. Confirm that you get a reply when you ping the network address from the monitoring appliance.
  4. If the monitoring appliance is the N-able N-centralServer, you can run a ping by browsing to https://your-own-N-central-server-name/admin> Test Host Connectivity.
  5. If you do not get a reply when you ping the network address from the N-able N-centralServer, you can change the Monitoring Appliance to a probe.
  6. Go to Views > All Devices > Network Devices > Reset Filter > Device1 > Monitoring > Status > Connectivity > Service Details > Monitored By: ...
  • If monitored by a Probe:
  1. Refer to our troubleshooting article: Using PING to verify probe-monitored Connectivity
  • The connectivity service simply checks for availability from the scan source, so if the scan source (be it N-able N-central or the probe) cannot reach the device the service will fail.
  • If the monitoring device is having a problem this could create Stale services instead, generally due to the Windows Software Probe Service being in a stopped or otherwise non-functional state.
    • This can be validated from Administration > Probes