[olug] Cox and Web Servers

[Jacobs, Robert A.]

Tell Apache to listen on a port other than "80" for connections.

When I first signed up with COX, I went round and round with them about
this very issue.  I spoke to a number of individuals above the "phone techs"
and was met with stony silence.

I offered to let them put a traffic shaper on my account and they still
would
not budge.  It was a hopeless endeavor.  I wanted to work with them; they
wanted
to milk me for more money.

In the end, I told Apache to listen on an obscure port and, if they knew,
they
never bothered me.

-----Original Message-----
From: William E. Kempf [mailto:williamkempf at hotmail.com]
Sent: Tuesday, October 08, 2002 3:29 PM
To: olug at olug.org
Subject: [olug] Cox and Web Servers


How does everyone else work around Cox blocking port 80?  Specifically, is
there some other port you'd recommend running on instead, and is there some
service similar to dyndns that would map an URL transparently to this
alternate port?  Maybe it's just wishful thinking, but it seems like such a
service could be provided.  If not, short of paying Cox the ridiculous fees
they want for a business connection, which this isn't, is there any other
way to get Cox to open the port up, such as complaining to the right
individual about how this is a terrible business practice on their part.
And lastly, if there's no palatable answer to any of these questions, is
there an alternative high speed Internet provider that doesn't block ports
and sits in the same general price range as Cox?

Bill Kempf
_______________________________________________
OLUG mailing list
OLUG at olug.org
http://lists.olug.org/mailman/listinfo/olug