I guess it is time to put my 2 cents in on all the cox stuff. 1. cox does not block the port for https which is ssl for http (hint), or they use not to, but they do block http (port 80) for sure.
2. cox does give you some webpage space on their server, so if you have problems with them pushing dhcp addresses you could write a small script that grabs your IP, then ftps it to the cox server, and then cron the job to run every hour like this: (http://members.cox.net/magoolsu/info/info.html) If you want the script that does this just email me. Strangely enough my ip has not changed for several days. 3. You could always run apache (web server) on a not trivial port and then just hand out your ip as <ip>:<port number>. You then could use the webspace given to you by cox as the front of your website and link back to your own server, and or some combination of these. Hope this helps Dennis On Mon, 2003-07-14 at 12:30, will hill wrote: > Some Cox lines, like mine, are noisy. It comes and goes. When it got really > bad, I called them. They sent out a repairman with a noise meter. He > replaced the line in my backyard and that helped some. After the Toledo FBI > raids, I quit using my cable modem for anything but browsing and email. > > I've been told that they push new DHCP addresses every 8 to 24 hours. That > and port blocking are done to enforce their "no servers" policy. Who knows, > they might have decided they don't like TS. > > > On 2003.07.13 23:51 Dustin Puryear wrote: > > I connect over Cox cable to a Win2k TS on a regular basis, as do some > > others, and I've noticed it can be hard to keep a connection up. Is this > > pretty standard? Anyone have problems keeping a connection going for a long > > time on Cox? The server is on Cox, while I'm on DSL. No real problems on my > > end. > > > > > > _______________________________________________ > General mailing list > [email protected] > http://brlug.net/mailman/listinfo/general_brlug.net -- Dennis emerge -p world http://members.cox.net/magoolsu
