Unable to connect RDWEB after installing the RDS Server 2019

Anonymous
2024-03-05T05:54:47+00:00

Hello: I have just installed the RDS services on a brand new Windows 2019 server.

All is well but I can't connect the rdweb to publish the remote apps.

I get "This site can't be reached"

Screen shots attached in sequence

Windows for business Windows Server User experience Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Anonymous
    2024-03-05T08:40:28+00:00

    Hello RaviAulakh,

    I understand that you are experiencing an issue with the Remote Desktop Web Access.

    Here are some troubleshooting steps:

    1. Open Server Manager, navigate to Roles > Remote Desktop Services > Overview, and ensure that the "Remote Desktop Web Access" role service is installed on the appropriate server.
    2. Launch Internet Information Services (IIS) Manager, browse to Sites > Default Web Site, and look for a folder named "RDWeb". Ensure that the application pool associated with the RDWeb site is running.
    3. In IIS Manager, go to Sites > Default Web Site > RDWeb > Bindings. Make sure that the website is bound to the correct IP address, port (usually 80 for HTTP or 443 for HTTPS), and hostname (if applicable).

    If the issue persists, you can enable “Show Analytic and Debug Logs” and review the Event Viewer's Application and Services Logs for more detailed error messages to pinpoint the exact issue.

    I hope the information above is useful. If you have any question or concern, please feel free to let us know.

    Regards,

    Jacen Wang

    0 comments No comments
  2. Anonymous
    2024-11-12T09:17:44+00:00

    Hey, I would like to add that I am experiencing the same issue with my IIS on EC2 machine.

    I did what you wrote above but nothing is changed. I am going over the logs to understand what is the issue

    0 comments No comments
  3. Anonymous
    2024-11-12T13:48:37+00:00
    0 comments No comments