Subject: RE: request time out with one site
jblagg@dataflowalaska.com
Date: Fri Dec 28 2001 - 11:07:33 AKST
Greg,
Have you considered that there may be blocking on the other end?
DSL aggregators are known as the source of DDOS attacks (lots of
unprotected MS boxen, plenty bandwidth) and the targets of those DDOS
may have blocked entire networks at one time, and forgotten to take them
down. (happens more than you think, six or seven folks configing the AC
list on a major router, somethings are bound to get lost)
Yours,
John B.
-----Original Message-----
From: aklug-bounce@aklug.org [mailto:aklug-bounce@aklug.org]On Behalf Of
Greg Hagele
Sent: Thursday, December 27, 2001 9:22 PM
To: Jim Gribbin
Cc: James McMorris; AKLUG
Subject: Re: request time out with one site
oops, I got my fingers dyslexic and did the pb not bp. here is the
www.bp.com
site
Tracing route to www.bp.com [208.254.0.207]
over a maximum of 30 hops:
1 146 ms 142 ms 134 ms pm6.nwc.alaska.net [209.112.154.6]
2 137 ms 134 ms 134 ms fe0-0-100-cr1.nwc.alaska.net
[209.112.154.30]
3 137 ms 132 ms 134 ms 12.124.174.5
4 179 ms 177 ms 177 ms br2-h30.st6wa.ip.att.net [12.123.203.2]
5 180 ms 177 ms 179 ms gbr1-p70.st6wa.ip.att.net [12.123.44.57]
6 179 ms 174 ms 174 ms gbr3-p70.st6wa.ip.att.net [12.122.5.157]
7 196 ms 192 ms 192 ms gbr4-p40.sffca.ip.att.net [12.122.2.197]
8 190 ms 192 ms 189 ms ggr1-p370.sffca.ip.att.net
[12.123.13.69]
9 198 ms 194 ms 194 ms att-gw.sf.uu.net [192.205.32.126]
10 197 ms 199 ms 197 ms 0.so-2-1-0.XL1.SAC1.ALTER.NET
[152.63.52.226]
11 196 ms 197 ms 194 ms 0.so-3-0-0.TL1.SAC1.ALTER.NET
[152.63.53.250]
12 261 ms 259 ms 259 ms 0.so-6-0-0.TL1.DCA6.ALTER.NET
[152.63.13.18]
13 259 ms 257 ms 257 ms 0.so-6-0-0.XL1.DCA6.ALTER.NET
[152.63.38.70]
14 259 ms 257 ms 257 ms 0.so-6-0-0.WR1.IAD6.ALTER.NET
[152.63.39.113]
15 267 ms 259 ms 254 ms 0.so-0-0-0.UR1.IAD6.Alter.Net
[157.130.59.70]
16 264 ms 259 ms 259 ms 206.112.64.21
17 262 ms 262 ms 259 ms 206.112.65.36
18 257 ms 257 ms 259 ms 208.254.2.5
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * *
greg
Jim Gribbin wrote:
> Just noticed something else. Interesting how even tho ASC is
supposedly
> combining all the ATU, PTI, & IA servers, we get compleatly different
> routing, right from the start.
>
> Just remembered, I used to have a problem getting to ANANDTECH from
home
> using IA but I could get there without problem from work using GCI. I
> cann't find it now, but someone had a link to an arcticle about how
> there were some pages that were not possble to get to from some
> locations. Nobody understood why this happens - one of the great
> internet mysteries.
>
> Jim
>
> On Wed, 2001-12-26 at 00:34, Greg Hagele wrote:
> >
> > That's kind of what I was thinking. I use ACS and have been running
DSL;
> > and until they just switched over to a new server, had no problems
with
> > this site or any other one for that matter. There is an other sites
I
> > can't get to also http://www.bp.com is one.
> >
> > Here is the type of trace I get with the sites I can't get to
(below).
> > Would it be logical to think that there is something at the ACS
server
> > that's not letting this and other sites through. Also why only
selected
> > sites, not all, could it be net congestion? or more likely the proxy
> > idea?. Any ideas? The more I know before I call ACS the more help
I may
> > get from them, if in fact the problem is there.
> >
> > Tracing route to www.bp.com [208.254.0.207]
> > over a maximum of 30 hops:
> >
> > 1 <1 ms <1 ms <1 ms 192.168.7.1
> > 2 51 ms 49 ms 49 ms 172.16.254.254
> > 3 47 ms 48 ms 46 ms 10.1.254.2
> > 4 49 ms 47 ms 47 ms fe4-1-0-cr1a.nwc.acsalaska.net
> > [198.70.245.1]
> > 5 * 76 ms 75 ms s8-0-0-cr1.sea.acsalaska.net
> > [208.151.100.166]
> > 6 75 ms 77 ms 78 ms aanet-sea.above.net [209.249.0.161]
> > 7 79 ms 77 ms 77 ms core3-core4-oc3.sea1.above.net
> > [208.185.175.93]
> >
> > 8 125 ms 127 ms 127 ms ord2-sea1-oc48-2.ord2.above.net
> > [208.184.232.57
> >
> > 9 126 ms 125 ms 127 ms core3-core2-oc48.ord2.above.net
> > [208.185.0.194]
> >
> > 10 132 ms 130 ms 130 ms uunet-abovenet-oc12.ord2.above.net
> > [208.184.231
> > 50]
> > 11 143 ms 143 ms 132 ms 0.so-5-3-0.XL2.CHI2.ALTER.NET
> > [152.63.68.178]
> > 12 132 ms 130 ms 132 ms 0.so-2-0-0.TL2.CHI2.ALTER.NET
> > [152.63.67.109]
> > 13 164 ms 155 ms 222 ms 0.so-3-0-0.TL2.DCA6.ALTER.NET
> > [152.63.19.170]
> > 14 167 ms 153 ms 152 ms 0.so-6-0-0.XL2.DCA6.ALTER.NET
> > [152.63.38.74]
> > 15 156 ms 157 ms 157 ms 0.so-6-0-0.WR2.IAD6.ALTER.NET
> > [152.63.39.117]
> > 16 154 ms 155 ms 234 ms 0.so-1-0-0.UR2.IAD6.Alter.Net
> > [157.130.59.82]
> > 17 253 ms 156 ms 156 ms 206.112.64.37
> > 18 156 ms 155 ms 153 ms 206.112.65.36
> > 19 217 ms 157 ms 157 ms 208.254.2.5
> > 20 * * * Request timed out.
> > 21 * * * Request timed out.
> > 22 * *
> >
> > It then goes on like this until it's stopped
> >
> > greg
> > ----------------------
> > James McMorris wrote:
> >
> > > This is probably no help, but I was able to see both sites with
IE6 on
> > > a Windows machine.
> > >
> > > By chance, it there a proxy somewhere between you and the site
that's
> > > blocking it? (This is the only "constructive" idea I had.)
> > >
> > > -Jim "Buddha" McMorris
> > >
> > > ----- Original Message -----
> > > From: Greg Hagele <ghagele@alaska.net>
> > > Date: Tuesday, December 25, 2001 2:44 pm
> > > Subject: request time out with one site
> > >
> > > >
> > > > I have been attempting to get into my banking site. when i try
> > > > going to the
> > > > secure page, from the main page, http://www.wellsfargo.com
(click
> > > > on the Online
> > > > Banking top right corner) the page will not load. It just says
> > > > "contactedhost waiting for reply" and never loads. I called
the
> > > > guys down in the lower
> > > > 48 and they said the direct page was banking.wellsfargo.com
> > > > I attempted that but no joy, they said they had no problems
> > > > getting in to the
> > > > page there. I can get to other secure sites and surf without
> > > > delay. Any ideas
> > > > on why this page may be not letting me in. I have tried a
couple
> > > > of different
> > > > computers and web browser Explore and Netscape with the same
result.
> > > >
> > > > thanks
> > > >
> > > > greg
> > > >
> > > >
> > > >
> > > >
> >
> >
> >
This archive was generated by hypermail 2a23 : Fri Dec 28 2001 - 11:12:08 AKST