From: W Walla (wallafly@hotmail.com)
Date: Thu Jul 22 2004 - 14:40:31 GMT-3
Hello!
Yes it started working. I repled to Dan, and thought it was a reply to all.
BUT, the plot thickens. When I added the route that fixed my issue it broke
something that had been working. There is a firewall and a vpn at that B
site. I did not have that on my config and my Diagram. (Thought that it
was a DF route just for internet... I am sure that it is screwing up the
routing. But still, it knows how to route well enough to ping a certain
device, but not well enough to telnet to it. But now I can telnet through
it (not ping though) so it is not an MTU problem.
I am going to make some ospf network additions, and remove the references to
the vpn, and then start stripping away the dfault routes..testing each along
the way.
Thanks Dan and everybody!
>From: "Daniel Sheedy" <dansheedy@gmx.net>
>Reply-To: "Daniel Sheedy" <dansheedy@gmx.net>
>To: "Tim Fletcher" <groupstudy@fletchmail.net>
>CC: <ccielab@groupstudy.com>
>Subject: Re: CAn Ping but not telnet /
>Date: Thu, 22 Jul 2004 15:56:22 +0200
>
>Hi Guys,
>
>Seems Wally didnt reply to the group when he got it working.
>
>He added a static route on the Router B and C, and suddenly the packets
>could find their way back!
>Magic at its best! :)
>It was a case of too broad default routes.
>
>Dan Sheedy
>
>----- Original Message -----
>From: "Tim Fletcher" <groupstudy@fletchmail.net>
>To: "MADMAN" <dmadlan@qwest.com>; "W Walla" <wallafly@hotmail.com>
>Cc: <dansheedy@gmx.net>; <ccielab@groupstudy.com>
>Sent: Thursday, July 22, 2004 3:53 PM
>Subject: Re: CAn Ping but not telnet /
>
>
> > Exactly what I was thinking. If you turn on debug ip icmp on the far
> > router, then ping it, you should see the responses. If not, you may not
>be
> > pinging what you think you're pinging.
> >
> > Also I don't think it's an MTU issue. That would only come into play if
>the
> > packets were big enough to hit the MTU. Setting up a telnet connection
>is
> > only going to use small packets. You would however have problems if for
> > example you did a sh run, which would send lots of data in large
>packets.
> >
> > -Tim Fletcher
> >
> > At 10:19 AM 7/21/2004, MADMAN wrote:
> > > I haven't read all the posts so sorry if I'm rehashing. I have seen
> > > this before and the issue was the device you were pinging was not what
> > > you thought it was. Try changing the IP addresses of the problem
>devices
> > > if this is possible and a traceroute may help to confirm your actually
> > > taking the path you would expect.
> > >
> > > Dave
> > >
> > >W Walla wrote:
> > >
> > >>Okay, well I learned from your replies, so thank you.
> > >>But, as far as routing, I CAN ping from A Lan to C Lan right though
>the
>B
> > >>router... Just not telnet.
> > >>I feel like it is an ACL or Firewall somewhere but there are not any
>that
> > >>I can see or have been told about. Also, None of the routers have
>ACL's
> > >>applied. Is it possible that they have some legacy ACL floating
>around
> > >>in their configs that is not showing up on the saved and running
>configs?
> > >>How would I clear that sort of possiblity short of rebooting all of
>them?
> > >>Thanks.
>
>_______________________________________________________________________
>Please help support GroupStudy by purchasing your study materials from:
>http://shop.groupstudy.com
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:12:00 GMT-3