Port forwarding problem - static webserver not accessible
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Port forwarding problem - static webserver not accessible
Model : Archer C9
Hardware Version : V1
Firmware Version : latest
I made home static webserver and forward port 80. Everything works some time but yesterday I've check and server was not accessible from outside (I have remote access to some computers outside my home location). I re-edit port forwarding rule few times, check everything and still my webserver was only working locally. Then I've trying to put my computer in DMZ and then it starts working! So I disabled DMZ and edit port forward for 2 ports - 80-81. And it works! Revert to port 80 only and stops working. Rule was last on list. I've check my firewall log etc. - only port 80 was using, but router requires two ports to be open. After many tries and even ask for testing couple of people, I decided to delete rule and re-enter the same rule again. And now (rule is now first in list) everything works on port 80 only. Strange. Is it some kind of firmware bug?
I hope someone check this.
Hardware Version : V1
Firmware Version : latest
I made home static webserver and forward port 80. Everything works some time but yesterday I've check and server was not accessible from outside (I have remote access to some computers outside my home location). I re-edit port forwarding rule few times, check everything and still my webserver was only working locally. Then I've trying to put my computer in DMZ and then it starts working! So I disabled DMZ and edit port forward for 2 ports - 80-81. And it works! Revert to port 80 only and stops working. Rule was last on list. I've check my firewall log etc. - only port 80 was using, but router requires two ports to be open. After many tries and even ask for testing couple of people, I decided to delete rule and re-enter the same rule again. And now (rule is now first in list) everything works on port 80 only. Strange. Is it some kind of firmware bug?
I hope someone check this.
