47

Description of the problem: I am not able to connect through Remote Desktop Connection to access Computer A from Computer B. More specifically, when I am on Computer B, I am not able to access Computer A through Remote Desktop Connection. I was asked to provide username and password, but I kept getting told by a "Windows Security" window that said: "Your credentials did not work."

enter image description here

Observation 1: I was able to access Computer B from Computer A. (The other way around.)

Observation 2: The only difference as I can tell, is that: I used a Microsoft Account to log-in (locally and natively) on Computer B, and used a username alone to log-in on Computer A. The usernames on the two computers (locally speaking) are:

Both computers are running Windows 10 Pro.

Observation 3: I have made sure that the there is no firewall between the two computers. (They are connected through a Ethernet switch in my home network, connecting to the outside world through the home router.)

Question: what has been going wrong? Do I have to assign and use the same Microsoft Account on Computer A? I have made sure that the password has been correct all the times, but the problem is persistent: I cannot connect from Computer B to Computer A, yet I can connect from Computer A to Computer B.

PS: I has also asked the same question in the TechNet forum, yet I am not counting on it quite a lot. Ref url.

Additional Information

The address for Computer A and B

As I only have dynamic IP on both machines, I used No-IP's service. Thus, for the two computers, for example: * Address for Computer A: computer-A.ddns.net * Address for Computer B: computer-B.ddns.net

Additional Experiments

Shutting down Computer B

When I shut down Computer B, using the address computer-B.ddns.net to connect still gets me the same error message (as in the screenshot above).

Getting a different IP for Computer B

Per the initial experiment, two computers are hosted in the same home network. Thus, the public IP for the two machines should be the same. To get Computer B a different IP, I disconnect the machine from the home network and used the Personal Hotspot on my phone. This time, I get a new error message:

enter image description here

Improve this question
6
  • 2
    You need to specifcy the account on Comtpuer A. Use "DESKTOP-XXX/username" as the username, and the password associated with that account, as the credentials to use when connecting. Set those in your RDP client/connectoid.
    – Ƭᴇcʜιᴇ007
    Commented Jun 24, 2017 at 17:28
  • @Ƭᴇcʜιᴇ007: I provided the credentials on the local Computer A to no avail. Could you clarify where does such error message (the screenshot) is coming from? Should it be the remote machine (Computer B) or the local machine (Computer A)? Note, I had the error when trying to connect from Computer A to Computer B, and there is no such user "DESKTOP-XXX/username" on Computer B.
    – llinfeng
    Commented Jun 24, 2017 at 17:36
  • 4
    @llinfeng the slash is the other way around: PC-NAME\username. Also the username is NOT the full email address. And it will only work if that user is set as local administrator on that computer or was added to the Remote Desktop users group (aka, has permissions) if the user never logged in on that machine before, it will not work by default.
    – LPChip
    Commented Jun 24, 2017 at 17:53
  • 1
    Windows 11 is a buggy mess - just dealt with this. Use a Local Account instead.
    – araisbec
    Commented Jan 30, 2023 at 22:09
  • @araisbec One side note: when setting up the local account using Win 11, it helps to keep the account simple, where no biometric info should be provided during the initial set-up process. (I learned this in a hard way, where I cannot register my index finger with my local account because it was used during the initial setup process with the same local account. And, I cannot find a way to delete such record. Ended up reinstalling Windows, lol).
    – llinfeng
    Commented Jan 31, 2023 at 0:03

13 Answers 13

Reset to default
48

I had the same with a couple machines linked to MicrosoftAccount\user from installation, remembered my previous installs started with a local account and were later linked to my Microsoft account and that worked fine.

Decided to change my Account so to sign in with a local account, tested RDP and that worked fine, decided to "re-link" my Microsoft account... tested again and it was still working without issues. Not sure exactly what causes the issue but it seems that creating a local account fixes the behavior, likely reg keys or gpedit settings not correctly configured with the Microsoft account.

Further to the above, I believe (from later found articles) that if the user signs in with the Microsoft's account password at least once rather than the PIN the issue may also be fixed. (Have confirmed this as the best fix)

https://community.spiceworks.com/topic/2047664-remote-desktop-fails-after-changed-to-microsoft-account

@TerenceGolla, hope you don't mind me quoting you below;

