Discovery: Windows proxy is unreachable and unable to be pinged/tested from the Discovery appliance UI. The proxy server IP can be pinged from the appliance CLI.

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BMC Discovery


    BMC Discovery 11.1


    BMC Discovery


    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
    28 ***
    29 ***
    30 ***

    -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 ( ) 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 ( ) at 2017-05-01 18:34 BST
    Nmap scan report for myTargetHost (xx.xx.xx.xx)
    Host is up.
    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:

    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles