Home Network Community > All Threads > AXE5400 and Dyndns
< All Threads

AXE5400 and Dyndns

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

AXE5400 and Dyndns

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
AXE5400 and Dyndns
AXE5400 and Dyndns
2023-06-10 20:15:24
Model: Archer AXE75  
Hardware Version:
Firmware Version: 1.6

Hi,

 

I'm trying to setup dyndns on this router and I can't get it working for some reason.

 

I'm logged in to dyndns through the router (it says Success!)

 

IP address is correctly updated in dyndns dashboard.

 

Computer is configured to use remote desktop on port 3389 and was working fine on my old router.

 

On the new router I set a static IP for the computer and I port forwarded port 3389 (internally and externally) to the computer's static IP address.

 

When I try to remote desktop, or to access via a browser, it just times out.

 

I'm using the correct format of mydomainname . dyndns . org:3389 (without the spaces)

 

Just for giggles I tried accessing via thecomputersIPaddress:3389 to see if I would get a response and I didn't

 

Any suggestions as to what I'm doing wrong?

 

TIA for any suggestions.

 

  0      
 
  0      
 
#1
Options
9 Reply
Re:AXE5400 and Dyndns
2023-08-28 21:19:54
I have the same problem. Did you find a solution? Everything is configured but system times out. Using RDC on local network is successful. But if I try to connect from another location the connection times out. I would appreciate any help.
  0  
  0  
#2
Options
Re:AXE5400 and Dyndns
2023-08-28 23:03:59

  @MissedTheBeat Sadly, no reply. I'm really getting fed up with TPLink support. Seems I know more about their products than they do. 

 

Every time I seek assistance, they are reading from a script, ignoring the fact that I've already provided them with the answers to their questions. 

 

Then, I'm met with an endless barrage of idiotic suggestions (did you unplug the router???) before they "escalate" the issue and I get no response. 

 

Good luck. As for me, this will be my last TPLink product. I'm not going to support their subscription based feature availability. 

 

 

 

  0  
  0  
#3
Options
Re:AXE5400 and Dyndns
2023-08-28 23:51:49 - last edited 2023-08-29 12:07:48

To be able to use RDP on port 3389 there are few conditions that have to be met:

 

1. WAN IP address of the router should be the same as the one registered in the dyndns dashboard - your public IP address.

2. Port 3389 (TCP) should forwarded to the computer in your LAN (configured either with static IP or DHCP address reservation).

3. Port 3389 should be enabled in Windows firewall inbound rules:

 

350b2a45c37a49c097a1d598354a73fe

 

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".
  1  
  1  
#4
Options
Re:AXE5400 and Dyndns
2023-08-29 00:46:44 - last edited 2023-08-29 00:47:51

As stated in my original post, the WAN IP address is correct. I'm using the dyndns updater client on the server and the router has my dyn credentials. IP address is confirmed correct on dyn's web portal. Also as stated in my original post, port 3389 is port forwarded to the server's internal IP address, which is static. Server's firewall rules do not need to be reconfigured since they have been working for the past 10+ years on my last two routers. I can RDP to the server inside my network using the server's internal IP address, but I cannot connect using the dyn host name, either inside or outside my network. Again, WAN IP is confirmed to be correct on the dyndns web portal. .

  0  
  0  
#5
Options
Re:AXE5400 and Dyndns
2023-08-29 10:48:18

 @terziyski 

Thanks for the reply.

 

I checked the following:

 

1 - WAN IP address is the same as the dynamic ip address used. This has been checked using a dns lookup tool. The router has the dynamic IP setting to the service provider (NO-IP) and the status is marked as 'Success!' in the dynamic DNS page of the router settings.

2 - Port 3389 has been forwarded using the 'Port forwarding' section of 'NAT Forwarding' of the router settings page.

3 - Port 3389 is enabled. This can be proved because I can use RDC when connected on the local network.

 

In addition, I have reserved the device IP in the DHCP section of the router settings and bound it to the MAC address to ensure the local IP address does not change.

 

Any further suggestions would be welcome.

 

Many thanks

  0  
  0  
#6
Options
Re:AXE5400 and Dyndns
2023-08-29 12:30:00 - last edited 2023-08-30 19:32:00

One clarification - your router's WAN IP address should be the same as your public IP address (registered with the DDNS provider).

Your public IP address could be found by typing "what's my ip" in Google search. If these two IP addresses are different then that's causing the issue.

Here are some more details regarding port-forwarding troubleshooting - pay attention to Step 4.

Your router WAN IP address has to be with a public IP address, i.e. not within the following IP address ranges:

  • Range from 10.0.0.0 to 10.255.255.255 — a 10.0.0.0 network with a 255.0.0.0 or /8 (an 8-bit) mask
  • Range from 172.16.0.0 to 172.31.255.255 — a 172.16.0.0 network with a 255.240.0.0 or /12
  • A 192.168.0.0 to 192.168.255.255 range, which is a 192.168.0.0 network masked by 255.255.0.0 or /16
  • A special range 100.64.0.0 to 100.127.255.255 with a 255.192.0.0 or /10 network mask; this subnet is recommended according to rfc6598 for use as an address pool for CGN (Carrier-Grade NAT)
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".
  1  
  1  
#7
Options
Re:AXE5400 and Dyndns
2023-08-30 13:42:35

  @terziyski 

Thanks.

 

I can confirm my public IP address is the same as the DDNS address.

 

I confirmed by looking at the status page of the router showing the IP address and using external IP lookup tools to double check.

 

By using a DNS lookup tool, I confirmed the DDNS URL I am using also has the same IP address.

 

The DDNS page of the router confirms the DDNS service is logged into and it reports 'Success'.

 

I appreciate any other things you can suggest to try.

 

TPLINK DDNS PAGE SCREEN SHOT

 

 

  0  
  0  
#8
Options
Re:AXE5400 and Dyndns
2023-08-30 14:03:28 - last edited 2023-08-30 14:19:01

  @MissedTheBeat 

 

If you're sure that your router's WAN IP address is not within the ranges from my previous post try the following:

 

2eaf9d671aff40eea7484f486cab7a43

 

Your ISP may be blocking the 3380 TCP port for some reason, so using a different external port would exclude that possibility.

In the screenshot replace the Device IP address with your actual RDP server IP address.

Of course you have to use the DDNS name like so DDNS:55555 while trying to access RDP server from outside your LAN.

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".
  1  
  1  
#9
Options
Re:AXE5400 and Dyndns
2023-08-31 11:00:41

  @terziyski 

 

Thanks for your help.

 

It's now working! But the problem was the Microsoft RDC app on my iPad. When I tried on my Laptop it works.

 

I did use the external port idea also. I think this might be wise from a security point of view.

 

I realised from reading your posts and links that the settings are correct. So it must be something else. Hence switching away from the iPad.

 

I am very grateful and owe you a pint.

 

Cheers

  0  
  0  
#10
Options

Information

Helpful: 0

Views: 946

Replies: 9

Related Articles
AXE5400 or AXE75
730 0
Ring Chime Pro Wont Connect to AXE5400
6198 4
AXE75 (AXE5400) WAN port is orange - won't connect to Internet
1134 0
AXE5400 / AXE75 UPnP not working
1167 1
Archer AXE5400 and Gigaspire u6xw GS4227zw
373 0
AXE5400 Tri-Band firmware update
719 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.