Subject: Re: request time out with one site
From: Jim Gribbin (jgribbin@alaska.net)
Date: Wed Dec 26 2001 - 19:56:56 AKST
I'm still trying to get a handle on this networking stuff, so I'm not
shure. It almost looks like you're going through 2 or 3 layers of local
servers before you get to Internet Alaska (ACS). Here is my traceroute
for comparison:
[root@be6 /root]# traceroute www.bp.com
traceroute to www.bp.com (208.254.0.207), 30 hops max, 38 byte packets
1 192.168.0.1 (192.168.0.1) 1.242 ms 0.374 ms 0.346 ms
2 cr2.nwc.alaska.net (209.112.154.245) 38.815 ms 33.290 ms 55.735
ms
3 fe0-0-2-cr1.nwc.alaska.net (209.112.154.110) 34.459 ms
fe0-0-2-cr3.nwc.alas
ka.net (209.112.154.108) 33.943 ms fe0-0-2-cr1.nwc.alaska.net
(209.112.154.110)
34.784 ms
4 12.124.174.9 (12.124.174.9) 45.435 ms 12.124.174.5 (12.124.174.5)
49.595 m
s 35.094 ms
5 br2-h30.st6wa.ip.att.net (12.123.203.2) 91.108 ms 78.236 ms
113.100 ms
6 gbr2-p70.st6wa.ip.att.net (12.123.44.61) 81.004 ms 84.585 ms
79.532 ms
7 gbr3-p80.st6wa.ip.att.net (12.122.5.165) 78.384 ms 98.472 ms
78.232 ms
8 gbr4-p40.sffca.ip.att.net (12.122.2.197) 157.037 ms 101.675 ms
127.102 ms
9 ggr1-p370.sffca.ip.att.net (12.123.13.69) 106.143 ms 94.628 ms
96.847 ms
10 att-gw.sf.uu.net (192.205.32.126) 117.469 ms 100.216 ms 99.484 ms
11 0.so-2-1-0.XL1.SAC1.ALTER.NET (152.63.52.226) 98.709 ms 98.459 ms
121.386
ms
12 0.so-3-0-0.TL1.SAC1.ALTER.NET (152.63.53.250) 102.965 ms 113.824
ms 99.64
5 ms
13 0.so-6-0-0.TL1.DCA6.ALTER.NET (152.63.13.18) 165.677 ms 159.605
ms 190.71
1 ms
14 0.so-6-0-0.XL1.DCA6.ALTER.NET (152.63.38.70) 158.913 ms 158.262
ms 159.38
7 ms
15 0.so-6-0-0.WR1.IAD6.ALTER.NET (152.63.39.113) 162.536 ms 158.552
ms 159.5
13 ms
16 0.so-0-0-0.UR1.IAD6.Alter.Net (157.130.59.70) 165.801 ms 167.036
ms 160.341 ms
17 206.112.64.21 (206.112.64.21) 163.308 ms 174.890 ms 186.894 ms
18 206.112.65.36 (206.112.65.36) 159.355 ms 159.946 ms 165.915 ms
19 208.254.2.5 (208.254.2.5) 162.058 ms 172.274 ms 163.501 ms
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
BTW - I am also on their DSL, but it the idsl (isdn over frame relay)
variety.
Jim - stabbing in the dark.
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 : Wed Dec 26 2001 - 20:13:21 AKST