Ports not opening,DMZ not helping helping either

Chn555

Reputable
Aug 27, 2015
7
0
4,510
Hello, Im having some problems forwarding ports, for tunngle and general gaming.
i have a Dlink DIR 825AC router, connected to HOTBOX(ISP modem+router) currently on bridge mode.
windows firewall off, nothing else installed.after creating rules ports are still closed.
I've tried DMZ, ports still remain closed. when connected directly to the modem they are all open and everything works.
Testing done with Simple Port Tester. using windows 10 64bit
thanks in advance.
 
in bridge mode i cant access it, should i reset it, disable nat and then bridge?
keeping in mind it works when i am connected directly to the modem
EDIT: now even when connected directly to modem i get port closed error. last time it worked, i have reset windows since then, anything beside firewall that could be blocking me?
 
Here is a simple test to see if modem is truly in bridge only mode.

Plug PC directly into modem (may have to reboot modem).

Open command prompt and run ipconfig. If the IP address is the same as when you google your IP address then it is functioning as a modem only. If it is something different (like 192.168.x.x) then it still providing NAT and DHCP.
 
You have to have the program running it for it to show the port open. Without the program wanting to use the port running, the service will not get a response back from that port thus think it is closed.

If program is on and still getting this issue then you need to add rule to local PCs software firewall (either windows or third party program like Norton or Bitdefender).
 


I've tried adding rules, turning off and event disabling process. also uninstalling my AV again for good measure.
And i've been testing it by starting tunngle and seeing if it connects, not just testing ports
 
So with PC connected directly to your modem your PC ip address (from typing ipconfig in command prompt) is the public IP from your internet provider
With the program running, and all firewalls disabled the port is still seen as closed?

I would double check the program is configured to that port because there should be absolutely nothing in your way at this point.

And I take it you have a tried a couple different port scanning sites?