New Contributor
•
1 Message
Cox Panoramic recent update is blocking my port forwarding
Is anyone else having the same issues with their Cox Panoramic router after the recent update? My security cameras can no longer be viewed and after speaking with numerous Cox reps, they had no answers or possible solutions for me. I completed a hard reboot on my router, they did not work. I set up triggers instead of port forwarding, that did not work. My ports are 100-107 which is not on the blocked list.
My last option is to purchase a different system altogether and throw this unit in the ocean. I also noticed after the update and being forced to use the cox wifi app my gig speed is about 500mbs.
Please let me know if anyone has a solution before I start buying new equipment.
Thanks.
DannyS
Moderator
•
591 Messages
0
0
Garry_Jay
New Contributor
•
2 Messages
Same here, can't view my security cameras either, apparently port forwarding no longer works. I talked to support and to make a long story short, they had no idea and told to contact the router manufacturer.
0
0
auddsnends757
New Contributor
•
1 Message
my smart washer and dryer and ring doorbell disconnected and I have tried everything to reconnect. Not sure if it’s related but Also moca is enabled and I am unable to disable it.
i hate cox, seriously about to leave cox and go with TMobile or some other cellular data internet.
2
0
Jellygrape
New Contributor II
•
7 Messages
I had issues with certain devices and programs not working when I enabled the maximum (high) firewall security on the modem. I found that instead of port forwarding, I needed to enable a “port trigger” so that the outgoing traffic could return via the specified port. This affected my Nest device, Discord, and VPN connections, among many others. Once I determined the correct port to set for triggering (and whether to use UDP, TCP or both protocols), I entered that info in the router’s (Advanced) config. Upon establishing a proper port trigger, all devices and programs that need to connect to an outside IP now work without issue. Have you made sure to select the proper port trigger protocol - or choose both UDP & TCP if in doubt? The alternative was to restore the modem’s security settings back to typical (medium).
My affected PC is connected via MoCA and while this resolved most of my software problems, I, like another who reported, cannot forward ports for MoCA devices. This has left me unable to forward the port for Remote Desktop because the router does not presently allow MoCA port forwarding.
3
0