RemoteApp webclient launch failure

Question

hello,
I followed the instruction below to set up the remote web client access for wordpad.

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-web-client

then, I am able to login http://hostname.com/RDWeb/webclient/,
when I clicked the published App 'wordpad',
it prompts to ask to Allow the remote computer to access
Clipboard Printer, I clicked Allow button, then I got the following error:

Oops, we couldn't connect to "WordPad"
The connection to the remote PC was lost. This might be because of a network connection problem. If this keeps happening, ask your admin or tech support for help.

There is no network issue, any suggestions?
thanks so much in advance.

Answer 1

Hi,
It is glad to hear that Chrome browser is working now. To figure out the specific error with Firefox, it seemed more traces and logs are needed, for which you are suggested to contact Microsoft Customer Support and Services for the in-depth investigation.

You may find phone number for your region accordingly from the link below:
Global Customer Service phone numbers
https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers
Thanks,
Jenny

Answer 2

@Jenny Yan-MSFT

I followed the steps below to create a new certificate which is untrusted certificate.
I am not sure if it could be the cause, do you know how to create a trusted certificate?

Follow these steps if there is no certificate bound to the RD Broker server
Open Server Manager > Remote Desktop Services.

In Deployment Overview section, select the Tasks dropdown menu.

Select Edit Deployment Properties, a new window titled Deployment Properties will open.

In the Deployment Properties window, select Certificates in the left menu.

In the list of Certificate Levels, select RD Connection Broker - Enable Single Sign On. You have two options: (1) create a new certificate or (2) an existing certificate.

Answer 3

Hi,
Besides of trusted by client PC (or destination computer), please also verify that the correct certificate is selected in the Default Web Site bindings. Open IIS Manager, select Default Web Site in the left pane, click Bindings in the Actions pane, and then edit the binding for https.
The certificate you select needs to have a name that matches what users will enter into Internet Explorer.

Moreover, manually add this certificate to Trusted root certification authorities of client PC and test again. (Check point 16 in below link)
https://social.technet.microsoft.com/Forums/lync/en-US/029f3176-26fe-4ac9-8e71-825064434541/forum-faq-how-to-setup-selfsigned-certificate-for-rds?forum=winserverTS

Thanks,
Jenny

Answer 4

@Jenny Yan-MSFT
thanks so much for your help. I have done all required. the certificate is still untrusted.
I checked the link you provided. it also shows untrusted. so I think it is ok for testing using the untrusted certificate as long as they are accepted in the “Trusted Root certification Authorities”. I have done all steps including point 16. still I got the same error message:

2020-09-29T15:27:28.588Z WebSocketTransport(NORM): WebSocket closed, url=wss://mycompany.COM:3392/rdp, wasClean=false, code=1015, reason=""
2020-09-29T15:27:28.591Z Connection(ERR): The connection generated an internal exception with disconnect code=ConnectionBroken(8), extended code=<null>, reason=WebSocket closed with code: 1015 reason:

the error message doens't say certificate, the firewall is turned off in the windows virtual machine, I am not sure if it will related to with microsoft azure network settings causing the issue?

Answer 5

@Jenny Yan-MSFT it looks that it works fine for chrome now, the above problem is related to the firefox. I just tested in both windows and macosx firefox and chrome browser, chrome works in both windows and macosx, but firefox failed in both windows and macosx with error code=1015 as shown above. any suggestions? thanks