Port forwarding not working in confirmed environment

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Port forwarding not working in confirmed environment

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Port forwarding not working in confirmed environment
Port forwarding not working in confirmed environment
2022-11-08 17:04:03
Tags: #Port Forwarding #https
Model: TD-W9970  
Hardware Version: V4
Firmware Version: TD-W9970(EU)_V4_1.3.0 Build 220616

Problem: I have setup W9970 for port forwarding, trying all of the different approaches, but it simply does not work forwarding port 443.

 

  • UPnP
  • Virtual Server
  • Port Triggering

 

In these instances, I can ping the IP and get results but the port will not forward to allow any data to be transferred over https.

 

I have read many other issues and this seems to be a problem with the firmware, I have tried all three versions (220616, 210220, 191204) available for W9970 V4.

 

Please let me know how we can resolve the problem with the firmware.

 

Background

I use port forwarding so that I can run a reverse proxy on port 443 to allow a single URL to map to my Synology NAS, with sub-domains for each service I run.

 

My existing environment and setup has been confirmed working:

 

  1. Modem: BT Openreach Huawei EchoLife HG612 3B
  2. Router: Tenda MW6 mesh network (PPoE)
  3. NAS: Synology

 

But I wanted to replace the modem part for better control, custom DNS, single NAT;

 

  1. Modem: TP-Link W9970 V4
  2. Router: Tenda MW6 mesh network (bridge)
  3. NAS: Synology

 

Meanwhile

So for now I am back to my original setup without the TP-Link device.

  0      
  0      
#1
Options
1 Reply
Re:Port forwarding not working in confirmed environment
2022-11-08 22:32:24

  @gingerbeardman 

 

In general you should be on the latest FW release (220616).

Try the following - disable UPnP, reboot the modem and then configure Virtual Server on port 443 for the corresponding LAN IP address - Port Triggering should be disabled.

Make sure that Remote Management via HTTPS is disabled:

 

If this was helpful click once on the arrow pointing upward. If this solves your issue, click once the star to mark it as a "Recommended Solution".
  0  
  0  
#2
Options