@Khaled- 

Did you check if pinging <name>.tplinkdns.com resolves to the IP address of your PPPoE session 41.34.68.101.

1. If it doesn't, change your VR2100 DNS servers to public DNS (e.g., Google's 8.8.8.8 and 8.8.4.4) in your network settings:

Hit Save button and check if the TP-Link DDNS name resolve to the PPPoE session IP address.

Then proceed with Remote Management access test.

2.If it does then disable:

Then proceed with Remote Management access test.

  @Khaled- 

Did you already log in with your TP-Link ID ?

In a browser type your router local IP address:

Then this login page opens:

Log in with your TP-Link ID now.

Try the Remote Management access.

Here's more on troubleshooting TP-Link DDNS.

  @Khaled- 

Actually no, the Remote Management feature opens the necessary ports automatically when it is enabled.

There's no obvious reason Remote Management won't work, if the TP-Link DDNS name has been resolved correctly to your router public IP address.

How do you test the Remote Management access - from your local network ? If that's the case try from an external network like a mobile Internet.

Is your public IP address dynamic ? Because if it's a static, you can use it directly instead of the TP-Link DDNS name.

Another approach would be to register with noip<dot>com instead and choose a name at your preference.

  @Khaled- 

Don't worry, I am using noip services 15 years already. I don't know why tplinkdns.com service didn't work for you, but after all you got what you wanted.