I've tried it on several different browsers, a couple of different 
operating systems, and multiple locations connected to the COX network, 
and they all fail identically, that's what made me suspect a network 
problem in the first place.  I wonder if the problem isn't an issue 
between the COX network and the remote server.

Anyone know what kind of source filtering is present on the remote server?

I searched through everything Google found on their "Fireslayer" 
service, and is seems to be a mishmash of in-house code and other stuff 
that they refuse to specify (understandably).  I'm wondering if 
they(like some other places) are just blanking out whole blocks of IP 
addresses assigned to the Cable companies because of all the zombied 
Windows machines used for DDoS.  I can verify my systems never 
participated in such, but since the public IP addresses rotate fairly 
regularly, I wouldn't be surprised if the whole subnet was blocked due 
to others running zombies (I've seen plenty of evidence that many of my 
neighbors are running zombie systems, a lot of them are also running 
unsecured WiFi, and constantly netscanning their own WiFi looking for 
more zombie targets).  Anyone know a way to find out if that's what 
they(Ev1) are doing?


Kevin Brown wrote:

> <SNIP>
> 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
>
---------------------------------------------------
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