Port forwarding doesn't work

[noisebomb44]

So since a while ago ive been unable to host servers, and can't seem to fix it by port forwarding, does anyone know what could be wrong here?

Things ive tried so far:

 

1. Declaring a local static IP, so that the ports i assign aren't used by some other device in my house instead

2. Port forwarding the port using every combination of UDP and TCP

3. Enabling DMZ (basically meaning that every port if opened on the computer i selected)

4. Disabling my firewall while doing everything above

5. Disabling my VPN service

 

After doing all of this the port is still closed, the only possible reason i can see is that my cable company is blocking the port, which ive heard some people talk about online

If anyone have a different method i could try, please tell me.

[Electronics Wizardy]

What port, what router, what ISP?

[noisebomb44]

Just now, Electronics Wizardy said:

What port, what router, what ISP?

Well, any port for that matter ( ofcourse excluding ports such as 80, etc ), the one im testing on right now is 1110 TCP. The router is a ISP supplied one, its probably nothing to go on since its not sold in stores, but its called "cbn CH7284E". My ISP is "ComHem"

[Electronics Wizardy]

1 minute ago, noisebomb44 said:

Well, any port for that matter ( ofcourse excluding ports such as 80, etc ), the one im testing on right now is 1110 TCP. The router is a ISP supplied one, its probably nothing to go on since its not sold in stores, but its called "cbn CH7284E". My ISP is "ComHem"

How are you testing this?

 

If you have a sart phone id test with that.

 

[noisebomb44]

Just now, Electronics Wizardy said:

How are you testing this?

 

If you have a sart phone id test with that.

 

Well im testing inside games, since thats what i want to port forward for. Risk of rain in particular, since it has an excellent port check, where it tells you if the port you type is open or not on the spot

[WatfordJC]

Com Hem CH7284E manual has port forwarding on pages 29 to 30. I'm making the assumption firmware updates haven't changed the Web UI.

 

• If your ISP uses CGNAT, port forwarding won't work. You can test if this is the case by going to the Firewall page in your router configuration and flipping ICMP Blocking on/off and conducting ping tests to your public IP from outside your network. If your ISP uses CGNAT then enabling/disabling ICMP Blocking will have zero effect on whether the IP is pingable.
• If the CH7284E doesn't do NAT loopback, you won't be able to test port forwarding of the public IP from within your LAN - use something like GRC's Shield's Up to test from outside your network.

After ruling out those two possibilities, the first thing I'd do is use the router's Ping Diagnostics Test (LAN) [page 39] to check the router can ping the machine (rule out a local firewall issue, connectivity issue, and IP address typo).

 

If ping works between router and machine, the next thing to do is to check netstat output on the machine. Make sure the software is really listening on the port you've told it to. If it is listening and the port is forwarded it will be shown as open by Shields Up. If it is not listening and the port is forwarded it will either be shown as closed (no firewall is dropping the packets) or stealthed (a firewall is dropping the packets).

 

The next thing to try is check the router firewall [page 33]. I have no idea what the different levels of 'IPv4 Firewall Protection' do, but depending on how you are testing if the port is open 'Port Scan Detection' might be causing an issue.

 

For port forwarding, double-check the Local IP Address is correct, that the Local and External start/end ports are the same, and that Enabled is set to On.

 

The only other thing I can see in the manual that may cause an issue is Port Filtering. I would assume Port Forwarding, DMZ, and Firewall configuration would override port filtering rules, but it might be the case that port filtering is treated as explicit blocking.

 

If the entire port range is being filtered by a single rule you might want to create multiple rules. That is, if ports 1 through 65535 are being filtered and you want to forward port 1110, replace that filtering rule with one for ports 1 through 1109 and add a second rule filtering ports 1111 through 65535.

 

 

[noisebomb44]

Thanks so much for the help! I got it working now, apparently windows firewall was working in coordination with my avast firewall or something, so when i port forwarded a program in my avast firewall, i still got "stealth", but after portforwarding in both firewalls i got it to work!