Cox has good tech support and pretty good uptime --- maybe 2 or 3 days in the last year have we had any trouble with the loops in the nearby city. IIRC, they implemented blocking in the spring of '03. 'Twas a tad poorly done, 'cause they just blocked port 80 (and possibly 25) wholesale for entire subnets. I'm guessing it was a for a number of reasons, not the least of which was the bandwidth still being eaten up by the CodeRed/Nimda bugs (although they say they have b/w to burn....)

The reason it was 'poorly done', IMO, was that they didn't bother checking who on those subnets had "permission", if you will....so I spent some time wondering where my domains had gone that morning....

Yes, Cox does allow hosting, at least in the local markets here; but you must purchase a "business" cable connection and pay for a static IP, which in my local market is something on the order of $70/month. The "express" package, or whatever it's actually called, is about $27 and DHCP. Also, you get more b/w on the "business" setup. I've seen downloads > 100Kbps; max on the lite setup (IIRC) around 10-20Kbps.

Now, if they'd just run a loop out here.... :rolleyes:

    Hrmm...you must have a different package out there dale. Out here, for the basic DHCP package, I'm paying just over $40/month. But my downloads are typically 200-400 kb/s.

      Although I'm not on Cox, I've been on Time Warner and I'm currently on Adelphia. I've had a web server up on both. Both have blocks on port 80.

      I just setup Apache to listen to port 7777 instead of port 80. Then I have to do [url]http://[/url][ip address]:7777/ and I'm on my server.

      This won't be acceptable if you're looking to assign a domain name since the domain names default to port 80. You must have a static IP address. This is when you start getting into the "business" level of service. But if you're just tinkering around and wish to access your web server from outside, its just a matter of changing the ports around.

        Which is all well and good, but if Cox drops your connection, you've been warned in their AUP...

        You may not operate, or allow others to operate, servers of any type or any other device, equipment, and/or software providing server-like functionality in connection with the Service, unless expressly authorized by Cox.

          Originally posted by LordShryku
          Hrmm...you must have a different package out there dale. Out here, for the basic DHCP package, I'm paying just over $40/month. But my downloads are typically 200-400 kb/s.

          Heh, maybe everything is different here. Didja see the "fuel prices" thread?

          Anyway, I might be wrong about current pricing; I may have also messed up the dload speeds. Best I can recall, that's what it was the last time I talked to anyone. The most recent change to any of my clients down there was the addition of a 2nd static IP to one modem; seems like that was about $15/month.

          Of course, nothing says that service in Carthage, MO has to be the same as Phoenix, AZ, does it? 🙂

            Very true, very true. Now if I could just someone to sponser say....a T1 line into my house, I wouldn't have to deal with these guys! 😃

              Yes, indeed! I'm actually kinda lucky, I think: My wife's boss (another home business) has a "T1" line into his house. I keep giving him free help. Hopefully soon he'll want a domain for his biz, and then I'll move a box in.... woot! 😃

              On a related subject:

              Heh, heh, this morning is one of those "2-3 days" I referred to. LordS, definitely hoping that Phoenix is not like Carthage is today!

              #ping carthage
PING carthage.cox-gateway.net (66.76.92.1): 56 data bytes
^C
--- carthage.cox-gateway.net ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
#traceroute carthage
traceroute to carthage.cox-gateway.net (66.76.92.1), 64 hops max, 40 byte packets
 1  69.27.132.135 (69.27.132.135)  159.901 ms  158.723 ms  150.855 ms
 2  69.27.132.188 (69.27.132.188)  154.679 ms  154.700 ms  159.870 ms
 3  tulsok6wcx3-ser5-0.wcg.net (64.200.227.141)  164.795 ms  164.729 ms  154.861 ms
 4  * dllstx1wcx3-oc48.wcg.net (64.200.240.81)  240.003 ms  185.780 ms
 5  dllstx2wcxb-pos9-0.wcg.net (64.200.110.194)  163.798 ms  164.797 ms  160.847 ms
 6  dllstx2wcx1-cox-peer.wcg.net (64.200.232.214)  158.575 ms  149.776 ms  149.850 ms
 7  dllsdsrc01-pos0901.rd.dl.cox.net (68.1.0.145)  159.697 ms  157.746 ms  161.863 ms
 8  68.1.206.6 (68.1.206.6)  162.474 ms  155.798 ms  149.832 ms
 9  dllsbbrc02-gex0101.ma.dl.cox-internet.com (66.76.45.2)  149.804 ms  158.692 ms  159.848 ms
