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
Hosting a website on Cox Cable??
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.
I have been running an FTP server on my computer on cox since like 2000. I do not give out the info nor do I leave it open to the public, I just use it when I need to grab something when I am not at home, or when I want to work on my PHP pages from work, I have my IIS up and running so that I can do a little work on my php scripts from work and be able to test them, my website will not be public and the upload of it should be much, much less then the average kiddy sharing files.