https://bugs.kde.org/show_bug.cgi?id=501477
--- Comment #7 from Alban BROWAEYS <[email protected]> --- (In reply to Alban BROWAEYS from comment #6) > (In reply to Ash from comment #5) > > Okay, this is not a bug in KRDP. I tried the latest version of > > gnome-remote-desktop (that is built against the same version of FreeRDP3) > > and it gives exactly the same error. > > > > I think I'm seeing a version of this: > > https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/162 > > > > I don't have permission on the Windows laptop to check the configured group > > policies, but there must be a setting that is preventing a connection to a > > non-whitelisted RDP endpoint. > > Weirdly, it seems like Windows implements this by still sending the > > connection, but without any security context attached, so FreeRDP errors at > > this line: > > https://github.com/FreeRDP/FreeRDP/blob/ > > acf830946cb8358f03ac9bdaad61da4397fb58fc/winpr/libwinpr/sspi/NTLM/ntlm.c#L495 > > > > The next thing I can try is to borrow a different (non-organisation) Windows > > laptop from a friend and see if that can connect to KRDP. > > to me the error you point to about windows policy is a 0x0002000D transport > error not the same as yours > > but > > [16:08:59:857] [296889:302985] [INFO][com.freerdp.core.connection] - Client > Security: NLA:0 TLS:0 RDP:1 > [16:08:59:857] [296889:302985] [INFO][com.freerdp.core.connection] - Server > Security: NLA:1 TLS:0 RDP:0 > [16:08:59:857] [296889:302985] [WARN][com.freerdp.core.connection] - server > supports only NLA Security > [16:08:59:857] [296889:302985] [ERROR][com.freerdp.core.connection] - > Protocol security negotiation failure > > points at your client not supporting NLA authentification ( Client Security: > NLA:0 TLS:0 RDP:1) only RDP auth. > But your server only supportinjg NLA authentification (Server Security: > NLA:1 TLS:0 RDP:0) Sorry I missed the latter: [16:10:38:453] [296889:304164] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 [16:10:38:453] [296889:304164] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 [16:10:38:453] [296889:304164] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 where the auth schemes are synced. INVALID TOKEN point to an auth issue. Then I might have the same issue as yours with my https://discourse.gnome.org/t/can-no-longer-login-to-gnome-remote-desktop-kerberos-error/32757 request for help. I did not have issue with freerdp 2 that had no kerberos support, but it seems my Samba AD kerberos client or something related messses up gnome-remote-desktop freerdp 3 because of freerdp3 kerberos support. -- You are receiving this mail because: You are watching all bug changes.
