PING -R

[Ondrej Sevecek]

Hello,
I have traced some ip routes with use of PING -R command to let record the
way of packet. This works fine for some paths, but it fails (with "Request
timed-out") for some others. It is not dependent on the number of routers in
the way (even when there are more than 9 routers, it might work fine).
What determines and prevents the answer comming home from some routers?
The pure PING without -R parameter succeeds, but only addition of -R
parameter results in "request timed-out". It seems like some router prevents
the record-route option. I can even determine the router's IP when pinging
everything behind him results in "request timed-out".

Nice day Ondra.

 

[Roland Hall]

If the router is rejecting ICMP requests, ping and tracert will fail since
they are ICMP messages.

Hello,
I have traced some ip routes with use of PING -R command to let record the
way of packet. This works fine for some paths, but it fails (with "Request
timed-out") for some others. It is not dependent on the number of routers in
the way (even when there are more than 9 routers, it might work fine).
What determines and prevents the answer comming home from some routers?
The pure PING without -R parameter succeeds, but only addition of -R
parameter results in "request timed-out". It seems like some router prevents
the record-route option. I can even determine the router's IP when pinging
everything behind him results in "request timed-out".

Nice day Ondra.

 

[Curtis Reynolds]

This is a common configuration for routers today with all the virus' that
run around using ICMP to find responding machines.

CR

 

[Chuck]

Hello,
I have traced some ip routes with use of PING -R command to let record the
way of packet. This works fine for some paths, but it fails (with "Request
timed-out") for some others. It is not dependent on the number of routers in
the way (even when there are more than 9 routers, it might work fine).
What determines and prevents the answer comming home from some routers?
The pure PING without -R parameter succeeds, but only addition of -R
parameter results in "request timed-out". It seems like some router prevents
the record-route option. I can even determine the router's IP when pinging
everything behind him results in "request timed-out".

Nice day Ondra.

Ping -r is ok occasionally, tracert is better. If you have ability to
install on the computer you're using, I much prefer PingPlotter from
http://www.pingplotter.com - the free version of that will do a
combination of ping -r and traceroute that I think you will like.


Chuck
I hate spam - PLEASE get rid of the spam before emailing me!
Paranoia comes from experience - and is not necessarily a bad thing.