Between two Windows 7 Ultimate computers. Worked fine up until about an hour ago. File sharing, web browsing works ok too. Show
Remote Desktop ConnectionAn authentication error has occurred. The requested security package does not exist Remote Computer: Computer-Name [OK] I found http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/7698b90a-0708-4aa2-a33b-9734de14319c and discovered that the broken computer was missing those values, but after I restored them, it was still broken. Thanks
Problem: When attempting to login to a remote RDS Server you see an error message”. “Your computer can’t connect to the remote computer because a security package error occurred in the transport layer” Systems Affected: Currently this has only been observed on Windows 10 Professional instances of the Remote Desktop Client. However it may apply to Windows 7 Professional also. Cause: After the recent patch cycle when using the Remote Desktop Connection Client cached usernames and password credentials no longer work and display the above error. Resolution: Clear the cached credentials and re-enter them. Please follow the Step by step below
Update 31 Jan 2020 – Another Possible Resolution I had a user complaining of this same error again but the above mentioned resolution failed to fix it. Problem: “Your computer can’t connect to the remote computer because a security package error occurred in the transport layer” Cause: The Remote Desktop Client local computer was a member of the same DOMAIN as the remote RDS Server. However the local computer was on the wrong subnet and was picking ups its DNS settings from a legacy Active Directory domain which didn’t have a trust relationship with the remote DOMAIN. So when trying to connect to the remote server it was somehow using the local LEGACY domain DNS security settings and getting the above mentioned error message Resolution: In the Remote Desktop Client change the username field to be fully qualified with DOMAIN\username instead of just username only. This then forces the Terminal Server Client to ignore the incorrect AD settings from the LEGACY DNS server and use the correct settings The error message ‘Your credentials did not work’ appears when you fail to connect to the remote system using Remote Desktop connection. This error is often caused by Windows policies that prevent incoming RDP connections, or simply your system’s username. Dealing with this particular error can be infuriating as the fault isn’t in the credentials but rather somewhere else. Such an error message might appear even if you are entering the correct credentials, thus, making it an ordeal. Your Credentials Did not WorkIf you are receiving the error message after installing a fresh copy of Windows 10, then you are not the only victim. Many users depend on Remote Desktop Connections and such errors are usually a nightmare to them, however, do not worry as you will be able to get over the issue after following this guide. What causes the ‘Remote Desktop Your Credentials Did not Work’ Error Message on Windows 10?The following factors are often found to be the cause of the said error message —
Now that you know the causes of the error message, you can follow the solutions provided down below to resolve your issue. Please make sure you follow the given solutions in the same order as provided. Solution 1: Reverting UsernameAs we have mentioned, the error message is sometimes caused because the user you are trying to connect from does not exist on the Remote Desktop server. This happens when you try to change your username or install a fresh copy of Windows. Changing your username does not necessarily change it for Remote Desktop Connection and thus, your credentials will be incorrect as the user is not on the server. Thus, to isolate the issue, you will have to revert to the username that you had been using prior to the appearance of the error message. Solution 2: Editing Windows Security PolicyThere is a Windows Security Policy for Remote Desktop Connection that does not allow non-Admin users to log in using RDP. Thus, if you want to login using a non-admin user account, you will have to grant the remote desktop users access. Here is how to do it:
Solution 3: Editing Local Group PolicyIf the above-mentioned solutions do not work out for you, you can try to isolate the issue by modifying a few Local Group Policies. Basically what you will have to do is give a set of Credential Delegation policies a specific value which will most likely fix your issue. Here’s how to do it:
Solution 4: Editing RegistryIn some cases, making some changes in the registry might get rid of the error. Therefore, in this step, we will be changing some configurations in the registry. For that:
Note: Also make sure that you are logging in locally and not through a Remote Desktop Connection because it might not work with Two factor Authentication enabled. Solution 5: Disabling Windows Hello sign-in (If applicable)Sometimes the Windows Hello sign-in can be problematic. Therefore, in this step, we will be replacing the Windows Hello sign-in with the normal Password. Try this:
|