"For a clean install of Windows 11 which by default sets up Windows Hello go to Settings->Accounts->Sign-in options and turn off "For improved security, only allow Windows Hello sign-in for Microsoft accounts on this device (Recommended)". This will allow you to sign-in with your password after which RDC will work. It also appears that once you use your password you can turn the option back on."

Improve this answer
8
  • 1
    I would totally agree with your observation! I now start all my new Windows OS with a local account, then sign-in through my Microsoft account for OneDrive and Windows Store. It has been consistent that local-account first is the best way to go ==> name the local account's "Firstname" as the desired username and one can "reproduce" identical user-directories across different Windows machines.
    – llinfeng
    Commented Apr 10, 2019 at 21:14
  • One more reason to use local accounts rather than Microsoft accounts: DUO authorization can only be established for Microsoft accounts for Windows OS Build < 1709.
    – llinfeng
    Commented Apr 23, 2019 at 17:55
  • 8
    "if the user signs in with the MS account password at least once": this is what fixed it for me. I had gone local/MS a few times, nothing worked once I switched to MS account. I was using Hello all the way (face, fingerprint, PIN), but the moment I did a password sign in once, it all started to work. Thanks!
    – kzu
    Commented Jul 22, 2019 at 3:56
  • 6
    Your final observation worked for me - you have to log in one time with the full password on the remote computer (i.e. in person, NOT using remote desktop).
    – Tim Long
    Commented Dec 13, 2021 at 21:00
  • 3
    For a clean install of Windows 11 which by default sets up Windows Hello go to Settings->Accounts->Sign-in options and turn off "For improved security, only allow Windows Hello sign-in for Microsoft accounts on this device (Recommended)". This will allow you to sign-in with your password after which RDC will work. It also appears that once you use your password you can turn the option back on.
    – Terence Golla
    Commented Jan 17, 2022 at 6:48
44

On my remote machine I have two accounts: I have a local administrator account and I have the MicrosoftAccount as a standard user.

To re-sync the password: logon with the local administrator account, I open the command prompt on the pc I wanted to be connected and type:

runas /u:MicrosoftAccount\[my account] cmd.exe

or

runas /u:[my account]@outlook.com cmd.exe

replacing [my account] with the actual account name of the Microsoft Account

If you recently changed your password, try with the old one, if it hasn't been synced, it'll work.

This will force the machine to re-sync the password so when you get prompted you can type the most recent password. As from that point on, RDP will recognise your new password.

I also tried the above commands while being logged on as the standard user. It looks like you can do the "runas" command for the current user, so you might not even need to use another account.

Hopefully above procedure contains enough clues so that someone can figure out what is happening and come up with a real solution

Improve this answer
2
  • 7
    This fixed the issue for me, and seems to be the easiest fix here. Thanks!
    – Jon Onstott
    Commented Oct 14, 2021 at 4:05
  • 1
    Thank you. The top command (i.e., runas …) worked wonderfully for me. I ran it on my Windows 11 machine, and I was afterwards able to successfully remote in from my Win 10 machine.
    – Sampson
    Commented Mar 9 at 18:57
14

For me it worked by logging in to my Microsoft Account on the target machine with the Password (not PIN) of the Microsoft Account once.

After that, I can RDP into the machine by using the credentials of the Microsoft Account without errors.

Improve this answer
2
  • 1
    The accepted answer describes this approach as well. No need for an additional answer.
    – dirdi
    Commented Oct 11, 2019 at 12:27
  • 1
    The accepted answer also suggests re-linking the Microsoft account and that "it seems that creating a local account fixes the behavior." The only step needed is signing in once with the password, as stated here.
    – Stephen Klancher
    Commented Aug 6, 2021 at 18:00
2

I think, at least in my case, the problem was a lack of synchronization between the password on the machine and the password of the Microsoft account.

The way I think I resolved this was as follows:

  1. Change my Microsoft Account password through the Win10 interface (under the "Users" control panel)
  2. Log out.
  3. Log in using the password (not using a PIN or face unlock)

Step 3 seemed to be key.

This resolved password problems both with remote desktop and with the task scheduler.

Improve this answer
1

I had a similar problem signing in using the latest OSX (Mac) client. In my case, there appears to be a bug in the client if you have a password with a % character. Once I changed my password to remove this character, I had no problems logging in with username set to the result of "whoami" run in a command prompt window.

