Archer D2 - remote management fails with other DDNS
Archer D2 - remote management fails with other DDNS
Model :
Hardware Version :
Firmware Version :
ISP :
I have just bought a new Archer D2.
I have experienced the following problem: I am unable to access in remote management when I use the DDNS of my Synology.
I explain better:
I have setup the router correctly for the remote management. In my network I have a Synology NAS with its DDNS service running.
Also with my old router, I was able to login to the router just using the alias XXXXXXX.synology.me
With the new Tp-link when I try to connect from the WAN, I get the login screen, so the public IP is mapped correctly (but without the TP-LINK logo, strange).
after I insert my psw I have only a blank page.
If I use the same DDNS to access to my synology NAS, using the port forwarding configured in the TP-LINK, I am able to access to the NAS without any problem.
In addition to that, I created another DDNS using NO-IP, and configured directly into the new router.
Now using the alias xxxxxx.ddns.net I am able to enter correctly.
In addition, if I point directly to the PUBLIC IP, I can enter correctly into the router.
Summarizing, I am able to access the remote management, but only using the PUBLIC IP, or the alias from NO-IP, but I cannot access using the alias from Synology DDNS.
Anyone can help me on this issue?
Thank you for your support.
PS: I can see in Advanced->Network->Internet two WAN interfaces configured:
br_8_35_0
pppoe_8_35_1_d
is it normal? I have an ADSL line, and the configuration of the TP-LINK for the DSL has been done using the router wizard.
Hardware Version :
Firmware Version :
ISP :
I have just bought a new Archer D2.
I have experienced the following problem: I am unable to access in remote management when I use the DDNS of my Synology.
I explain better:
I have setup the router correctly for the remote management. In my network I have a Synology NAS with its DDNS service running.
Also with my old router, I was able to login to the router just using the alias XXXXXXX.synology.me
With the new Tp-link when I try to connect from the WAN, I get the login screen, so the public IP is mapped correctly (but without the TP-LINK logo, strange).

after I insert my psw I have only a blank page.

If I use the same DDNS to access to my synology NAS, using the port forwarding configured in the TP-LINK, I am able to access to the NAS without any problem.
In addition to that, I created another DDNS using NO-IP, and configured directly into the new router.
Now using the alias xxxxxx.ddns.net I am able to enter correctly.


In addition, if I point directly to the PUBLIC IP, I can enter correctly into the router.
Summarizing, I am able to access the remote management, but only using the PUBLIC IP, or the alias from NO-IP, but I cannot access using the alias from Synology DDNS.
Anyone can help me on this issue?
Thank you for your support.
PS: I can see in Advanced->Network->Internet two WAN interfaces configured:
br_8_35_0
pppoe_8_35_1_d
is it normal? I have an ADSL line, and the configuration of the TP-LINK for the DSL has been done using the router wizard.