Kerberos RDP from Linux

avatar

Hi,

I'm trying to connect to a domain with NTLMv2 disabled via Kerberos authentication on an Ubuntu 22.04

It works fine via rdesktop directly on the machine, as well as a xfreerdp with compiled kerberos Support that I have on the this system. E.g. Remmina works fine with this setup.

When trying to log on with RDM it fails. Terminal gives the following errors:

[13:46:00:919] [26213:26228] [INFO][Devolutions.Rdp.Credentials] - parsing "X*********", "X*****.X**.X**" (Mstsc) => "Username: "X*********" Domain: "X*****.X**.X**""
[13:46:00:921] [26213:26228] [WARN][com.freerdp.core.client] - Skipping, channel already loaded
[13:46:00:921] [26213:26228] [WARN][com.freerdp.core.client] - Skipping, channel already loaded
[13:46:00:921] [26213:26228] [WARN][com.freerdp.core.client] - Skipping, channel already loaded
[13:46:00:921] [26213:26228] [WARN][com.freerdp.core.client] - Skipping, channel already loaded
[13:46:00:562] [26213:26228] [WARN][com.winpr.sspi] - InitializeSecurityContextA status SEC_E_INTERNAL_ERROR [0x80090304]
[13:46:00:562] [26213:26228] [ERROR][com.freerdp.core.auth] - InitializeSecurityContext failed with SEC_E_INTERNAL_ERROR [0x80090304]
[13:46:00:562] [26213:26228] [ERROR][com.freerdp.core.transport] - NLA begin failed
[13:46:00:562] [26213:26228] [ERROR][com.freerdp.core] - transport_connect_nla:freerdp_set_last_error_ex ERRCONNECT_AUTHENTICATION_FAILED [0x00020009]


I tried different ways of entering the username and domain, but wasn't successful. I tried the different Authentication method settings, including Default and Kerberos without luck.

Is there a way of specifying the path to freerdp and passing an environmental variable? That way I could make sure it uses my working freerdp with the matching kerberos Ticket?

All Comments (2)

avatar

ok, so this doesn't really answer my question regarding how to set your own xfreerdp - but I did manage to get a successful Kerberos authentication working by setting SSPI to "Portable" and Authentication Package to Kerberos

avatar

Hi,

Glad to read you had some success with your authentication process.
Does that mean you can connect you session embedded in RDM?

To answer your other question, you can set your session as external in the general section of the entry's properties.
When launching an external RDP session, a prompt will offer you 2 choices.

  1. Normal. Will execute xfreerdp (you need the freerdp-x11 package installed) and create a settings file based on your entries properties.
  2. Custom. You have complete control on what app to launch and the command line used. You can access the entry's properties through variables like $HOST$ or $PASSWORD$


Let me know if you have further question
Regards

Jonathan Lafontaine