Issue discovery device via MID server, can someone help for some tip or solution?

[May Seettoh]

172.x.x.x is not a reachable host (no response to target ports scanned by MID).

[May Seettoh]

Thank you 🙂 

[Rahul Priyadars]

Please close the thread if this helped you. 🙂

Regards

RP

[Harish Bainsla]

Here are steps you can take to troubleshoot the issue within the context of ServiceNow:

1. MID Server Status:

   • Check the status of the MID Server in ServiceNow. Ensure that the MID Server associated with the discovery is up and running.
   • Verify that the MID Server has the correct credentials and permissions to access and scan devices on the network.

2. Firewall and Network Configuration:

   • Ensure that there are no firewall issues preventing communication between the MID Server and the target host.
   • Verify that the network configuration allows traffic between the MID Server and the devices in the 172.x.x.x range.

3. Discovery Configuration:

   • Review the discovery configuration in ServiceNow. Confirm that the discovery job is set up correctly, and the target IP addresses and ports are specified accurately.

4. Device Accessibility:

   • Manually check the accessibility of the target host with the IP address 172.x.x.x. Ensure that the host is reachable from the MID Server.

5. Logs and Diagnostics:

   • Check the MID Server logs for any error messages or clues about the failure. Logs can provide valuable information about what went wrong during the discovery process.
6.