TL-MR6400 DDNS and Remote Admin not working - wrong WAN IP addresses?

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

TL-MR6400 DDNS and Remote Admin not working - wrong WAN IP addresses?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TL-MR6400 DDNS and Remote Admin not working - wrong WAN IP addresses?
TL-MR6400 DDNS and Remote Admin not working - wrong WAN IP addresses?
2018-03-04 06:26:43
Model :

Hardware Version :

Firmware Version :

ISP :

I have a TL-MR6400 with an EE pay as you go sim card.

I am ultimately trying to gain remote access to a web server attached to the router using port forwarding.

I am however unable to access the router remotely either via direct IP or via DDNS.

On a PC connected to the router I am able to access the internet and the status page of the router has Connection Status: Connected.

The router status page shows an IP address "100.124.XXX.XXX" (Ive used Xs to mask actual address and ill call this one .)

Using DDNS with noip reports a different ip address "213.205.XXX.XXX" . this is the same using the router DDNS to report IP or using the noip client on a PC.

Under remote management I have setup:
- Web Management Port: 8081
- Remote Management IP Address: 255.255.255.255
- Saved

I am unable to access remote management via :8081 or :8081. I have also tried a number of other port numbers

Pinging address is unsuccessfull

Pinging address is unsuccessfull

Running a tracert from a pc connected to the router does not show up either or .

I have no idea whats happening......

Any help greatly appreciated

Firmware Version:
1.0.15 Build 170912 Rel.75663n
Hardware Version:
MR6400 v2 00000000
  0      
  0      
#1
Options
1 Reply
Re:TL-MR6400 DDNS and Remote Admin not working - wrong WAN IP addresses?
2018-03-08 13:58:30
What port had you opened for the web server? It should not be the same as the remote management port 8081? If you want to access the router's web server, then no need to set port forwarding. Just remote management is enough.
  0  
  0  
#2
Options