A summary of my latest investigation. I am able to reproduce this bug with Windows 24h2, but in a way that points to mstsc.exe being the culprit and with a quite acceptable workaround:
From an initially working setup, confirmed with a working mstsc.exe: * flushed the certs while keeping mstsc.exe open ``` sudo rm -r ~gnome-remote-desktop/.local/share/gnome-remote-desktop/ ``` * Restart g-r-d * On the GUY, open GNOME settings, the Remote Login panel, enable again, re-enter credentials, see that some new certificates were generated * Now mstsc.exe complains about the certificates * Exit and relaunch mstsc.exe --> Then it's fine. I'm still a bit confused, because with 24h2 I can only connect with .\<username> whereas 25h2 allows me to connect without the .\. Same installation process, Windows 11 pro, running mstsc.exe against the same RDP server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2137626 Title: Windows clients struggle to connect out-of-the-box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2137626/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
