I can ping it, so it's prolly not being picky as to who it answers icmp
requests from. Is the problem machine behind a firewall or other node
that can keep a spiteful eye towards unknown hosts? It's possible that
it may be blocking ther replies.
some alternatives...try using tracepath instead of traceroute....different
packet params. Also....try using nmap to ping it....you have much greater
control over what kinds of packets are used for the scan, and other nifty
features. If you do suspect it's a firewall problem, do your trace using
UDP over port 53. Most firewalls will let port 53/udp through because that's what
DNS uses (alternately, you can try to telnet to port 53 on that box). If
that doesn't work, use fragmented packets, some stateless firewalls can be
duped by those.
tack
On Fri, 29 Jun 2001, Erik Curiel wrote:
>
> Does anybody have any ideas on why I might be able to ping a certain host
> from one box but not from another? It's webnic.registrars.com. I can
> ping it from my box, but not from another one on another network. I can
> ping other things from that box, though, so it's not (just) a problem
> with that box's connection to the outside world. If webnic.registrars.com
> is up, then shouldn't basically *any* be able to find a route to it if one
> can? Traceroute just hangs from the one box as well after a certain
> point.
>
> Any suggestions would be greatly appreciated.
>
> Thanks!
>
> E
>
>
--
------------------------------------------
"Oh Dear, She's stuck in an infinite loop,
and he's an idiot!" --Prof Farnsworth
