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

May Seettoh
Tera Contributor

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

7 REPLIES 7

doug_schulze
ServiceNow Employee
ServiceNow Employee

Your mid doesn't have the necessary network access to the target, or a firewall is preventing its scanning.

Thank you 🙂

Hi Doug,

 

Where you able to fix your  the error you were getting from Discovery such as - x.x.x is not a reachable host (no response to target ports scanned by MID).

Rahul Priyadars
Giga Sage
Giga Sage

Just to add what Doug Said. Refer Below KB for Ports and Credential related TroubleShooting.

 

Credentials/Permissions troubleshooting on Discovery, Service Mapping, Orchestration. - Support and ...

 

Regards

RP