Background: I trying to do a RDP login to a domain client (Win10) (client A) with a second client (Win10) (client B) while both a connected on a network without connection to the domain controller. But it fails without access to the domain controller, while other login methods work, see the following cases for details:
- logging into client A from client B via RDP with the domain account (without DC connection) fails
- logging into client A from client B via RDP with the domain account (with DC connection through a VPN on client A) works fine
- logging into client A locally/directly with the domain account (no RDP) works fine (without connection to the DC, using cached user account / domain credentials on client A)
- logging into client A from client B via RDP with a local user account works fine (without connection to the DC)
- logging into client A from client B via remote terminal works fine (without connection to the DC using cached user account/domain credentials on client A)
Eventviewer shows me the following entry in the security Windows log:
ID: 4625
Failure Reason: Unknown Username or bad Password
Question: Apparently there is a verification needed by the domain controller, which causes the problem. Is it possible to get RDP to use the credentials locally stored on client A (basically the same way I can logon in case 3 directly)?
Goal: In essence, I want to be able to login via RDP the same way I can login locally. I need to remotely continue the user session I started locally (in case no VPN could be established, if I locally logged on with cached credentials, the RDP needs to login with cashed credentials as well). Unfortunately, a third-party screen sharing application is not an option.
So far I haven't found any solution on the web, mostly because the search results were cluttered with other use cases (e.g. trying to RDP into the domain controller, etc.).