Quote:
|
Originally Posted by mr-b
It's not so much that, it's that recent virus outbreaks e.g. the W32.Welchia.Worm, have used ICMP to check for potential hosts to infect, and because of the increased traffic many web hosters and service providers have either turned off ICMP or else drop the packets at any hint of any Denial of Service attacks.
Therefore traceroute and ping are just not reliable indicators of network connectivity.
So there's no substitute for looking at network traces to see exactly what's going on.
Some free tools are www.ethereal.com or its relation http://www.networkchemistry.com/products/packetyzer/ |
All my servers block ICMP unless it comes from specific IP's (which obviously belong to support staff). So we can ping them and trace to them, but joe public cannot. This is not uncommon these days.
Most people tend to confuse pings and tracerts with web traffic (and tcp/udp traffic in general) - I would love a pound for everyone who posts a tracert when they are having http/https problems. It is an easy mistake to make (the same problem happens with gamers, who post ICMP pings when their games use UDP or TCP).