10  * * *
11  * *^C

                well I setup apache to listen to 18762, I can do localhost:18762 hits and hit my own site with however not able to hit it from the outside world. I am running ZoneAlarm and have already set Apache to Server and given it FULL internet access. My FTP is working fine on port 18763.

                Not sure as to why it is not working, onless cox is just blocking all incomming HTTP Header request. I am not looking to host a full out site, just have testing grounds so I can show my scripts to friend and people at work.

                If you wanna try to hit the site, try hitting

                thanks

                  Score, it was my stupid firewall, it appears to not let people make request even with zonealarm reconizing apache as a Sever. I will have to look into it a bit more and see why zonealarm is not working with it, does anyone have any suggestions as to any other firewall software or what option in zonealarm I might be missing?

                  thanks

                    Just a guess: is ZA smart enough to realize that Apache is listening on a non standard port?

                    Maybe it's opening :80 for it....

                      I do not think it is smart enough to know, I have tried to get it to open incomming and outgoing TCP port 18762 but that did not seem to work, I am going to try some other firewalls, ZA is making me mad, now it is also blocking my FTP

                        So you've got your server running on Cox, then?

                          Yes i did, running it on a different port, had to remove my firewalls and such, now I am reading up on how to get a firewall up and make it work with Apache, otherwise I might just use IIS 🙁

                            So clause six of their Acceptable Use Policy doesn't apply to you, then?

                              ... or are you just choosing to ignore it...

                                I chose to ignore it once. Like I said the first time around, when they scan, if they find you, they may not like you for a while...
                                ie. Shut off your connection until you grovel and apologize profusely.

                                  So they portscan you? Is that legal?

                                    It's not that they portscan individuals, but they scan their networks for server-type traffic. I don't remember all of the details, becuase I was just trying to get my internet back, and was fairly PO'ed. My friend said they got him for running a FTP server also.

                                      Originally posted by cafrow
                                      Yes i did, running it on a different port, had to remove my firewalls and such, now I am reading up on how to get a firewall up and make it work with Apache, otherwise I might just use IIS 🙁

                                      I'm not sure what IIS will do differently. This is really a networking issue (mainly port forwarding to be exact). I'm a big fan of those cable/dsl routers. They're pretty cheap ($50 for a WAP/cable/dsl router w/4 ports). It will allow you to easily establish your routing rules without having to get network certifications to do it. These routers will not filter content, but the port forwarding and NAT is really what you need. Keep zone alarm on your PC, but just have it monitor your PC and not the entire network (unless you know what you're doing).

                                        Originally posted by LordShryku
                                        I chose to ignore it once. Like I said the first time around, when they scan, if they find you, they may not like you for a while...
                                        ie. Shut off your connection until you grovel and apologize profusely.

                                        I've had a "server" (more like a PC) up and running since about '98. Granted, I'm not trying to do any commercial work (make a buck off of it) nor am I doing heavy amounts of traffic.

                                        As for port scanning, sure they can port scan you. Heck, the rest of the world is port scanning you anyways, there's not much difference if they jump in. I'm not sure if its in an ISPs best intrest to do so since it takes CPU cycles to port scan all their nets. What I'd predict they do is they look at their router logs and see if there's abnormalities to their users' upstream rates. Then flag any questionable ones. They really don't need to port scan if their logs provide enough details.

                                          Write a Reply...