Port forward on cox Gateway router.
Dear Cox internet support Last week I signed up for Cox fiber to the home and I was given the following Cox router as my Gateway:- Modem / Router Details MAC Address: 10:E1:77:2A:F3:A4 Model ...
Forum Discussion
First, they aren't blocking port forwarding, they just don't help you make it work. Some people have no problems port forwarding. Also, most people don't need port forwarding. First because most people don't have special requirements for NAT, and those that do use UPnP which works by default. Also, like I said before, since running a server is against terms of service(ToS) there really isn't a incentive to fix port forwarding since many people use it to run servers. They don't so much care about someone gaming, since that doesn't use up a lot of upload bandwidth, but cameras, web servers(8080) and other things do.
Also, many ISP in the US don't work with port forwarding because they use CGNAT. Most cellular providers and some fiber providers and Starlink all use it. There are ways around it, but they are technically complex.
Speaking of which, have you considered using a VPN? Openly exposing your cameras to the internet is not safe specially with all the hacks and exploits going on. See here.
So yea, if you are technical enough to need port forwarding, you should be using your own router anyway, SPECAILLY with fiber. Consider this a blessing in disguises to get off their junk hardware.
This is a web camera consuming a couple of kilobits at most. I don't wish to put it through a VPN because that means only I can view it not anyone else.
I have a paid commercial agreement with Cox communication to receive 300mbs of bandwidth to my door downstream AND UPSTREAM via fiber. it's in my contract. Nowhere in the contract can they dictate to me how I use that bandwidth.
if they block, throttle, inhibit or stop me using this two-way communication channel that I am paying for then they are in breach of contract. the ball is in Cox's Court to explain why this is not working, and get it fixed. Deploying a crap router to a customer's premise is no excuse.
Hi, there. The answers provided are essentially correct. We are not blocking all ports, though we are blocking some at the cable modem level: https://www.cox.com/residential/support/internet-ports-blocked-or-restricted-by-cox.html . If these are not the ports you are using, they should be open.
hi Chris
Thanks for confirming that inbound traffic is not blocked. So it begs the question, who will help me if it doesn't work on a cox router? (the call center doesn't even know what port forwarding is, let alone fix it up).
can you please provide a direct contact+email of someone who could troubleshoot please?
i need to set up additional services that must work from the internet and this is now day 7 of it not working. i have a home fiber link for this reason.
thanks!
aroutley, we do have Cox Complete Care for $10 per month who will be glad to help you with port forwarding. Check out https://www.cox.com/residential/completecare.html?campcode=cta-learnmore-srch-promo-res-cox-complete-care-nc. Thanks, Lisa, Cox Support Forums Moderator
Do you have a commercial agreement as in Cox Business Service? If so, that changes things both hardware and support wise. If you have residential service, you must abide by their acceptable use policy.
"5. Servers. 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."
Not that it's enforced that much. Think of it like the speed limit on the road. It is more enforced when the rule is broken to the extend that it causes a disservice to other users. I was only explaining that to show why Cox probably isn't keen on fixing the port forwarding issue. First Cox moved port forwarding from the local GUI to a website. Then they moved it from the website to the Panoramic app. Then that broke for some. Some fixed it by getting their gateway reprovisioned. Some fixed it by turning off MoCA. Some fixed it by swapping gateways. Either way, it won't be something Cox will support without paying. It is outside Cox's normal scope of support. Ball is in your court. Either pay for CCC(and hope they can even make it work) or get your own router.
I just don't understand why you want their hardware. Can't control the firmware, limited features and performance, and it can cost you monthly. With fiber, it's easy to use your own router. You just unplug the ethernet from the old gateway and connect it to WAN port of new router.
As for not using a VPN, your network, your risk to take. Just know that it's a risk. See discussion here or google it for more info.
Hello WiderMouthOpen
Most ISPs have that clause buried in the fine print of their agreement somewhere on page 562. It's a leftover for networks with huge dissymmetry between upstream and downstream, such as cable modem providers (where Downstream is in the gigabits and Upstream is only tens of megabits). Cox is a cable company providing mainly DOCSIS services.
In my particular case I have 300 MB upstream + downstream which would hardly stretch any network capacity if I used 1kbs Upstream. Shouldn't that clause be removed for customers like me? If not now, when then? It's a little perplexing for Cox to offer such an amazing Network, but show little interest in having customers actually USE all that bandwidth. Furthermore I live in a small town in Arizona where most people won't even know how to host a server from their home, let alone do it.
As for your suggestion I probably will end up swapping out the router to solve the problem.
Thanks for your tip on security. I normally firewall everything and just leave one or two services running on port 80. I'll take that risk.
Regards Andrew
The AUP rules are put there for two reasons. First, Cox can use it as a reason to suspend or terminate someone's service that they see using a lot of bandwidth. Fiber/FTTP may have more bandwidth upstream then HFC/DOCSIS but it is still not unlimited and it is still shared. Someone seeding BitTorrent all day will raise a red flag if the bandwidth use on the node is high enough. Second, Cox has decided that anyone needing things like unblocked ports, unlimited bandwidth and server use should use Cox Business. It's a upsell possibility. Like it or not, that's just the way it is.
Also, something else to consider, part of the reason Cox can't fix the issue is because the platform behind(xFI) it is licensed from Comcast. There are differences between the Comcast app and Cox app but there is also lots of overlay. So even if Cox wanted to troubleshoot the port forwarding issue, the process to do so wouldn't be easy/cheap. I did find a work around for xFI though, so maybe that might work? What is the exact problem you are having setting it up? You mention port 80. FYI that port is blocked by Cox.
