[nsp] RE: OK I'm Stumped!!!!

[Melvin C. Etheridge]

Let me add that this is only affecting about a couple dozen customers.

If they bring their system in to our office we can dial up and surf fine.

If we go out to the customers premises with our laptop sometimes it works
and sometimes we get the same error.

Customers can surf for about 10-15 minutes.  Then "page cannot be found".
Also I can have customer ping a IP and get all replies back...I can have
them ping www.yahoo.com and get all replies back.....but the cannot browse
check or send email or use AOL IM or MSN IM.

Also,  Everything seemed to be fine earlier this evening and now has stated
going down hill over the last hour or so....

Like I said....

THIS IS DRIVING ME CRAZY!!!!!!

Mel

----- Original Message ----- 
From: "Stephen J. Wilcox" <steve at telecomplete.co.uk>
To: "Melvin C. Etheridge" <mele at enia.net>
Cc: <cisco-nsp at puck.nether.net>
Sent: Monday, June 07, 2004 5:47 PM
Subject: Re: [nsp] RE: OK I'm Stumped!!!!


> Not if you can ping
>
> What I'd do next.. find a nearby server you control that they can ping but
cant
> browse a web page on.. run tcpdump or equiv on that box
>
> Now try ping using increasing packet sizes, see what size they stop
working at
> (if they stop working).
>
> Try opening a webpage on the server and record the tcp connection
>
> For ping, tcpdump should help you work out in which direction the problem
lies
> (ie you receive the icmp echo but the dialup doesnt report the echo
reply).
>
> For the webpage, a successfull handshake and get request then a stall
shouts mtu
> issues.
>
> Are you doing anything else on the as5300/nearby routers to do with
wccp/web
> caching, policy/source routing?
>
> Steve
>
> On Mon, 7 Jun 2004, Melvin C. Etheridge wrote:
>
> > THIS IS STILL DRIVING ME CRAZY!!!!!
> >
> > Could this be a routing issue?
> >
> > Help?!!!
> >
> > Mel
> >
> > ----- Original Message ----- 
> > From: "Jon Lewis" <jlewis at lewis.org>
> > To: <cisco-nsp at puck.nether.net>
> > Sent: Saturday, June 05, 2004 4:44 PM
> > Subject: Re: [nsp] RE: OK I'm Stumped!!!!
> >
> >
> > > On Sat, 5 Jun 2004, Martinez, Edwin II (contractor) wrote:
> > >
> > > > I would have to agree with Andrew's gut feeling, that it is MTU
related.
> > > > However, it won't be that easy.
> > >
> > > IIRC, several years ago, I set the framed-MTU in our default radius
> > > profile to 1500.  Many windows users were able to connect, but not
surf.
> > > It seems they really wanted to negotiate the MTU.  If you're setting
MTU
> > > via radius, try removing that from your default profile.
> > >
> > > ----------------------------------------------------------------------
> > >  Jon Lewis                   |  I route
> > >  Senior Network Engineer     |  therefore you are
> > >  Atlantic Net                |
> > > _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
> > > _______________________________________________
> > > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
>