Keep in touch and stay productive with Teams and Officeeven when you're working remotely. Learn how to collaborate with Office Tech support scams are an industry-wide issue where scammers trick you into paying for unnecessary technical support services.
You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service number.
I am trying to use Remote Desktop within my private network between two machines with Win10 64 Pro version The machines are on the same wifi network on 5GHz and network is set as private on both. Guest finds host through Remote Desktop, either directly through local IP address, or through entering machine name.
Login attempts fail. I have reset my account password on the host machine. I only have one user on the machine. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. We appreciate your post here in the Community forums. Note: You may also check this thread from time to time as we have other community members here who may also be able to answer your concern. Did this solve your problem? Yes No. Sorry this didn't help.
April 14, Keep in touch and stay productive with Teams and Officeeven when you're working remotely. Site Feedback. Tell us about your experience with our site.
Can you please provide assistance.Experiencing issues while using Remote Desktop connections are not uncommon. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials.
Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. In such case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. Just make sure that you follow each one of them in sequence.
According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. Refer to these steps:. As mentioned, one the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. You can also try to edit the Windows Security Policy as it could help in resolving the error.
This Windows Security Policy, when enabled, will not allow non-admin users to logon to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself. On the other hand, if you are currently experiencing other issues aside from this one, there is a one-click solution known as Advanced System Repair you can use.
Aside from that, it also cleans out your computer for any junk or corrupted files that help you eliminate any unwanted files from your system. For complete set of instructions in downloading and using it, refer to the steps below.
Our software needs to be installed on your computer to work. Please follow the step below to get started:. Malware may reinstall itself multiple times if you don't delete its core files. This may require tracking down dozens of files in different locations. We recommend downloading Advanced System Repair to eradicate Malware for you it should cut down the time to about 15 minutes.How To Fix Remote Desktop Connection Erro
Unable to find your error above? Please follow the step below to get started: Step 1: Open web browser on your computer Step 2: Go to errortools. Live Support.Problems with Remote Desktop connections are common.
While attempting to connect to the Remote Desktop network, many users have reported the error — Your credentials did not work, The login attempt failed.
If you face this issue, obviously, the first step should be verifying the credentials.
How to Fix Remote Desktop Error: “Your credentials did not work” in Windows 10
However, a significant number of users have noted that the credentials were correct and in many cases worked fine earlier.
Users have reported this problem on newly installed versions of the operating system and immediately after reinstalling Windows. The issue is probably caused due to the Windows security policies or the username might have been changed recently.
The latter is especially true when you reinstall Windows and enter a new username. The credentials for the Windows Remote Desktop connection do not change automatically.
The Network Adapter Troubleshooter will help check the flaws with the network if any and correct the same. Select the Network Adapter Troubleshooter from the list. It has been reported that this issue occurred on systems where the network profile was set the public. Changing it to private helped in resolving the issue.
Click on Change connection properties. Shift the radio button for Network profile to Private. In this case, you could change the username back to what it was before the reinstallation and see if that helps. If you need to allow non-admin users to use the Remote Desktop connection, you would have to edit this policy. This is obviously possible if you are the administrator of the system yourself. Press Enter to open the Local Security Policy.
In the next window, select Add user or group. Click on Check names to resolve the username. In case you need to set this policy across a series of systems, the same could be done through the Group Policy Editor. The procedure for the same is as follows:. Hit Enter to open the Group Policy Editor. Navigate to the following path:. KaranKhanna TWC. March 11, KaranKhanna TWC Karan Khanna is a passionate Windows 10 user who loves troubleshooting Windows problems in specific and writing about Microsoft technologies in general.We've had this issue with some of our machines lately.
Our machines are domain-joined and Azure-AD joined. They are enrolled in Azure Intune as well. We have a setup going where any user outside of our network can RDP into their work machine via the edge. The issue is that every time a few not all of us try, we get "Logon attempt failed" errors and nothing else. We tried several different username combos: name domain. RDP has worked in the past. Windows Firewall is enabled on the machines but not all of the rules are. The ones that are off are set to allowed anyway regarding RDP.
I would check your GPO for setting that could be causing issues, such as how many can logon at time and etc. Also check the logs on the remote machine for the errors. We don't have a GPO enabled for limiting remote desktop. You have to ensure no authentication information is sent when connecting, forcing the login screen to appear. Note: when setting up the computer accepting the connection make sure not to force Network Level Authentication checkbox on the menu where you allow the remote connections.
I too have had this problem trying to remote into a client site; from my PC win 7 when this first started years ago and now Win10, trying to remote into a Windows server.
All login attempts gave me an invalid password response and it wasn't the password3 strikes, account is locked. From the Windows desktop login, I could then switch users to a non-locked account and voila, I'm in. This customer just migrated that server to Windows Server 2k That however, played differently.
Once I locked out the "booster login", RDP would simply give me an "internal error occured". Remote Desktop Connection Manager no longer took me to the windows desktop for the "account is locked" notification, and simply reported error account is locked and I could go no further. However, going back to Remote Desktop Connection, saving a connection file for that server, following the edit instructions for enablecredsspsupport:i:0 authentication ahnd level:i:2, allowed me to log in; and it's a windows desktop login.
With these settings I do not input my credentials in the RDC window, but over on the blue windows login screen. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. We have the latest Windows 10 Updates and the Build Which of the following retains the information it's storing when the system power is turned off?
Verify your account to enable IT peers to see that you are a professional. Check the security one as well, logs for remote log-ons usually show up in there. Josh wrote: chargp02a wrote: We don't have a GPO enabled for limiting remote desktop.
remote desktop will not accept my password
Unfortunately, I don't see anything in there regarding anything Remote-like. To do this, you must create and edit an. This topic has been locked by an administrator and is no longer open for commenting.
Please enter new credentials. What exactly has to be configured on the server to allow me to keep the password saved on my machine? To be able to use saved credentials in this situation you need to do the following in your Windows 7 machine :. When it's an IP address it will never save the credentials. References: here. Answer can also be found here in the similar question.
The user, when logging in and getting this error message, can click Delete on the login window to remove and re-enter the credentials. If you are a sysadmin and you have users with this issue, it is likely that the GPO was set that way intentionally, so don't just turn that security feature off.
Sign up to join this community. The best answers are voted up and rise to the top. Home Questions Tags Users Unanswered.
Asked 8 years, 10 months ago. Active 3 years ago. Viewed 14k times.
Unfortunately, there are some policy restrictions, because when I connect with saved password I'm getting the following message: "Your credentials did not work The server's authentication policy does not allow connection requests using saved credentials. Shaeak Silentread Shaeak Silentread. Are you the user or admin? Active Oldest Votes. Jake Jake 21 1 1 bronze badge. Close all windows by pressing OK. Now you should be able to use your saved credentials.In Windows 10you can use Remote Desktop feature to connect systems remotely.
This article talks about an issue which is related to credentials used in Remote Desktop connectivity. In this case, I was pretty sure that the credentials were correct.
Even they worked fine with other machines but one of my machines start throwing this error. Click OK to open Security Policy snap-in. Double click on the policy to modify its status.
Click Apply followed by OK. Close Security Policy snap-in. In the right pane of Credentials Delegationlook for the policy setting named Allow delegating saved credentials.
The policy is Not Configured by default. Double click on it to modify its status:. On the policy configuration window, set it to Enabled. Under Optionsclick Show button. Repeat step 4 for following GPO settings as well at same path mentioned in step 2 :.
Then check if your Remote Desktop Connection is working. For me Windows 8 ThinkPadthe issue was with my registry editor compatibility level.
Your email address will not be published. Save my Name and Email in this browser, for the next time I comment. Please enter new credentials. The logon attempt failed.Keep in touch and stay productive with Teams and Officeeven when you're working remotely. Learn how to collaborate with Office Tech support scams are an industry-wide issue where scammers trick you into paying for unnecessary technical support services.
You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service number. When trying to use saved credentials in Remote Desktop Connection you might receive this message: Your credentials did not work. Your system administrator does not allow the use of saved credentials to log on to the remote computer terminal.
Please enter new credentials. To be able to use saved credentials in this situation you need to do the following: 1. Run cmd and enter gpupdate command to update your policy. Now you should be able to use your saved credentials.
Did this solve your problem? Yes No.
Sorry this didn't help. April 14, Keep in touch and stay productive with Teams and Officeeven when you're working remotely. Site Feedback. Tell us about your experience with our site. Created on May 16, Even though I've clicked "edit" and put in my credentials Windows 7 Remote Desktop Connection does not automatically use them.
The checkbox "always ask for credentials" is NOT checked. When I connect from other Windows clients to the same target machine their saved credentials are used properly. Is this a Windows 7 Remote Desktop Connection bug or am i doing something wrong? This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question BPatti Replied on November 11, Thanks for marking this as the answer.
How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. How satisfied are you with this response? This site in other languages x.