I have Comcast HSI (formerly Comcast@Home), and I noticed about a week before they transitioned me from @Home, that port 80 was blocked. So, my web site was down for about a week. After the transition it was back. I think @Home has just closed it, possibly in an effort to cut out as much as they can before crashing straight into the sun.
...you can always change the port numbers in your server (tricky) and/or webserver (easier) to alleviate the problem (unix)? I forgot how to do this in win-nt/2000. In Mac OS X (not the Server version), I don't know if it is a good idea to play with the httpd.conf file.
...changing port numbers is also good to discorage hack attacks (port scanning can offset this).
On a side note, I don't blame Cox and other cable companies for closing some of the port numbers available to their users - it may suck ass but some people take advantage. I'm sorry to say I'm one of them - my website pushes about 500MB on an average day. Why do I do it? I'm poooooooooooooooor!
What is wrong with them!?
Comments
Port 119, which was blocked by @Home since forever is unblocked too.
The only ports blocked now are the NetBIOS Windows Networking ports...137-139 and 1080.
...changing port numbers is also good to discorage hack attacks (port scanning can offset this).