I also confirmed it’s not a network issue as my Macbook (in the same VLAN) can do it just fine.
I tried the one from the Snap store, but it’s looking for wlfreerdp
.
The Flatpak version worked fine
I also confirmed it’s not a network issue as my Macbook (in the same VLAN) can do it just fine.
I tried the one from the Snap store, but it’s looking for wlfreerdp
.
The Flatpak version worked fine
Install wlfreerdp
as the popup suggests you?
Not in Neon or Ubuntu repo, unless it goes by a different package name?
Package names frequently differ across distros. Use your package manager to search for rdp
.
I did.
the only one I found is freerdp2-wayland
, and that didn’t work. That pop up is from the Snap package.
And the one from Flatpak worked. So I think it’s just missing that dependency for Wayland.
The one that came with Neon repo is either graphically glitchy or it refuses to connect.
$ krdc
KRDC: Starting RDP session
[11:39:34:798] [761599:761599] [WARN][com.freerdp.crypto] - Certificate verification failure 'self-signed certificate (18)' at stack position 0
[11:39:34:798] [761599:761599] [WARN][com.freerdp.crypto] - CN = FMT-DC01.folksvfx.int
[11:39:39:718] [761599:761599] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Connection reset by peer
[11:39:39:718] [761599:761599] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
[11:39:40:081] [761599:761599] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Connection reset by peer
[11:39:40:082] [761599:761599] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
[11:39:40:082] [761599:761599] [ERROR][com.freerdp.core] - freerdp_post_connect failed
KRDC: Unable to connect
KRDC: ERRCONNECT_CONNECT_TRANSPORT_FAILED The connection transport layer failed.
Snap issue
https://bugs.kde.org/show_bug.cgi?id=481962
Neon issue
https://bugs.kde.org/show_bug.cgi?id=481968
I’m suspecting that the KRDC issue from Neon repo is related to certificates.
This is a separate problem, but I’ve been trying to figure out what I’m missing with that for a while now since I have the root and intermediate certificates, but the system can’t seem to recognize it.
I’m able to add the same certificates in Firefox manually and it works
I was using Remmina but had same issues there after updating to Plasma 6
In my case it helped to switch from 8 bit colors to 32 bit colors… I have no idea why it helped, but it did
In KRDC it helped to force RemoteFx as acceleration
Strange, you’re right!!
How did a certificate issue fix that issue?
I was having the exact same issue and, weirdly enough, what @Loozi mentioned actually worked for me, although I didn’t explicitly select 32-bit color, but left it as “Use Best Available”.
Hi,
I did a test with plasma 6.0.1 no issue with krdc to remote a windows 10 computer, more details below :