Sujet : Re: Pingable, But No Route To Host
De : mm+usenet-es (at) *nospam* dorfdsl.de (Marco Moock)
Groupes : comp.miscDate : 24. Feb 2025, 10:26:43
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <20250224102643.6649b69e@ryz.dorfdsl.de>
References : 1
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 regardsMarcoSend spam to 1740380019muell@stinkedores.dorfdsl.de
Pingable, But No Route To Host
Re: Pingable, But No Route To Host