No-IP (DUC) Remote Desktop Connection

If you are using No-IP (DUC) for remote desktop connection to an internal server, you still need to establish port forwarding at the router even though the Firewall of the router is disabled.

This is because No-IP (DUC) will resolve the IP path up to the router's WAN IP. Therefore, the remote desktop packet will be stuck at the router if there is no port forwarding.

The port is 3389.

Don't assume No-IP (DUC) to act like SKYPE or MSN which will be able to resolve all TCP/IP paths.

The same applies to any other applications such as remote connection to MSSQL and etc.