Incredibly frustrating that Microsoft can't properly encode characters.

Improve this answer
1
  • Ditto here, for a @, thank you for sharing! Microsoft...
    – SΛLVΘ
    Commented May 25, 2023 at 11:38
1

In my case the problem was that I went passwordless using Authenticator app, and I never logged in to my remote machine with my Microsoft Account using password.

So, the fix for me was:

  • Remove PIN
  • Login using password
  • Set the PIN back again

Then RDP connection using Microsoft Account worked.

The remote machine never got the password hash or whatever it happens behind the curtains

Improve this answer
1

I ran into this problem recently, and confirmed that the answer is in fact the requirement of logging into your machine with the password. If you configure a Windows 10/11 system with a Microsoft account using the login prompts, Windows Hello kicks in immediately and makes you log in with a pin.

Since a pin login never hashes the password used to authenticate the user, when you attempt to connect using RDP, that authentication token seemingly goes nowhere and authenticates against nothing -- this is regardless of whether you've put in the username as the email address of the Microsoft account, or the username of the local account. Odd indeed, but it at least makes sense!

Improve this answer
1

After reading the post by @AdamZaloum, I turned off "Require Windows Hello sign-in for Microsoft accounts", in the Sign-in option Settings page.

That fixed it for me, after everything else I tried didn't.

Screenshot from Windows 10 Pro:

Screenshot of Windows 10 settings

(Microsoft doesn't allow passwords in Windows Hello!? They're up in the night if they really think a PIN is more secure than a 20 character password!)

Improve this answer
0

I am no expert, but these are my findings: I can only RDP on my Windows 10 PRO machines. All of my Windows Home or Premium will not work. MS does not allow it on those OS's. My MAC PRO however, with the older Windows for MAC RDP loaded, will work perfectly.

Improve this answer
1
  • If you lower the security settings it will work on home and premium too There's this checkbox: Allow only on computers running Remote Desktop with Network Level Authentication (recommended), which is checked by default. Uncheck that, and home and premium users can connect too.
    – LPChip
    Commented Jun 24, 2017 at 18:43
0

I solved it by telling Windows in the settings that I want to login via a local user and not by the Microsoft account.

I created a new local user with a new password. (new local account means in this way that the new user stays the same, just as a local one)

Login via RDP than works with: Username: PC-NAME\UserName Password: new local user password

I am German user so I try to translate the write words.

Changing to local user works in settings under Account/Infos "...login via a local account"

Hope this helps. I don't see any reason for using the Microsoft Account for login instead of a local account.

Improve this answer
0

In RE to kodybrown and to help those who need an answer to this, follow these steps on the PC you wish to remotely connect to that has a Microsoft account attached and Windows Hello active. I will also note that this method only works on the Professional version of Windows as the Home version doesn't have access to the Local Users and Groups tool.

  1. Press Win+R to open the RUN dialogue.
  2. Type lusrmgr.msc and press Enter
  3. Navigate in the left pane to Users then double-click the user account you wish to use for remote access. This should open a dialogue called <user> properties.
  4. In that dialogue, ensure that User must change password at next logon is unchecked and that Password never expires is checked.
  5. Now go into the Member of tab in the user properties dialogue and add the group Remote Desktop Users to that list.
  6. Click Apply at the bottom and close out this dialogue and the Local Users and Groups window.
  7. If you haven't already enabled remote in settings, navigate to Settings → System → Remote Desktop and toggle it on. Click Confirm and under Remote Desktop users, add the user account you modified in Local Users and Groups.
  8. You're now all set to use Microsoft's Remote Desktop tool or similar.

With these set, you can use your Windows Hello PIN physically on the PC and your Microsoft account password on the Remote Desktop app from another PC or your mobile device! Any prompts you get for admin during the Remote Desktop connection should ask for the Windows Hello PIN, not the password. Good luck and hope this solves your issue!

Improve this answer
0

Simply

  1. Lock you PC
  2. Press "I forget my PIN"
  3. Login with password with or without reset pin
  4. Done
Improve this answer
1
0

need to login with full password, so in place of PIN, ask I lost my PIN numbers and make the long and full process to login with password (and change pin)

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .