So you found legitimate way around the clause that explicitly prohibits running servers on residential accounts? Care to share for benefit of others?

>No.
>>Hi Claude,
>>
>>Aren't you breaking COX Acceptable Use Policy by doing that?
>>
>>>It's really very economical unless you're hosting an application that requires 99%(or significant) uptime, backups, etc. Your choices are Cable or DSL. Within Cable or DSL there are Business and Residential(including SOHO) classes. Business class will probably get you a faster connection and more freedom with the internet servers you host. The downside is that Business class will be more expensive, typically twice as much as Residential.
>>>My most recent project was to get the lowest Residential rate for Cox High Speed Internet Service ($39.95/mo.), but, still host my own web server. I'm happy to report that, with a few adjustments, my website(www.activevfp.com) is back online with this service. I'm able to network the internet connection to 3 wired computers and several wireless devices thru a Linksys router and also host a Web and FTP server(DNS and SMTP serving should still be possible too). The only hitch in hosting the web site was that Cox blocked Port 80 from http internet traffic. The solution was to have the web server listen for HTTP traffic on Port 8080. I also took advantage of Web Forwarding from NetworkSolutions to make sure that anybody that types in www.activevfp.com will be forwarded to the proper port.
>>>Another item to be aware of is if you have a static or dynamic IP address. I have a dynamic IP but it rarely changes. If it does, I can easily go to NetworkSolutions and repoint the domain to the new IP. DynDNS, a 3rd party service, is a way to automate these changes although, for me, I don't see the need, especially if it's not free. With a static IP address, you wouldn't have to worry about any of this...