Service Mapping : Error 118.xxx.xx.xxx is not a reachable host (no response to target ports scanned by MID).

geet · ‎04-16-2019

Hi All,

I created an entry point with an address:

https://abcd.com/xyz

When i clicked view map for the first time, discovery ran and gave below result:

118.xxx.xx.xxx is not a reachable host (no response to target ports scanned by MID).

Discovery Log

Host Discovery

2019-04-16 23:01:04: Discovery started

2019-04-16 23:01:04: 118.xxx.xx.xxx is not a reachable host (no response to target ports scanned by MID).

2019-04-16 23:01:04: Discovery completed



Can anyone please help me.

Regards,
Geet

tompowe · ‎04-18-2019

Couple of ideas:

1. Find out if there is a firewall between MID Server and target and if so, what ports are allowed.

2. Find the owner of the device and find out what type of device this is. If it's Windows, make sure port 135 is open on that box. If it's a Unix device, then you want port 22 open. If it's a network device, you need port 161 open.

- If it's a network device, it might have an ACL list which only allows certain servers to speak to it using SNMP. If it has one, your MID Server needs to be listed on it.

View solution in original post

Prapon P_ · ‎07-14-2020

Hello,

I've the same problem to discovery Linux server but I don't understand why credential testing has no problem.

tompowe · ‎07-15-2020

I assume you mean credential testing using the "Test credential" link on the Credential record?? If so, do you have MID Servers that are clustered? If so, then it's possible that some of those MID Servers can reach the target, while others in the cluster can't.

Yes, even though you tell "Test Credential" which MID to use, if your MID is part of a cluster, then Test Credential could use any of them. That's a "surprise" feature I learned. 🙂