[olug] Cox and Web Servers

[Trent Melcher]

Well they are blocking it in the Elkhorn area.  I actually had it
running directly on port 80 until we switched to cox.net from @home,
@home never gave me this trouble.

Trent

-----Original Message-----
From: olug-admin at olug.org [mailto:olug-admin at olug.org] On Behalf Of Phil
Brutsche
Sent: Tuesday, October 08, 2002 9:08 PM
To: olug at olug.org
Subject: Re: [olug] Cox and Web Servers

A long time ago, in a galaxy far, far way, someone said...

> How does everyone else work around Cox blocking port 80?

Cox doesn't block port 80.  The block went away when we swiched to
cox.net
from home.com.

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

Almost any port # you want (don't choose stuff like 25, 137-139, 111,
etc), and yes.

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

It's not terrible business practice.

It's smart security, in the face of Nimda and Code Red.

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

There isn't one.  DSL is available, but the speed doesn't compare and
costs more.  And isn't available everywhere Cox is.

-- 

Phil
phil at brutsche.us

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