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.
Sorry for the noob questions.
I'm also experiencing the issues with port forwarding with my Panoramic Wifi (Technicolor) modem/router setup. Can you provide a bit more detail? I am in the following area: Advanced > Port Triggering > Add Port Trigger. I need to forward ports 7777 and 27015 both TCP/UDP. How do I enter this? Also, how do I specify which device to route traffic to?
Port Forwarding requires that you use the Cox Wifi app - not the modem's web browser config. Port Forwarding is for when you need an outside client to be able to connect to your PC or device (like Remote Desktop or Plex). When in the Cox Wifi app, go to Network (at the bottom) > Gateway > Advance Settings (scroll down) > Port Forwarding > Add Port Forward. You will then have to select the CONNECTED device that you need a port forwarded to under "Select One", input the port number that you are looking to forward and lastly, select the proper protocol.
If you have an internal device that is being blocked by Cox's Maximum Security Firewall software settings, such as a Nest Gen 3 Thermostat like I have, then you will have to go to your web browser, log into the modem config page and enter a Port Trigger from the Advanced > Port Triggering section. I had to create a Port Trigger for the Nest thermostat with the following values: TCP, Trigger and Target Ports: 9543-9543. Note that this does not expose port 9543 to the internet - instead it allows data that the Nest sends out (from one port) to be returned via port 9543. The game Guild Wars 2 requires TCP port 6112 to be triggered. Discord requires a very large UDP port triggering range for voice (UDP 50000-65535) though I did not need to trigger the TCP port for Discord chat. I also needed a specific TCP port triggered for a VPN connection I use otherwise, I could not connect. Lastly, you will not need to specify a specific device for a Port Trigger entry like you will for a Port Forward.
Thank you for your reply -and for explaining the difference. I've setup a game server for Ark Survival Evolved, which requires ports 7777, 7778 and 27015. I've entered them into the Wifi app (using the webpage wifi.cox.com) instead of the modem's web interface. I also made sure that the firewall settings in Windows 10 were allowing the server traffic as well.
Unfortunately, the ports still appear to be closed when scanning with a webpage like canyouseeme.org. Am I still doing something wrong?
