Project

General

Profile

Bug #2208

Ping indicates host is live when it is not (Windows)

Added by Luke Murphey almost 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
Start date:
02/14/2018
Due date:
% Done:

100%


Description

Try pinging an unreachable host from the uptime monitoring dashboard and the ping dashboard. It acts like they are up.

The

Pinging att.com [144.160.36.42] with 32 bytes of data:
Reply from 144.160.36.42: Destination port unreachable.
Reply from 144.160.36.42: Destination port unreachable.
Reply from 144.160.36.42: Destination port unreachable.
Reply from 144.160.36.42: Destination port unreachable.

Ping statistics for 144.160.36.42:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),


Related issues

Related to Network Tools - Bug #1903: Ping on Wake-on-LAN page indicates host is live when it is not (Windows) Closed 06/29/2017
Related to Network Tools - Bug #1714: Traceroute doesn't work on Windows Closed 02/01/2017

Associated revisions

Revision 262 (diff)
Added by lukemurphey over 6 years ago

Added handling of output when Windows indicates no packet loss but no packets could be sent

Reference #2208

History

#1 Updated by Luke Murphey almost 7 years ago

  • Related to Bug #1903: Ping on Wake-on-LAN page indicates host is live when it is not (Windows) added

#2 Updated by Luke Murphey almost 7 years ago

  • Related to Bug #1714: Traceroute doesn't work on Windows added

#3 Updated by Luke Murphey over 6 years ago

See test_windows_parse_host_unreachable in unit.py. I already test for this.

#4 Updated by Luke Murphey over 6 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF