Maybe PC1 doesn't have a route back to R2, so the reply doesn't make it back.
As the other poster suggested, mabye R2 is using a source address in its ping that isn't in any of your static routes. Or maybe there's an access list that denies the ping or ping reply. The possibilities are endless. It's time to gather more data about what's really happening. Debug and protocol analyzer output might help. Also, study the router configs and "be the packet." ;-) Priscilla Paul wrote: > > Hi, > > R1 can ping/traceroute through R2 so on and so forth untill it > reaches its > destination at PC1. > The same ping/traceroute fails when executed from R2 !!!! > Why does this happen ??? > The ping result can be see below from R2. > > WHA4006-1#ping 10.9.9.3 > > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 10.9.9.3, timeout is 2 > seconds: > ..U.U > Success rate is 0 percent (0/5) > > We use static routes throughout ... > > Any thoughts or ideas ... > > Kind regards > > Paul ... > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=55745&t=55701 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
