I'm affected too. I'm on Linux Mint 19.3 MATE (amd64) which is based on Ubuntu 18.04. Connecting to a Windows 10 machine and Windows Server 2019 fails. Connecting to a Ubuntu 18.04 server works, however.
freerdp2-x11 version: 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 openssh-client version: 1:7.6p1-4ubuntu0.3 openssl version: 1.1.1-1ubuntu2.1~18.04.5 kernel: 5.3.0-26-generic This is how I try to connect: Terminal 1 $ ssh -L [localport]:[server]:[port] [username]@[ssh-server] Terminal 2 $ xfreerdp /v:localhost /port:[localport] /u:[username] /network:modem /kbd:german /f Password: [22:15:20:829] [15325:15326] [ERROR][com.freerdp.core.nla] - SPNEGO failed with NTSTATUS: 0xC00000BB [22:15:20:829] [15325:15326] [ERROR][com.freerdp.core] - freerdp_set_last_error Unknown error class [0xC00000BB] [22:15:20:829] [15325:15326] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail [22:15:20:829] [15325:15326] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 [22:15:20:829] [15325:15326] [ERROR][com.freerdp.client.x11] - Freerdp connect error exit status 1 With option /log-level:TRACE $ xfreerdp /v:localhost /port:[localport] /u:[username] /network:modem /kbd:german /f /log-level:TRACE [22:16:59:351] [15346:15347] [DEBUG][com.freerdp.client.x11] - Searching for XInput pointer device [22:16:59:353] [15346:15347] [DEBUG][com.freerdp.client.x11] - Pointer device: 11 [22:16:59:361] [15346:15347] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE [22:16:59:361] [15346:15347] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE [22:16:59:361] [15346:15347] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE [22:16:59:361] [15346:15347] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: TRUE [22:16:59:362] [15346:15347] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE [22:16:59:362] [15346:15347] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE [22:16:59:362] [15346:15347] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA [22:16:59:362] [15346:15347] [DEBUG][com.freerdp.core.nego] - Attempting NLA security [22:16:59:365] [15346:15347] [DEBUG][com.freerdp.core.nego] - RequestedProtocols: 3 [22:16:59:449] [15346:15347] [DEBUG][com.freerdp.core.nego] - RDP_NEG_RSP [22:16:59:450] [15346:15347] [DEBUG][com.freerdp.core.nego] - selected_protocol: 2 [22:16:59:450] [15346:15347] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_FINAL [22:16:59:451] [15346:15347] [DEBUG][com.freerdp.core.nego] - Negotiated NLA security [22:16:59:452] [15346:15347] [DEBUG][com.freerdp.core.nego] - nego_security_connect with PROTOCOL_NLA [22:16:59:557] [15346:15347] [DEBUG][com.winpr.utils] - Could not open SAM file! Password: [22:17:04:907] [15346:15347] [DEBUG][com.winpr.sspi] - InitSecurityInterfaceExA [22:17:04:907] [15346:15347] [TRACE][com.freerdp.core.nla] - InitializeSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312] [22:17:04:907] [15346:15347] [DEBUG][com.freerdp.core.nla] - Sending Authentication Token [22:17:04:907] [15346:15347] [DEBUG][com.freerdp.core.nla] - [...] NTLMSSP......... [22:17:04:908] [15346:15347] [DEBUG][com.freerdp.core.nla] - [...] ................ [22:17:04:908] [15346:15347] [DEBUG][com.freerdp.core.nla] - [...] ........ [22:17:04:953] [15346:15347] [ERROR][com.freerdp.core.nla] - SPNEGO failed with NTSTATUS: 0xC00000BB [22:17:04:953] [15346:15347] [ERROR][com.freerdp.core] - freerdp_set_last_error Unknown error class [0xC00000BB] [22:17:04:953] [15346:15347] [ERROR][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_NLA - nla_recv_pdu() fail [22:17:04:953] [15346:15347] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 [22:17:04:954] [15346:15347] [DEBUG][com.freerdp.core.rdp] - transport_check_fds() - -1 [22:17:04:954] [15346:15347] [ERROR][com.freerdp.client.x11] - Freerdp connect error exit status 1 It was working until a few weeks ago (Windows 10 and Windows Server 2008 R2, wheras the Windows Server 2019 was not existing back then). I'm not aware of packages related to this issue being updated on the client machine (Linux Mint 19.3). I know that there has been updates on the Windows 10 machine. It could be related to a Windows update (speculative). I worked around it by adding cosmic to sources.list.d (main and universe) and apt-pinning the 4 packages freerdp2-x11, libfreerdp- client2-2, libfreerdp2-2, libwinpr2-2 to the version 2.0.0~git20180411.1.7a7b1802+dfsg1-2. I chose this version because in newer versions the libfreerdp... packages depend on libc6 >= 2.28 which would have had a too big impact (currently installed version of libc6 is 2.27-3ubuntu1). The output of the working version ist: $ xfreerdp /v:localhost /port:[localport] /u:[username] /network:modem /kbd:german /f [23:02:50:703] [21097:21098] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr Password: [23:02:54:854] [21097:21098] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRX32 [23:02:54:854] [21097:21098] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16 [23:02:54:999] [21097:21098] [INFO][com.winpr.clipboard] - initialized POSIX local file subsystem [23:02:55:474] [21097:21098] [INFO][com.freerdp.client.x11] - Logon Error Info SESSION_ID [LOGON_MSG_SESSION_CONTINUE] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847075 Title: xfreerdp fails with Windows 10 terminal server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1847075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
