Visitor
•
2 Messages
Port Forwarding is blocking certain ports
This has been plaguing me for a few months. I'm able to forward ports 80 and 443 and can verify I can toggle the ports open/close. However, whenever I want to open up other non-standard ports, such as game-server ports like 7707 or 20560, the app/router says they're open, but the game itself and other 3rd party tools says the ports are still closed.
I thought it was an issue with the Xfinity Gateway, so I factory-reset it and still had the same issues. I got an approved Netgear modem/router (C7000v2) and achieved the exact same result: common ports like 80 and 443 can be opened but most other ports remain closed even when they should be open.
I've already contacted customer support but they only send me to the self-help documentations and pass me around, resorting to sending a tech to take a look.
flatlander3
Problem Solver
•
1.5K Messages
2 years ago
You didn't say what you trying to point your open ports at, but windows is notorious for spawning services on the local loopback interface, and not on an Ethernet address. You can see that with an administrator cmd prompt and netstat -ab. Windows defender (advanced firewall), and anti-virus programs, especially if you are using a web shield/proxy VPN feature will block ports too. You might have to add an exception to allow the service. You might also have to specify which IP address to bind the service to.
You might have to make a firewall rule with Linux too, there's the same local vs external IP for the service issue, plus a remote permission issue with connecting to something like a database application.
You can try to connect to the ports you think you have a service running on from another box on your network, or use a utility like nmap on another computer to scan the device you have the services running on from your local network. See if there are actually the ports available that you expect to be open as a first debugging step to take the router config out of it.
Xfinity tech support isn't going to be able to help you with running services, or a configuration on a 3rd party gateway.
(edited)
2
flatlander3
Problem Solver
•
1.5K Messages
2 years ago
Oh. I saw the proxmax part. Never mind about docker containers. Some of the same concepts apply such as bridging. This is really going to depend on how the networking is setup on it. Might just be natd. Could be vlans involved too.
The only ports Xfinity blocks are these: https://www.xfinity.com/support/articles/list-of-blocked-ports
If you can't see that the port is open on your local network if you portscan the host box with nmap with something else on your network, you've got zero chance of a port forward on your router working, so you're going to want to fix that problem first and make sure the service is actually running correctly in the container.
Caution. If you are running a gaming server on a work equipment network, that's going to get you canned. Most won't hesitate.
(edited)
0
0