This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BMC Discovery 11.1
After adding a new Windows proxy (from the Proxy Manager UI), the appliance is unable to communicate, ping or perform tests to the proxy from the Discovery UI. Troubleshooting showed:
-From the appliance CLI, traceroute fails after 30 hops with
-From the appliance CLI, using nmap to check the status of the proxy communication port shows:
$ /usr/bin/nmap -p T:4321,4323 xx.xx.xx.xx
Starting Nmap 7.01 ( https://nmap.org ) at 2017-05-01 18:03 BST
Read from /usr/bin/../share/nmap: nmap-payloads.
Read from /usr/tideway/etc: nmap-services.
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.01 seconds
-Changing nmap to not ping produces the following output:
/usr/bin/nmap -Pn -p T:4321,4323 xx.xx.xx.xx
Starting Nmap 7.01 ( https://nmap.org ) at 2017-05-01 18:34 BST
Nmap scan report for myTargetHost (xx.xx.xx.xx)
Host is up.
PORT STATE SERVICE
4321/tcp filtered unknown
4323/tcp filtered unknown
However, from the appliance command line, it is possible to ping the IP of the proxy server successfully.
A Windows host-based firewall is enabled on the proxy server
Either disable the Windows firewall on the proxy server, or create a rule to allow communications on the ports detailed in the documentation here: