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

[geet]

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]

Geet,

That means the MID Server could not reach that IP Address.  There could be several reasons:

1.  That device is offline (maybe the configuration is pointing to something that is no longer around)

2.  Your MID Server cannot route to that IP Address.

3.  your MID Server is being blocked by a firewall.

[geet]

Hi Tompowe,

Thank you for the response !

I ran Quick Discovery on the IP and found response in Discover Log as follows:

There was no open port on this target, the target may be alive but not active.

So What should be my next step to resolve this?

Regards,

Geet

[tompowe · Accepted solution]

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.

[robertgeen]

Based on your IP I would say you are trying to access a public IP which won't have the appropriate ports open. See if there is an internal IP you can hit instead.