Several thoughts: A standard ping uses as its source address the address of the exit interface. Extended ping can use the address of any interface on that router. Do a trace to see where it fails. Check the routing tables of the various routers. Somewhere a route is missing. For example - suppose routers A and F each have a LAN segment and a WAN interface. A standard ping from either would use its WAN interface address. Now on one end (say A)the LAN network isn't in the routing table. From A you can ping F (maybe both LAN and WAN); but F can only ping the WAN interface of A - not the LAN. Let us know your results.
> -----Original Message----- > From: Peter P [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 25, 2003 8:56 AM > To: [EMAIL PROTECTED] > Subject: ping things [7:66155] > > > I can ping from router A through various hops to router F. > Therefore the packet'knows' how to reach F - and also how to > find a path > back to A by reply. However from router F I cannot ping router A. > As the ping works in the first case - ie it knows the path > back from F to A > - how come it doesnt work in the 2nd ? The path is 'clean' ie > no firewalls, > access lists or any filtering. Puzzled. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=66168&t=66155 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
