Comment

I recently used the old Windows RDP client they refer to. I tried to connect to a Windows VM and it didn’t work. Had to pull out some old log utility tool and filter a while to recognize the server didn’t use a valid TLS certificate (lives inside a VPN) and the handshake failed. Tried disabling cert validation (although I’m not sure if that one obfuscated option did exactly that), still no luck.

I then tried KRDP in KDE. It asked me if I’m sure I wanted to connect since the cert is self signed. I accepted and got in. Easy as that.

source

Sort:hotnew top

KyuubiNoKitsune@lemmy.blahaj.zone ⁨1⁩ ⁨day⁩ ago
Weird, I mean, the only place I’ve used any kind of software that wasn’t just mstsc.exe (the OG RDP) is on my phone, and no matter how many servers I’ve connected to, with self signed certs, I’ve always been able to connect. Unless you’re connecting from a client without NLA, maybe it was that…

superops.com/…/what-is-network-level-authenticati…

source
- passepartout@feddit.org ⁨1⁩ ⁨day⁩ ago
  mstsc.exe was exactly the one I used. I vaguely remember that I had used that successfully some years ago (in a much bigger environment with proper certs) and it worked.
  
  Regarding NLA: I believe that I would have to disable that on purpose no? It was on a very vanilla Windows 11 install. I just looked and regarding any other settings than the ones listed in mstsc.exe, I get told that Windows 11 Home edition doesn’t support RDP lol.
  
  source
  - KyuubiNoKitsune@lemmy.blahaj.zone ⁨1⁩ ⁨day⁩ ago
    Yeah, you would, but it would only matter if you were connecting from an unsupported client.
    
    But when you said Win 11, my eyes glazed over, lol, don’t touch that piece of shit with a barge pole.
    
    source