![Remote desktop credentials not working](https://kumkoniak.com/32.jpg)
The automatic Windows patch to raise the security level is not implemented if the PC doesn’t allow automatic updates. If your PC received the May update but the target PC hasn’t implemented the CredSSP update, the PC receives the error message when it tries to connect to that PC.
![remote desktop credentials not working remote desktop credentials not working](https://www.anyviewer.com/screenshot/windows/local-group-policy-editor-window.png)
![remote desktop credentials not working remote desktop credentials not working](https://i.stack.imgur.com/zQJE2.png)
It changed the default setting from Vulnerable to Mitigated which means that any PC using CredSSP is not be able to use insecure versions. Security update deployment information: May 08, 2018 The Microsoft Security patch issued on Tuesday, May 8th triggered the problem by setting and requiring remote connections at the highest level (CredSSP Updates for CVE-2018-0886):: It recommends some steps but isn’t very clear what those changes are nor whether those changes are needed to be made by network administrators globally via group policies, or group policies on every PC and VM. It offers extensive information on a series of updates since March 2018. The link goes to this page,, and explains the Credential Security Support Provider protocol (CredSSP). This could be due to CredSSP encryption oracle remediation.įor more information, see https:/go./fwlink/?linkid=866660
![remote desktop credentials not working remote desktop credentials not working](https://www.anyviewer.com/screenshot/windows/user-rights-assignment.png)
Remote Desktop Connection Error An authentication error has occurred. Users received error messages like this when they tried to remote to machines they connected to successfully for a long time: No dice.Starting May 9, we received many reports of Remote Desktop connections failing globally. a FQDN, doing that thing with the Group Policy editor ("Allow Delegating Saved Credentials with NTLM-only Server Authentication"), and checking the Group Policy on the remote side for anything unusual-looking. I can also see it trying the saved credentials for a split second before being presented with this dialog.Īfter googling around for an answer, I've tried several things, including using an IP address vs.
![remote desktop credentials not working remote desktop credentials not working](https://content.spiceworksstatic.com/service.community/p/post_images/0000325519/5b91aa6b/attached_image/Capture3.png)
I can see that the credentials are in fact saved in the Credential Manager, and the right name is always filled in trying to log on. Then I type in the same password as always and it works. Nothing about why it didn't work, just that it didn't - "Your credentials did not work" and "The logon attempt failed". It works, and I can connect, but having saved the credentials that worked, they never seem to be accepted on subsequent logins, always rejecting them and requiring me to reenter the password part manually. Trying to log in to an Amazon EC2 instance (running Windows Server 2012 R2) via RDP.
![Remote desktop credentials not working](https://kumkoniak.com/32.jpg)