@Ai Yamano1 ,
It looks like the error <IP> is not a reachable host (no response to target ports scanned by MID) in your ServiceNow Discovery/ServiceNow Service Mapping setup is telling you that even though your MID Server is up and credentials are validated, the MID Server either doesn’t have network-level reachability to the target host (for example due to routing, subnet scope or firewall issues) or the standard ports the MID Server tries to scan (such as RPC/WMI on Windows or SSH on Linux) are blocked or not responded to. This typically happens if the MID Server’s IP range configuration doesn’t include the target host, or if the target machine’s firewall is preventing connections from the MID Server, or the host simply isn’t active at the time of the scan........ For example, a common resolution flagged by users is: Your MID Server doesn’t have the necessary network access to the target, or a firewall is preventing its scanning.....
In this kind of lab scenario you should verify from the MID Server machine that you can ping (or connect via telnet/SSH/WMI) the target IP and port, confirm that the target is powered on and reachable, confirm the firewall allows the MID Server’s IP, and ensure the IP address range in the Discovery/MID Server config includes that host..........Once network reachability is confirmed, the error should resolve and the scan will progress past the not reachable host stage.........
If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.
Thanks and Regards,
Kaushal Kumar Jha - ServiceNow Consultant - Lets connect on Linkedin: https://www.linkedin.com/in/kaushalkrjha/
