Remote computer will not accept credentials from Remote Desktop

I have 5 computers in my home office. All Windows 10 or 11. On two of them I am able to use remote desktop to log in to a server. Three of them get their credentials rejected. I have used remote desktop for many years. One of the computers which will not log in to the server can use remote desktop to access one of the other computers in my home office. What can this be?

Of course, PRO version is expected on all machines.

On each machine that fails, open a command prompt as admin and enter:


Note that the user name can be a MS account such as an email address but the password should not be a HELLO type, such as a PIN.

OAT said:

Of course, PRO version is expected on all machines.

On each machine that fails, open a command prompt as admin and enter:

Code:

cmdkey /generic:TERMSRV/<SYSTEMTOCONNECTTO> /user:<USERNAME> /pass:<PASSWORD>

Note that the user name can be a MS account such as an email address but the password should not be a HELLO type, such as a PIN.

Click to expand...

I did that and got the message: Credential added successfully.
But I still cannot log on using Remote Desktop.
It tells me "Your credentials did not work."

I now find that on one of the machines that could connect using saved credentials, when I re-enter the credentials, using the same credentials I've always used, it gets rejected???

Atom said:

I did that and got the message: Credential added successfully.
But I still cannot log on using Remote Desktop.
It tells me "Your credentials did not work."

Click to expand...

Please double check using credential manager that the accounts, one for remote desktop and one for the system,
are the same on ALL systems, delete if and redo if necessary.
I recommend disconnecting from ALL SYSTEMS to prevent lock out. Reboot to make sure.
This is one of my systems OATPCII connecting to OATPCI:
Note: The username has been whited out.

As a last resort, use one of the 3 troublesome systems to test. On your computer delete the credentials you use to access that machine. Restart.

On the test system, disable remote desktop, restart and and enable it again. Then on your computer try to access the troublesome system again. Enable or Disable Remote Desktop in Windows 11 Tutorial

If that works for one system, do the same thing on the other two.

Atom said:

I have 5 computers in my home office. All Windows 10 or 11. On two of them I am able to use remote desktop to log in to a server. Three of them get their credentials rejected. I have used remote desktop for many years. One of the computers which will not log in to the server can use remote desktop to access one of the other computers in my home office. What can this be?

Click to expand...

Atom said:

I did that and got the message: Credential added successfully.
But I still cannot log on using Remote Desktop.
It tells me "Your credentials did not work."

Click to expand...

Please remember if you use a Microsoft Account to log into the PC, those are the credentials needed.

Also ensure all PC's have the "Allow remote connections from this computer" box ticked, as well as the box below it....



Under Search type "advanced system setting" (without quotes), click the Remote tab.

Under Start, Settings, click System, and scroll down to Remote Desktop, and make sure "Remote Desktop" is toggled on. Also "Require devices use Network Level Authentication to connect (Recommended). This needs to be done on each PC.

I've 4 PCs on my network and I can remote log into all of them without issue. Windows 11 version shown below my avatar.

And I would NOT advise to delete your credentials unless absolutely necessary (as in I know for a fact the credential are no good). Doing so will reset everything used with your Microsoft account. Unless you can't use said credentials to log anything, there's zero wrong the credentials.

I removed all credentials and disabled remote desktop and restarted.
Re-enabled remote desktop.
Same result.

Atom said:

I removed all credentials and disabled remote desktop and restarted.
Re-enabled remote desktop.
Same result.

Click to expand...

I'm sorry Atom , I am at a loss.
I am currently using 5 systems and all of them can be connected to and can connect to other systems using RDP.
Even my 3 VMs can do the same as well.

I will soon be testing the use of remote desktop for logging on to my home network computers
from outside my home network. This will tell me if it is a problem local or the server
I'm trying to access.

This may sound odd, but stick with me on this...

The system to which you are unable to logon, do you logon to those with Windows Hello (facial recognition, PIN, fingerprint, etc.)? If so, please logon off, then log back on again using your password. You only need to do this once. If no option for a password is given, go to Settings > Accounts > Sign-in options.

If a password is not set, configure one. If you see an option that says something to the effect of only allowing Windows Hello logins, turn that off. My apologies, due to the way my system is setup I don't see that screen so I cannot give you the exact wording or provide a screenshot.

See if any of that helps.

Atom said:

I have 5 computers in my home office. All Windows 10 or 11. On two of them I am able to use remote desktop to log in to a server. Three of them get their credentials rejected. I have used remote desktop for many years. One of the computers which will not log in to the server can use remote desktop to access one of the other computers in my home office. What can this be?

Click to expand...

Hi,
Might try anydesk

Or the OP could learn to us the apps already included in Windows, which actually do work... when configured correctly.

Yeah I was confused by those ms apps that don't work lol

I've observed that authentication issues with the Local Security Authority (LSA) can sometimes occur when using a Microsoft Account (MSA) for remote access in both Remote Desktop Connection (%windir%\system32\mstsc.exe) or Remote Desktop (RDP app: C:\Program Files\Remote Desktop\msrdcw.exe). In such cases, setting up a local (admin) account on the target machine then using its account name and password to login does work most of the time. Give it a shot, if this fits your situation.
HTH,
--Ed--

ThrashZone said:

Yeah I was confused by those ms apps that don't work lol

Click to expand...

Funny, that I'm able to get them working for me. And networking isn't even my strength