Devolutions ForumDevolutions Forum

got security negotiation failed (0x0002000C) when RDP via RD Gateway

got security negotiation failed (0x0002000C) when RDP via RD Gateway

avatar
pirate585

Hi there,

I am connecting to a Windows server via RD gateway, but got security negotiation failed (0x0002000C) error. May I know how to troubleshoot the error? I do additional test and here are the results

  1. tried another RD gateway and it works fine
  2. tried Windows App in apple store (https://apps.apple.com/tw/app/windows-app/id1295203466?mt=12) to connect to the problematic RD Gateway and it works fine, too


RDM Mac version: 2026.2.2.1
MacOS version: 26.5

Regards,
Eric

All Comments (3)

avatar
Richard Markiewicz

Hi Eric

Sorry for the trouble.

In the first case, to see if it unblocks you; in the RDP session that's using the Gateway try going to Authentication and changing the SSPI Module setting to "System". Does it help?

Otherwise, please send me a session log. Please follow the steps precisely as they have changed in 2026.2:

  1. Close RDM completely
  2. Open RDM
  3. Before doing anything else, go to Help > Session Logs and Enable session logs
  4. Try the connection via the problematic Gateway, it will fail
  5. Locate the corresponding log back in the Help > Session Logs window and send it to me by PM (you may need to zip the file to attach it to the message)
  6. I will take a look at a high priority


Even if changing the setting I mentioned originally helps, the session log (with the default / bad value) will still be really helpful so we can check the issue and prevent it happening in future.

Please let me know if something isn't clear, and thank you for your patience

Kind regards,

Richard Markievicz

avatar
pirate585

Hi Richard,

Appreciate the prompt response. Unfortunately, I am unable to reproduce the error on next day. There is no change on RDM and the problematic RD gateway, but no error on next day. I observe the case for a few days and all are good so far. I guess we can close this issue until it happens again.

Regards,
Eric

avatar
Richard Markiewicz

Hello

Is it possible this was just a transient network error, and you got (un)lucky that Windows App worked?

The way the RDP protocol works; the client first sends a security negotiation message telling the server what types of security it supports. The server is supposed to answer with a corresponding message, and then security negotiation can proceed. If that first reply was not received from the server (maybe because the network had a transient issue in an unexpected way), that would lead to this error.

Anyway - since the issue has not come back, I suppose things are fine. But if it does reoccur please follow the steps in my post above and let me know, and we will take a look straight away.

Thanks and kind regards,

Richard Markievicz