I connect from my personal Windows Pro desktop to a domain-joined Windows 11 Pro work laptop. The deprecated Microsoft Store Remote Desktop app works when I enter the account as DOMAINuser; it reaches the Windows sign-in screen and shows "Other user," where I can enter my password. However, mstsc, the newer Windows app, Devolutions, mRemoteNG, and RDCMan all ask for credentials before connecting and then fail, even when I try DOMAINuser, user@domain, or .user. Network Level Authentication is already disabled. I need a reliable way to connect before formatting my personal PC, but I cannot locate the old app's installer. What should I check or configure?
2 Answers
Since NLA is already disabled, check the actual RDP and authentication errors instead of repeatedly changing the username format. Clear entries in Credential Manager under Windows Credentials, then test with the laptop’s fully qualified computer name or IP address. An administrator should also verify the Remote Desktop Services firewall rules, the user’s membership in Remote Desktop Users, and the relevant event logs on the laptop. Those checks usually reveal whether this is a network, permissions, or domain-authentication problem.
Try launching mstsc without saved credentials and specify the computer name or address first. At the Windows security prompt, use DOMAINuser rather than .user; the latter means a local account on the remote computer. user@domain can work, but only if the domain’s UPN is configured that way. If you are outside the office, connect to the company VPN before starting RDP so the client can reach the domain and authenticate.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures