RemoteApp webclient launch failure

remoteUser1 101

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.

Glaucia Fernanda da Silva Diniz 1 Reputation point

2022-06-21T06:01:46.123+00:00
The error for me scren "opening remote port"

Set a problem soution for case.

Open 'RD Gateway Manager';

Expand 'Policies'

set 'Resource Authorization Policies'
3.1 RDG_AllDomainComputers - click-in 'Allowed Ports', add ports 3389;443
3.2 RDG_RDConnectionBrokers - click-in 'Allowed Ports', add ports 3389;443

if problem persist reinstall a featrue de gateway and steps again.
rds opening remote port

Accepted answer

Jenny Yan-MSFT 9,326 Reputation points

2020-10-01T09:16:12.047+00:00

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
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

9 additional answers

Dag Arne Kirkerod 1 Reputation point

2020-10-14T18:12:59.637+00:00

Same problem. But the error is not consistent. Sometimes launch works fine (RD Web Client 1.0.21.0), sometimes not. We got this error message in browser:
Oops, we couldn't connect to "Task Manager"

Same issue Chrome and Edge.

Activating RD Console Logs, the log shows:
2020-10-09T12:53:26.622Z Connection(ERR): The connection generated an internal exception with disconnect code=GatewayProtocolError(52), extended code=<null>, reason=Gateway tunnel authorization failed with error code=2147965403

The event log on the RD-GW service get this event when faulty connection happens:

Source: Microsoft-Windows-TerminalServices-Gateway
Event ID: 201
The user "xx\yy", on client computer "official.ip.adress.client", did not meet connection authorization policy requirements and was therefore not authorized to access the RD Gateway server. The authentication method used was: "NTLM" and connection protocol used: "HTTP". The following error occurred: "23003".

Regards
/Dag Arne
Please sign in to rate this answer.
Dag Arne Kirkerod 1 Reputation point

2020-10-15T03:29:10.447+00:00

Envirionment:
W2K19, 1806
SRV1: GW & WEB, outer DMZ
SRV2: CB & LIC, Internal Zone
SRV3: RD-Host, Internal Zone

The Firewall's has been opened as stated in config guides and DNS entry's are correct (no multi IP's on same fqdn objects). No clustring/redundancy in any roles. If firewall's had not been correct, the connection problem should be consistant..

Any help on this issue would be appropriated

Mr_Biscuitz 1 Reputation point

2021-11-25T16:36:35.573+00:00

Hi

It's been over a year which you have had this issue which you may of since resolved but I came to this page as i was having the same issue. The above event ID (201) you were having was the exact same error i was having although i wasn't looking at the gateway until i saw your post here so thank you.

You need to add the group to the relevant policy as per these instructions which helped me - https://kb.eventtracker.com/evtpass/evtpages/EventId_201_Microsoft-Windows-TerminalServices-Gateway_67388.asp

I was confused as it was working through the old rds web page onsite or via adding it in control panel but not using the webclient. From this I assume (possibly wrongly but it sort of makes sense to me) that the gateway isn't touched as using it via the older way as i was onsite whereas the webclient goes through the gateway hence the error.
Sign in to comment

Share via

RemoteApp webclient launch failure

rds opening remote port

9 additional answers