RemoteApps not working on RDWeb over internet

Question

I have a Remote Desktop deployment with Remote Desktop Brokers, and Remote Desktop Gateway. On the firewall we are exposing the RDWeb service over port 443. On the LAN, the app published open without any problem, but not over internet. Can somebody help with some ideas what I am missing?

Thank you so much.

Answer 1

Hi Gerardo

When facing issues accessing the RDWeb service over the internet, here are some ideas to troubleshoot the problem:

1. Verify firewall and NAT settings: Ensure that the firewall and network address translation (NAT) settings are properly configured to allow incoming connections on port 443 from the internet to the RDWeb server. Check if any additional rules or port forwarding is required on the firewall to allow the traffic.
2. SSL certificate: Ensure that you have a valid SSL certificate installed on the RDWeb server. The certificate should match the domain name used to access the RDWeb service over the internet. Check the certificate's expiration date, validity, and chain of trust.
3. Public DNS configuration: Confirm that the public DNS records are correctly configured to point to the external IP address of your network. Ensure that the DNS records for your domain name (e.g., rdweb.example.com) are correctly set up and resolving to the correct IP address.
4. External IP address and NAT loopback: Test accessing the RDWeb service using the external IP address from an external network. Some firewalls do not support NAT loopback, which means you may need to test the connection from outside your network to ensure it works properly.
5. RDWeb and RD Gateway settings: Double-check the configuration of RDWeb and RD Gateway to ensure they are set up correctly. Verify the bindings, authentication settings, and other configuration details. Ensure that the RDWeb service is configured to use the RD Gateway for external access.
6. Certificate trust: Make sure the client machines accessing the RDWeb service trust the SSL certificate installed on the RDWeb server. If the client machines do not trust the certificate, they may display warning messages or prevent the connection.
7. Test from a different network: Try accessing the RDWeb service from a different external network or using a mobile device's cellular network. This helps determine if the issue is specific to your current network or if it's a broader connectivity problem.
8. Check RDWeb logs: Examine the RDWeb logs on the RDWeb server to identify any error or warning messages that might provide insights into the connectivity issue. Look for any relevant entries related to incoming connections or authentication failures.

If you have gone through these steps and the issue persists, it may be helpful to consult with a network or security specialist to review your specific network configuration and provide further assistance in diagnosing the issue.