How to configure router 'port forwarding rule' to remotely access my RDSH server in the office from home, with RX-RDP, RX420(RDP) or RX300 thin client?
Customers who deploy RDSH servers can access their user sessions remotely via the router port forwarding method. However, this approach can result in security vulnerabilities (port 3389
forwarding) and should be the last option if the customer does not have RD Gateway or VPN infrastructure. The admin should re-enforce a strong password set for accounts to help mitigate
security vulnerability.
Port forwarding maps the port on your router’s IP address (your public IP) to the port and IP address of the RDSH server you want to access. The port forwarding rule intercepts the data traffic heading to your company’s router public IP address and redirects it to the internal RDSH server IP address. This allows NComputing thin clients in a public network to connect to the RDSH server in the private network.
Your IT admin will
first setup and enable port forwarding on your organization’s router to allow
for Remote Desktop connection outside the organization’s network.
Please refer to the article below
for detailed port forwarding instructions:
There are a few good websites describing how to configure port forwarding for different routers. Here are some reference links:
https://helpdeskgeek.com/networking/configure-router-for-remote-desktop/
https://www.dynu.com/Resources/Tutorials/DynamicDNS/RemoteDesktop
https://www.wikihow.com/Set-Up-Port-Forwarding-on-a-Router
Implementation considerations using router port forwarding to access remote RDSH servers
- Easy to configure.
- Only requires RDSH server address and port.
- Works with Dynamic DNS.
- Safety depends on the quality of the firewall;
- Requires strong user passwords (may be vulnerable to brute force attack).
- User session performance may be impacted by latency.