1. Forum
  2. Usenet
  3. COMP.MISC

  • Pingable, But No Route To Host

    From Lawrence D'Oliveiro@21:1/5 to All on Mon Feb 24 07:53:39 2025
    Observed some interesting behaviour with a local online service: the
    domain name is pingable, but any attempt to actually connect returns “no route to host”.

    Looks like the ping service is being provided by a separate mechanism to
    the actual host itself. What kind of server infrastructure would tell
    porkies like that? No doubt this is characteristic of some well-known
    cloud service ...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Mon Feb 24 10:26:43 2025
    On 24.02.2025 07:53 Uhr Lawrence D'Oliveiro wrote:

    Observed some interesting behaviour with a local online service: the
    domain name is pingable, but any attempt to actually connect returns
    “no route to host”.

    Please use a sniffer like Wireshark and check which ICMP packet you
    receive. E.g. Telnet gives "No route to host" even when the ICMP Type 3
    Code 13 Communication Administratively Prohibited is being received.

    A rather confusing message.

    Looks like the ping service is being provided by a separate mechanism
    to the actual host itself. What kind of server infrastructure would
    tell porkies like that? No doubt this is characteristic of some
    well-known cloud service ...

    Some stupid default settings in firewalls return port unreachable
    instead of admin prohibited. This might be the case too, but check the
    packets first.

    --
    kind regards
    Marco

    Send spam to [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)