1 Reply Latest reply on Sep 16, 2020 12:02 PM by Andrew Waters

    Endpoint dropped although ping is fine

    Danny Fleer
      Share This:

      I've noticed some endpoints where scanning fails when ping is used to check the availability. In this case the result of the scan is "No response". To scan the endpoints we use a BMC Discovery Outpost.

       

       

      The strange thing here is that a ping from the commandline of the outpost server shows that the endpoint is available:

       

      C:\>ping  10.241.167.23

       

      Pinging 10.241.167.23 with 32 bytes of data:

      Reply from 10.241.167.23: bytes=32 time=1ms TTL=122

      Reply from 10.241.167.23: bytes=32 time=1ms TTL=122

      Reply from 10.241.167.23: bytes=32 time=1ms TTL=122

      Reply from 10.241.167.23: bytes=32 time=1ms TTL=122

       

      Ping statistics for 10.241.167.23:

          Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

      Approximate round trip times in milli-seconds:

          Minimum = 1ms, Maximum = 1ms, Average = 1ms

       

      The only way to scan the endpoint successfuly is dusing the "Do not use ping before scanning" option.

       

       

      Question: Which command is used to ping the endpoint to check it's availability?