Re: Help finding failure point accessing PLUG Website

Craig White wrote:

> On Mon, 2005-02-14 at 21:22 -0700, Joseph Sinclair wrote:
>
> from a dsl client of mine (service by getnet) 1st hop obscured
>
> # traceroute -n www.plug.phoenix.az.us
> traceroute to plug.phoenix.az.us (66.98.190.6), 30 hops max, 38 byte
> packets
> 1 216.19.999.999 46.558 ms 40.953 ms 42.937 ms
> 2 216.19.201.247 43.712 ms 43.949 ms 43.222 ms
> 3 216.19.201.248 45.150 ms 44.466 ms 44.963 ms
> 4 38.112.7.25 46.599 ms 45.778 ms 44.854 ms
> 5 154.54.1.145 72.304 ms 66.997 ms 67.612 ms
> 6 38.112.12.186 72.025 ms 70.554 ms 136.376 ms
> 7 207.218.245.110 71.009 ms 68.639 ms 68.024 ms
> 8 * * *
>
> from a sprint broadband client of mine
>
> # traceroute -n www.plug.phoenix.az.us
> traceroute to plug.phoenix.az.us (66.98.190.6), 30 hops max, 38 byte
> packets
> 1 192.168.0.254 0.221 ms 0.174 ms 0.164 ms
> 2 10.252.61.1 21.723 ms 23.587 ms 22.688 ms
> 3 24.221.37.1 31.248 ms 21.940 ms 21.810 ms
> 4 160.81.22.53 28.790 ms 28.902 ms 29.137 ms
> 5 144.228.173.22 29.542 ms 29.396 ms 29.646 ms
> 6 168.215.54.101 29.135 ms 30.699 ms 30.938 ms
> 7 66.192.255.90 60.317 ms 59.032 ms 59.917 ms
> 8 168.215.53.62 64.508 ms 65.799 ms 66.661 ms
> 9 66.192.246.123 64.547 ms 63.618 ms 139.987 ms
> 10 216.54.253.2 66.673 ms 64.244 ms 64.885 ms
> 11 207.218.245.110 97.780 ms 100.198 ms 98.326 ms
> 12 * * *
>
> from a T1 client of mine (first hop obscured)
>
> # traceroute -n www.plug.phoenix.az.us
> traceroute to plug.phoenix.az.us (66.98.190.6), 30 hops max, 38 byte
> packets
> 1 216.19.999.999 4.425 ms 2.272 ms 2.386 ms
> 2 216.19.222.233 4.279 ms 4.268 ms 4.297 ms
> 3 216.19.201.248 4.483 ms 4.362 ms 4.144 ms
> 4 38.112.7.25 5.345 ms 7.189 ms 5.691 ms
> 5 154.54.1.145 27.906 ms 27.445 ms 28.420 ms
> 6 38.112.12.186 29.159 ms 29.146 ms 29.384 ms
> 7 207.218.245.110 29.055 ms 30.716 ms 28.704 ms
> 8 * * *
>
> problem doesn't change...
> # host 207.218.245.110
> 110.245.218.207.in-addr.arpa domain name pointer
> ivhou-207-218-245-110.ev1.net.
>
> Houston - I think we've got a problem
>
> They be the problem - I'm sure someone else has already pointed this
> out.

Traceroute to ASU from anywhere and you get the same thing. The border router
is just choosing not to respond. So, that leaves two or three places that are
the problem. The browser in use or the webserver. Since it is a vhost it
requires that the server be able to figure out which host the browser really
wanted based on the headers the browser sent in the request. So, either the
browser is munging the headers that it sends and so the server doesn't respond,
or the server isn't correctly interpreting the headers to respond and is just
dropping the request.

Since the site works for others (myself included) it leaves something about
either the clients browser or they don't like him for some reason (blacklisted
by some security software or something, so a firewall at the system dumps him).
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss