Upgraded from Archer A7 to Archer C5400X, new problem possibly with NAT Loopback

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

Upgraded from Archer A7 to Archer C5400X, new problem possibly with NAT Loopback

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Upgraded from Archer A7 to Archer C5400X, new problem possibly with NAT Loopback
Upgraded from Archer A7 to Archer C5400X, new problem possibly with NAT Loopback
2021-05-22 22:36:34
Model: Archer C5400X  
Hardware Version: V1
Firmware Version: 1.1.2

My home configuration includes an Archer C5400x router and a wired Engenius EWS357AP Access Point.  I use DDNS address to monitor my security cameras both locally (connected to Wireless LAN) and remotely.  In my previous configuration with an Archer A7 router and the Engenius AP, I could access the cameras without any problem no matter what I was connected to (remote, LTE, router or AP).  Since the upgrade to C5400X, I can still access the cameras remotely, on LTE and connected to router WiFi,  When connected to WiFi on the AP, the operation fails.

 

To confirm, I entered the DDNS name in the browser to see if I could reach the NVR.  As expected, remote, LTE and router WiFi works, but AP WiFi times out.  It seems that the responses are never routed back to the AP.

 

I would appreciate any suggestions that can help resolve this problem.

 

  0      
  0      
#1
Options
4 Reply
Re:Upgraded from Archer A7 to Archer C5400X, new problem possibly with NAT Loopback
2021-05-24 12:30:06

@jas00 

 

Is the NVR attached to the router or the AP?

 

Can you get to the NVR/DVR using an IP address (192.168.x.xxx)?

 

Are you using address reservation and port forwarding?

  0  
  0  
#2
Options
Re:Upgraded from Archer A7 to Archer C5400X, new problem possibly with NAT Loopback
2021-05-24 13:21:45

@jas00 

 

NVR is connected to router (wired connection).

 

Yes, I can get to the NVR using the local IP address .

 

I'm using port forwarding (Hikvision NVR):

 

HTTP port 80

RTSP port 554

Server port 8000

camera 1 port 65001

camera 2 port 65002

camera 3 port 65003

 

Not using address reservation (Hikvision IP fixed not conflicting with DHCP range).

 

to further clarify.  I use IVMS-4500 app to access cameras on android mobile.  I can create two devices, one using DDNS address (name.tplinkdns.com), and one use local IP address.  On LTE network, and connected to router WiFi, both devices can see cameras.  Connected to AP WiFi, only local IP device can access cameras.

  0  
  0  
#3
Options
Re:Upgraded from Archer A7 to Archer C5400X, new problem possibly with NAT Loopback
2021-06-06 21:43:57 - last edited 2021-06-06 21:44:56

@jas00  Unfortunately, this is one of the (many) issues with the firmware of this "premium" router from TP-Link. NAT loopback does not work on the same network (though I have had it work from LAN -> WIFI. Sometimes the router needs a reboot to make it work.) @Tony and the rest of the TP-Link team have just dropped the ball on this product. Wifi sucks also, my 2 year oldER ASUS router is better. I would return it :(

  0  
  0  
#4
Options
Re:Upgraded from Archer A7 to Archer C5400X, new problem possibly with NAT Loopback
2021-06-06 22:09:00

@makeIThappen 

 

Thanks for the response.  I'm really disappointed with the router.  I actually purchased it for it's WAN LAG capability, but that never worked.  My ISP is Comcast with 1.2Gbit service and my modem is a Motorola MB8600 that supports LAG.  I quickly gave up on that because I got no help from TP Link.

 

Later my wife complained about not being able to see our security cameras on her smartphone when she was in the main part of the house (access point WiFi connection).  I've gone round and round with TP Link support, but all they do is try to blame some other component in my network.  Never had any problem when I was using an Archer A7 router.  Upgrading to the C5400X was a mistake.

 

I did get it to work once after a reboot of the router, but haven't been able to repeat this.

 

 

 

 

  0  
  0  
#5
Options