🚀 go-pugleaf

Lawrence Baldwin wrote:

> John/Randy, anyone else,
>
> I tackled this one.  Bottom-line he could only load pages that were a
> few hundred
> bytes in size...or he could load pages from certain (e.g. Microsoft
> sites).

Well, first, just to eliminate some variables, I ran a traceroute to his IP:

Tracing route to alcatraz.den.co.bbnow.net [24.219.14.14]
over a maximum of 30 hops:

  1   <10 ms   <10 ms   <10 ms  ROUTER [192.168.0.1]
  2    20 ms    10 ms    20 ms  adsl-78-160-1.gnv.bellsouth.net [216.78.160.1]
  3    10 ms    10 ms    10 ms  205.152.46.65
  4    10 ms    10 ms    10 ms  205.152.46.249
  5    10 ms    20 ms    10 ms  205.152.48.93
  6    10 ms    20 ms    10 ms  205.152.111.184
  7    10 ms    20 ms    10 ms  903.Hssi4-0-0.GW1.ORL1.ALTER.NET [157.130.66.53]

  8    20 ms    30 ms    20 ms  504.at-2-1-0.XR2.ATL1.ALTER.NET [152.63.84.46]
  9    20 ms    30 ms    30 ms  194.at-1-0-0.TR2.ATL1.ALTER.NET [146.188.232.98]

 10    40 ms    40 ms    40 ms  109.at-5-0-0.TR2.DFW9.ALTER.NET [146.188.141.30]

 11    40 ms    50 ms    40 ms  188.at-1-0-0.XR2.DFW9.ALTER.NET [152.63.98.41]
 12    40 ms    50 ms    40 ms  184.ATM7-0.BR1.DFW9.ALTER.NET [152.63.98.133]
 13    50 ms    50 ms    50 ms  atm4-0.core2.Dallas1.Level3.net
[209.245.240.137]
 14    40 ms    50 ms    50 ms  so-6-0-0.mp2.Dallas1.level3.net [209.247.10.109]

 15    80 ms    80 ms    90 ms  209.247.8.73
 16    80 ms    90 ms    80 ms  so-0-1-0.mp1.LosAngeles1.level3.net
[209.247.8.69]
 17    90 ms    90 ms    90 ms  209.247.153.106
 18    80 ms   100 ms    81 ms  den-r5-1-a5001.i3s.net [24.219.27.113]
 19   661 ms   521 ms   501 ms  10.48.1.62
 20   400 ms   471 ms   401 ms  alcatraz.den.co.bbnow.net [24.219.14.14]

Trace complete.

Nasty delay there at hop 19.  Next I verified that 1400 byte packets were still
being dropped by his IP (they were).  Then I wanted to see if any hops BEFORE
his IP were also dropping them.  Hop 19 is not a reachable address, and Hop 18
apparently doesn't answer pings (regular pings were getting no answer either).
Hop 17 responded to 1400 byte pings normally.  So, it's either his computer or
the routers at hops 18 or 19.  Unfortunately, if it was ANY of the routers, it
would be the one at 19 I would suspect, with that huge delay on it.  In fact
that delay is so huge (half a second?), that I suspect that there is something
going on there.

I'm not sure where to go from here.  I've only run into a similar problem once,
and it was a router or DSLAM problem that was fixed after 8 days without anyone
informing us of what was wrong.  I'm sure you had him run the tweak diagnostic
applet at dslreports?

Randy S.