This sounds like an access list problem somewhere. It could be on
Router9, or it could be on the other routers. Outgoing access lists do
not filter packets originated from the routers themselves. So, you
could have an access list blocking outgoing ICMP that would still allow
the router itself to originate a trace but would block any other hosts
from doing the same thing.
Or, perhaps you have an access list on Router9 that is blocking ICMP
from other networks, but not directly attached networks/routers.
I would initially take the following steps: Telnet to router9, turn
off logging to the console and turn on icmp debugging. Try a trace from
Router1 and then one from HostA. Turn off debugging and examine the
logs. (assuming that you were logging in the first place.) Then go to
Router1 and repeat the process. That might help pinpoint where the
problem actually lies.
HTH,
John
>>> "Deloso, Elmer G (WPNSTA Yorktown)" <[EMAIL PROTECTED]>
2/16/01 9:03:32 AM >>>
Hi, all.
I might have posted something similar to this not too long ago but I
might
not have beed specific enough. Here's the story:
HostA ---Router1---........................Router9----HostB
If i traceroute from within Router1 to HostB, it goes through.
But if i do the same from HostA, it stops at Router9.
The same thing happens when tracerouting from HostB's end, it stops
at Router1.
So i checked with another network that also has a route to Router9,
ans the same story happens. From the Router-Y the trace gets to
HostB. But from Host-Y it stops at Router9.
Has anyone else seen this and figured out the cause?
Thanks.
Elmer Deloso
_________________________________
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
