[KRdp] [Bug 499144] Remote Desktop Connection - Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.

[Pedro Albuquerque Santos]

https://bugs.kde.org/show_bug.cgi?id=499144

--- Comment #7 from Pedro Albuquerque Santos <petersaints at gmail.com> ---
(In reply to Chris from comment #6)
> I have this issue as well, on fully updated Fedora 42 install. Connecting
> from a Windows 11 (23H2) machine i don't have admin rights on, so no option
> for other RDP clients. I was hoping to access my Fedora laptop from the
> Windows 11 machine, but can't with the Microsoft RDP client (mstsc). 
> 
> Connecting from a Windows 10 (1809) machine with "mstsc" works just fine.
> Would be really great to have the Windows 11 mstsc working.
> 
> mstsc error code: 0xd06
> 
> Operating System: Fedora Linux 42
> KDE Plasma Version: 6.4.4
> KDE Frameworks Version: 6.17.0
> Qt Version: 6.9.1
> Kernel Version: 6.15.10-200.fc42.x86_64 (64-bit)
> 
> This seems to be the relevant log section:
> 
> [21:11:02:549] [23043:000064c2] [ERROR][com.freerdp.core.transport] -
> [transport_read_layer]: BIO_read returned a system error 104: Connection
> reset by peer
> [21:11:02:549] [23043:000064c2] [ERROR][com.freerdp.core.peer] -
> [transport_read_layer]: ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
> [21:11:02:549] [23043:000064c2] [ERROR][com.freerdp.core.nla] -
> [nla_server_recv_stream]: nla_recv() error: -1
> [21:11:02:549] [23043:000064c2] [ERROR][com.freerdp.core.transport] -
> [transport_accept_nla]: client authentication failure
> [21:11:02:549] [23043:000064c2] [ERROR][com.freerdp.api] -
> [peer_recv_callback_internal]: CONNECTION_STATE_NEGO -
> rdp_server_accept_nego() fail
> [21:11:02:549] [23043:000064c2] [ERROR][com.freerdp.core.transport] -
> [transport_check_fds]: transport_check_fds: transport->ReceiveCallback() -
> STATE_RUN_FAILED [-1]
> [21:11:02:550] [23043:00005a03] [WARN][com.freerdp.core.rdp] -
> [rdp_send_deactivate_all][0x557f084fdca0]: rdpMcs::userId == 0, skip sending
> PDU_TYPE_DEACTIVATE_ALL
> [21:11:02:550] [23043:00005a03] [ERROR][com.freerdp.core.transport] -
> [transport_default_write]: BIO_should_retry returned a system error 32:
> Broken pipe
> [21:11:12:624] [23043:000064da] [WARN][com.freerdp.api] -
> [peer_unexpected_client_message]: Unexpected client message in state
> CONNECTION_STATE_FINALIZATION_FONT_LIST, missing flag
> FINALIZE_CS_FONT_LIST_PDU [0x00000100]
> org.kde.krdp: New client connected:  Windows platform Windows NT
> kpipewire_record_logging: Hardware encoding is not supported on this device.
> [libx264 @ 0x7f7dc4479d80] -qscale is ignored, -crf is recommended.
> [libx264 @ 0x7f7dc4479d80] using cpu capabilities: MMX2 SSE2Fast SSSE3
> SSE4.2 AVX FMA3 BMI2 AVX2
> [libx264 @ 0x7f7dc4479d80] profile Constrained Baseline, level 6.1, 4:2:0,
> 8-bit
> kpipewire_dmabuf_logging: eglChooseConfig returned this many configs: 1
> [21:11:13:215] [23043:000064da] [ERROR][com.freerdp.core.transport] -
> [transport_default_write]: BIO_should_retry returned a system error 104:
> Connection reset by peer
> [21:11:13:215] [23043:000064da] [ERROR][com.freerdp.core.peer] -
> [transport_default_write]: ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
> [21:11:13:230] [23043:00005a03] [ERROR][com.freerdp.core.transport] -
> [transport_default_write]: BIO_should_retry returned an error:
> error:0A00010F:SSL routines::bad length
> [libx264 @ 0x7f7dc4479d80] frame I:1     Avg QP:20.00  size:426534
> [libx264 @ 0x7f7dc4479d80] frame P:21    Avg QP:20.52  size:  7931
> [libx264 @ 0x7f7dc4479d80] mb I  I16..4: 100.0%  0.0%  0.0%
> [libx264 @ 0x7f7dc4479d80] mb P  I16..4:  0.3%  0.0%  0.0%  P16..4:  7.1% 
> 0.0%  0.0%  0.0%  0.0%    skip:92.6%
> [libx264 @ 0x7f7dc4479d80] coded y,uvDC,uvAC intra: 43.0% 43.2% 40.8% inter:
> 2.1% 5.5% 1.8%
> [libx264 @ 0x7f7dc4479d80] i16 v,h,dc,p: 61% 30%  8%  1%
> [libx264 @ 0x7f7dc4479d80] i8c dc,h,v,p: 63% 19% 16%  2%
> [libx264 @ 0x7f7dc4479d80] kb/s:215665.44

Interesting. I didn't realize this was a Windows 11 specific issue. I thought
it was broken all across the board. Is there any way to configure the Windows
11 client to behave like Windows 10? What about alternative clients for RDP
that work on Windows? I only ever used the official one on Windows.

Probably, even if one of these workarounds work they might not work
specifically for you if they require admin rights. But it would be interesting
to know if it is possible anyway.

-- 
You are receiving this mail because:
You are the assignee for the bug.