Hello,
From personal experience I would point the finger at access lists.
Take this scenario into account
Host A -> RouterA -> (wan) -> RouterB -> HostB
192.168.1.0 192.168.2.0 192.168.3.0
Ok, if you had an access list that say permitted traffic to exit on Router
A from Router B it would get to HostA, BUT that same access list would not
permit HostB on a different subnet to Talk to Host A. That would require
RouterA to know about Host B's subnet and allow routing from it. The same
holds true crossing the link in the opposite direction.
Brandon Ripper
CCNA
PS This would happen on the entire net because off same config problem
every place, or possibly lack of config.
At 11:03 AM 2/16/01 -0500, you wrote:
>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]
