RD Gateway Known Issues

This KB Article References:

It has been noticed that many Windows machines are configured to not use NTLMv2 security.  This results in a failure to log onto the RD Gateway without a clear error message as to why.  To fix this, you'd need to make a change to your local registry.


The security setting must be corrected on the client computer before RDP can be established.  Please set the registry entry on your computer to use NTLMv2 security (option 3 or higher).  This can also be configured through the local security policy on your computer.

LmCompatibilityLevel Registry Key Values

Path to Registry Key: MoHKLM\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibiltyLevel

ValueMeaning
0Clients use LM and NTLM authentication, but they never use NTLMv2 session security. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
1Clients use LM and NTLM authentication, and they use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
2Clients use only NTLM authentication, and they use NTLMv2 session security if the server supports it. Domain controller accepts LM, NTLM, and NTLMv2 authentication.
3Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controllers accept LM, NTLM, and NTLMv2 authentication.
4Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controller refuses LM authentication responses, but it accepts NTLM and NTLMv2.
5Clients use only NTLMv2 authentication, and they use NTLMv2 session security if the server supports it. Domain controller refuses LM and NTLM authentication responses, but it accepts NTLMv2.
This Content Last Updated:
01/24/2026

Supported By


Customer Engagement and Support

Need Help? The fastest way to get support is by submitting a request through our ticketing system.

Get Help With the RD Gateway
This KB Article References:
Estimated Read Time:
1 minutes
This Content Last Updated:
01/24/2026