Forum Discussion
JamesCrk
Cirrus
CirrusAPM RDP Remote resource cannot be reached
14.1.5.2 with APM Hi, we have APM confiugred presenting native rdp to users. we have serval hundred users using this on a daily basis without issue, but we now have 3 users who cannot launch the rd...
Found out it was related to registry string: RDGClientTransport
if its not present or set to 0 (which is default) it will work. if its set to 1 or 2 it will fail with that error.
JamesCrkCirrus
CirrusYes the contents are identical to the rdp file on my machine which works
lnxgeek
MVP
MVPMy next step would be to validate if any packages are leaving the machine with Wireshark.
If that isn't the case I think it must be related to application firewalling (or what it is called on Windows 😀) which stop the traffic from going out.
- JamesCrk
Found out it was related to registry string: RDGClientTransport
if its not present or set to 0 (which is default) it will work. if its set to 1 or 2 it will fail with that error.
- lnxgeek
Fantastic! 😁
Do you have any documentation of this setting?
It sounds interessting.
- JamesCrk
Just what I found on google:
The Remote Desktop Protocol v8 introduced the HTTP & UDP transports. The values for the RDGClientTransport registry key are;
- 0 (default – HTTP) (also known at “negotiate NLA using TLS”)
- 1 RPC over HTTP (also known as “RDP Security”)
- 2 RemoteDesktopGateway (WinHTTP)