Forum Discussion
First, the easiest solution would be to buy your own router. Since you have fiber, the gateway is in router mode with the ONT acting as the modem, so any normal router with a ethernet WAN port and DHCP should work. If you pay for the gateway, not only will this save you money and fix your problem, but a retail router will almost always beat a Cox gateway by way of features/security/performance. Cox gateway also uses band steering and automatic channel selection that can't be disabled which causes problems with IoT like wifi cameras. Never mind it is missing the VPN and VLAN capability you should use when using IoT remotely.
With that said, the port forwarding feature is hit or miss. It isn't really known why it works for some and not others. See post here. It could be a firmware issue, where swapping it out for a different will work. Or it could be a issue with the XB7/8 while you had the XB6 before. Either way, Cox doesn't support port forwarding anymore(probably because servers are against ToS) so if you even want to troubleshoot it with them, you have to pay 10$ for Cox Complete Care.
Thanks for your feedback. I am rapidly reaching the same conclusion, that buying my own router is the only solution.
I hope you see the rich irony of a company selling a service that (as far as forwarding) doesn't Work, then expects the customer to replace what they themselves are already paying for just to make it work. What the heck ISP (outside of china/Iran / North Korea / Russia blocks port forwarding?
I hope someone at Cox reads this post and gives me the official company line.
- WiderMouthOpen3 months agoEsteemed Contributor II
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.
- aroutley3 months agoNew Contributor II
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.
- ChrisJ23 months agoModerator
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.
Related Content
- 2 years ago
- 5 years ago
- 12 years ago
- 4 months ago