| Summary: | krdp disconnects immediately after connection | ||
|---|---|---|---|
| Product: | [Plasma] KRdp | Reporter: | SnDream <sndream> |
| Component: | general | Assignee: | Unassigned bugs <unassigned-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | ahiemstra, zdenek.koprivik |
| Priority: | NOR | ||
| Version First Reported In: | 6.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
SnDream
2025-11-21 14:10:53 UTC
Update: After testing, both the krdp configured in the settings and the krdpserver command can be connected via KRDC, but still cannot be connected via mstsc. I've also noticed some changes for KRDP after updating to Plasma 6.5.x in KDE neon. One thing I've noticed is that starting from 6.5.0 you need to check "Allow me to save credentials" in the MS Win11 client to successfully connect to Plasma RDP. Without this checkbox enabled I don't even get the user and password prompt (it was definitely not the case in Plasma 6.4.x). You can still input the password and uncheck "Remember me" in the dialog to avoid saving the credentials. Even with this workaround enabled, it usually takes at least 2 attempts to connect to the Plasma desktop (first attempt usually ends with error in the client), but sometimes I need more attempts or relaunch the client etc. It is a kind of roulette to get to my remote Plasma desktop, but once it successfully connects, it usualy works fine. (In reply to KOPRajs from comment #2) I tried your method, and it does work. Now I at least have a workaround to perform RDP login, rather than using the traditional VNC protocol. Thank you very much! |