This could be due to credssp encryption oracle remediation rdp
=> http://misttesmontter.nnmcloud.ru/d?s=YToyOntzOjc6InJlZmVyZXIiO3M6MjE6Imh0dHA6Ly9iaXRiaW4uaXQyX2RsLyI7czozOiJrZXkiO3M6NjI6IlRoaXMgY291bGQgYmUgZHVlIHRvIGNyZWRzc3AgZW5jcnlwdGlvbiBvcmFjbGUgcmVtZWRpYXRpb24gcmRwIjt9
Authentication will not work and you will get this error message: An authentication error has occurred. An authentication error has occurred.
I thought we had this problem fixed. Machine has to physically be moved to other project. Security is on the minds of everyone and it should be.
Developer environment is always as per the projects requirement. Thus, do not choose this option before applying the update to all of your clients and servers. Now I'm fine as your solution fix the issue. Resolution: Hopefully this will be fixed in future updates but for now you can de below configuration in your registry to avoid above error. Perform these steps, install updates on remote server and to stay secure revert changes back to what it was. But the session will be exposed to the attack.
How to solve CredSSP Encryption error when trying RDP - There is the possibility that the current default setting could change from the tentative update and therefore impact the expected secure session requirement. Regarding the production environment, it depends by the kind of access and accountability that you have and most importantly which process to follow to apply any change, if updates are scheduled for patching Tuesday or 1 month behind and so on.
Typically this error is encountered when attempting a connection to an Azure hosted client, it has also been encountered when attempting a connection to Windows Server 2012 client. An authentication error has occurred. This vulnerability applies to all modern versions of Windows Operating systems and allows for a remote code execution vulnerability. Workaround Ensure that your windows environment has the latest updates applied. Use group policy to change the Credential Delegation at the client. Once the change is made in the group policy editor it is put into effect immediately. No restart was required to apply the change. Also changing the setting back to Not Configured does result in the error re-appearing. The following was released to cover this issue. While this article specifically calls out Azure clients, this has been encountered on non-Azure clients as well. As always it is important to install the latest Windows Updates to prevent these types of vulnerabilities. It is recommended to check at least monthly for new updates if not done automatically.
