I am debugging trying to debug a problem with Krdc to determine if it is a plasma 6 issue. Background I have an RDP server running xrdp which works fine with Plasma 6, HOWEVER, I need to rename the server. hostnamectl hostname <NEW-NAME> Rebooted server, updated DNS and DHCP static leases for NEW-NAME. After reboot, everything works fine using NEW-NAME, except for krdc. I can ping by name name I can ssh into server using new name On Windows machines that RDP in using NEW-NAME, they get a certificate message because the name changed and after accepting they login and everything works FINE. On Linux machines that RDP in using NEW-NAME with krdc as the lcient it displays a blue screen and never displays the xvnc login prompt nor any message about the certificate issue because of the name change. The issue is not a DNS issue since everything else works using NEW-NAME and it is not an xrdp server issue because if I use xfreerdp /v:NEW-NAME from the SAME clients that fail with krdc, it works fine and they get the xvnc login prompt and then login and get the desktop. I believe that xfreerdp works because I read something which said it is using an option to either auto accept the new certificate or to ignore it certificate issues. Bottom line is that krdc does not work when the server is renamed and xfreerdp does from the same client computer to the same RDP server. I have confirmed that this is not a client side configuration or update issue because I build a new TW machine with a brand new installation and I get the same results krdc cannot handle the server rename and xfreerdp has no issue with it. I suspect that when a client using krdc attempts to connect using the NEW-NAME that the server is still using a certificate with the OLD-NAME and when krdc gets the mismatch instead of display a message asking the user to accept the certificate it just displays the blue screen and does nothing. One other point of interest is that sometimes, when the krdc client gets the blue screen I can actually hear the login sound playing. If I rename the RDP server back to OLD-NAME then all clients using krdc work again. I have tried to find documentation on what needs to change when you rename a server as well as how to find the certificate that is causing this issue but have not been successful Other things I've tried is to run update-ca-certificates and then run xrdp-keygen xrdp to regenerate the /etc/xrdp/rsakeys.ini file but that didn't resolve the issue. Any guidance on how to find the certificate that is causing the issue would be greatly appreciated -- Regards, Joe