BUG: Adding device fails when device is not ping'able
When I attempt to add a device in OM8 and that device is not ping'able (but some TCP ports are open, e.g. 25, 80, etc) the add fails. This is a serious problem for us as we have hundreds of devices that are not pingable but do have open TCP ports that we need to monitor. I've seen this issue brought up before in the forum, and a "workaround" was promised for a future version of OM, but I do not see it in OM8. These devices are behind multiple firewalls in our facility, so simply enabling ping/ICMP temporarily is not feasible. Please advise as to how we can get this issue resolved.
New to ADSelfService Plus?