Forum Discussion
APM RDP Remote resource cannot be reached
- Apr 27, 2023
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.
My 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.
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.
- lnxgeekApr 28, 2023MVP
Fantastic! 😁
Do you have any documentation of this setting?
It sounds interessting.
- JamesCrkApr 28, 2023Cirrus
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)
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com