Many servers had to be rebooted as people thought it was a server-side error!įortunately, Microsoft was aggressive in their stance to tighten the security of applications. Unfortunately, this code patch created some ripples, which lead to authentication errors in the Remote Desktop Protocol (RDP) of a Windows server.įurther, a CredSSP error resulted in Windows servers becoming inaccessible via RDP for many users. This registry entry is a temporary workaround until you have patched your server, when you have done that, remove the setting with this command.On 8th May 2018, Microsoft launched a patch to fix gaping vulnerabilities exposed in the CredSSP module. Run this from an elevated command prompt to achieve the same result: REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters" /v AllowEncryptionOracle /t REG_DWORD /d 2 Connect to the server that you were unable to connect to before.Set the value of AllowEncryptionOracle to 2 Set the new registry entry to have a value of 2:.Create a new DWORD value called “ AllowEncryptionOracle“.HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters Navigate to the following registry key, or create it if it does not exist:. Modify the registry to allow your machine to connect to it: This is because the server you are connecting to is not patched up to date, and the machine you are connecting from is. This is a quick credssp registry fix for the following error when trying to connect to a machine using RDP (Remote Desktop): An authentication error has occurred.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |