Archer VR400 and port forwarding to port 80 - FIXED
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Archer VR400 and port forwarding to port 80 - FIXED
Model :
Hardware Version :
Firmware Version :
ISP :
So we have a big issue. We've replaced a router that connects to CCTV. Replaced with the VR400. The router is, as usual, 192.168.1.1 and CCTV is set to get DHCP so got 192.168.1.101 so we then setup a reservation which is all fine.
We then went to NAT Forwarding/Virtual Servers setup forwarding to the CCTV 192.168.1.101 on port 80 on TCP. This should work. But for some reason TP-Link decide the management console for the router is on port 80 as well. So from what I can tell, this is conflicting with the port forwarding to the CCTV.
If you then try to connect to the external IP address of the router from a different network to port 80, all you get is 403 Forbidden which I believe is coming from the TP-Link router, meaning it's not even bothering to forward to the CCTV.
Anyone else got this issue? Is it a conflict with the Management Port which you can't appear to change as whatever free port you use, the TP-Link wrongly states it conflicts with a non existent entry in the Virtual Server.
The router is on firmware Firmware Version:0.2.0 0.9.1 v0070.0 Build 170719 Rel.63031n
Hardware Version :
Firmware Version :
ISP :
So we have a big issue. We've replaced a router that connects to CCTV. Replaced with the VR400. The router is, as usual, 192.168.1.1 and CCTV is set to get DHCP so got 192.168.1.101 so we then setup a reservation which is all fine.
We then went to NAT Forwarding/Virtual Servers setup forwarding to the CCTV 192.168.1.101 on port 80 on TCP. This should work. But for some reason TP-Link decide the management console for the router is on port 80 as well. So from what I can tell, this is conflicting with the port forwarding to the CCTV.
If you then try to connect to the external IP address of the router from a different network to port 80, all you get is 403 Forbidden which I believe is coming from the TP-Link router, meaning it's not even bothering to forward to the CCTV.
Anyone else got this issue? Is it a conflict with the Management Port which you can't appear to change as whatever free port you use, the TP-Link wrongly states it conflicts with a non existent entry in the Virtual Server.
The router is on firmware Firmware Version:0.2.0 0.9.1 v0070.0 Build 170719 Rel.63031n