Share via

Question HTML5 Webclient

Michael Fana 26 Reputation points
2020-12-07T15:54:34.743+00:00

Hello,

i have (hopefully) a simple question. I have a collection, which is accessible via Web-Access (https:/<fqdn>/rdweb/...)

No i want to test the html5 Client. I hav successfully published the client (https:/<fqdn>/rdweb/webdlient/index.html). It works internally without a problem.

Now i want to access the page via https from external ressource, but the connection will not start.

So my simple question is - do i need another port to be open additionally to https (443)??? My understanding was, that everything "happens" inside the webpage....

Thanks a lot.

Micha

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,406 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Eleven Yu (Shanghai Wicresoft Co,.Ltd.) 10,726 Reputation points Microsoft Vendor
    2020-12-08T03:33:00.467+00:00

    Hi,

    If the port 443 and 3389 has been opened, no other port need to be opened.

    If port has no problem, the issue might related to the certificate and the FQDN in the URL.

    Article “Set up the Remote Desktop web client for your users” mentioned below about certificate for webclient:

    1. The RD Web Access role is configured with a publicly trusted certificate. That means you should not use a self-signed certificate but need to obtain a certificate from a trusted public authority such as GoDaddy, GeoTrust, Digicert, Symantec, GlobalSign, Thawte, etc.
    2. Your URL uses the FQDN of the server hosting the RD Web role. https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-web-client-admin

    Also, blog “Certificate Requirements for Windows 2008 R2 and Windows 2012 Remote Desktop Services” mentioned certificate requirements as below:

    1. The certificates you deploy need to have a subject name or subject alternate name that matches the name of the server that the user is connecting to.
    2. The certificate for RDWeb needs to contain the FQDN of the URL, based on the name the users connect to. If you have users connecting externally, this needs to be an external name (needs to match what they connect to).

    https://techcommunity.microsoft.com/t5/ask-the-performance-team/certificate-requirements-for-windows-2008-r2-and-windows-2012/ba-p/375448

    Thanks,
    Eleven

    If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.

    0 comments