Windows 7 rdp authentication error

windows 7 rdp authentication error

Method 1: Change the Remote Desktop Settings In order to fix the “An authentication error has occurred the function requested is not supported. What causes 'An Authentication Error has occurred' while connecting to a Remote Desktop? · Latest updates are not installed in either the. When a local computer running Windows attempts to access a Windows ECS using RDP (for example, MSTSC), an identity authentication failure. windows 7 rdp authentication error

watch the thematic video

An authentication error has occured. The function requested is not supported [FIXED]

Why Does an Authentication Failure Occurs After I Attempt to Windows 7 rdp authentication error Log In to a Windows ECS?

Symptom

When a local computer running Windows attempts to access a Windows ECS using RDP (for example, MSTSC), an identity authentication failure occurs and the desired function is not supported.

  • If the error message contains only the information that an identity authentication failure occurs and that the desired function is not supported, rectify the fault by following the instructions provided in Solution.
  • If the error message shows that the fault was caused by "CredSSP Encryption Oracle Remediation", as shown in Figure 1, the fault may be caused by a security patch released by Microsoft in March 2018. This patch may affect RDP-based CredSSP connections. As a result, setting up RDP-based connections to ECSs failed. Rectify the fault by following the instructions provided in Microsoft documents.
    Figure 1 Failed to set up a remote desktop connection

Solution

Modify the remote desktop connection settings on the Windows ECS:

  1. Log in to the ECS.
  2. Click Start in the lower left corner, right-click Computer, and choose Properties from the shortcut menu.
  3. In the navigation pane on the left, choose Remote settings.
  4. Click the Remote tab. In the Remote Desktop pane, select Allow connections from computers running any version of Remote Desktop (less secure).
    Figure 2 Remote settings
  5. Click OK.

Windows – Remote Desktop Error ‘An authentication error has occurred. The Local Security Authority cannot be contacted’

KB ID 0000826

Problem

Update May 2018: This is Following ArticleIs Probably What You Are Looking For;

Windows RDP: ‘An authentication error has occurred’

 

 

I saw this while attempting to create a remote desktop connection to a Windows 2012 Server, windows 7 rdp authentication error. (Though connecting to Windows 8 will be the same).

RDP Error Local Security Authority

I’d only just set this server up, and knew I’d enabled RDP, and I was attempting to connect as the domain administrator, so at first I was a little perplexed.

Solution

If you have direct/local access to the machine you are trying to connect to.

1. Press Windows Key+R > In the run box type sysdm.cpl {enter} > Remote.

RDP Error Local Security Authority

2, windows 7 rdp authentication error. Remove the tick from “Allow connections only form computers running Remote Desktop with Network Level Authentication (recommended)”.

3. Try again.

If you do not have direct/local access to the machine you are trying to connect to.

1. On YOUR Machine > Windows Key+R > type regedit {Enter} > File > Connect Network Registry > Type in the details for the machine you are trying to connect to > OK.

Connect to remote Registry

2, windows 7 rdp authentication error. Navigate to;

{remote-machine-name} > HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Terminal Server > WinStations > RDP-Tcp

Locate the UserAuthentication value and change it to 1 (one) > OK > Exit the registry editor.

UserAuthentication Registry

3. Try again.

Disable RDP Network Level Authentication via Group Policy

If the destination server is in a remote data centre or remote location, and you cannot access the System Properties, you can turn this option off with group policy, windows 7 rdp authentication error, and wait a couple runtime error r6034 photoshop hours.

1. On a DC > Start > Group Policy Management > Either create a new group policy object and link it to the OU containing the problem machine, or edit and existing one. (Here on my test network I’m going to edit the default domain policy – WARNING this will disable this feature on all machines in a production environment!

2. Navigate to;

Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security

3. Locate the ‘Require user authentication for remote connections by using Network Level Authentication’ policy.

GPO Require RDP Network Level Authentication

4. Set the policy to Disabled > Apply > OK > Close the Group Policy Management Editor.

GPO Disable RDP Network Level Authentication

5, windows 7 rdp authentication error. How long before the Group Policy will affect the target machine? Group policies are processed when a machine starts up, after this they are processed again, (only if they have changed), the time period varies (so all clients do not update at the same time), windows 7 rdp authentication error. The interval is 90 minutes, with a random offset off 30 minutes. So the maximum time it can possibly take is 2 hours (120 minutes). Note: this is the default setting, it can be manually changed up to (45 Days) 64,800 minutes, (though why would you do such a thing?)

Windows – Forcing Domain Group Policy

Related Articles, References, windows 7 rdp authentication error, Credits, or External Links

NA

Remote Desktop Connections Fail

Starting May 9, we received many reports of Remote Desktop connections failing globally. Users received error messages like this when they tried to remote to machines they connected to successfully for a long time:

Remote Desktop Connection Error

An authentication error has occurred. The function requested is not supported Remote computer: <computer name> This could be sacred error code 10026 to CredSSP encryption oracle remediation. For more information, see https:/go.microsoft.com/fwlink/?linkid=866660

The link goes to this page, https://support.microsoft.com/en-us/help/4093492/credssp-updates-for-cve-2018-0886-march-13-2018, and explains the Credential Security Support Provider protocol (CredSSP). It offers extensive information on a series of updates since March 2018. 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.

The Microsoft Security patch issued on Tuesday, windows 7 rdp authentication error, May 8th triggered the problem by setting and requiring remote connections at the highest level (CredSSP Updates for CVE-2018-0886)::

Security update deployment information: May 08, 2018

It changed the default setting from Vulnerable to Mitigated which means that any PC using CredSSP is not be able to use insecure versions. 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.

The automatic Windows patch to raise the security level is not implemented if the PC doesn’t allow automatic updates. This mismatch between the implementation of a security requirement (which is not optional) without the corresponding automatic update may be the source of this problem.

However, there are many situations such as development, testing, build, staging, and deployment environments which require a stable environment that would be destroyed by automatic Windows updates.

We continue to research this.

The symptoms are rather strange because we found that some machines successfully connected while others didn’t.

For instance, we had a Windows 7 machine that hosted Remote Desktop. A Windows 7 PC had no problem connecting to it, but the same user connecting from a Windows 10 machine failed when that was never an issue before and the host machine allowed remote connection for years.

There are also reports of problems with Windows 10 machines connecting to Windows 10 machines, and people locked out of their Azure VMs.

One could rollback the security update, but rather than risking other security problems, there’s a quick fix.

Simply adjust the Remote Desktop settings on the host machine to a lower security level. From File Explorer, choose Computer, right-click and select Properties, then click Change Settings, and go to the Remote tab.

From Windows 10, uncheck the option to “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)”:

From Windows 7, it’s setting the option to the Less Secure option rather than More Secure:

Once these are set, users can remote to the machine again.

Microsoft Comment

Based on this blog post, a Microsoft colleague told us this:

“I double checked the Windows bug database and they are aware of the problem, windows 7 rdp authentication error. No ETA on a fix yet unfortunately. Your workaround is what’s suggested to temporarily get around the error, although it is not suggested as a long-term fix.”

This section was added after our initial workaround and is based on the experience of many users struggling with this problem.

The problem is often caused because the local machine is patched with the Windows Update and the machine it’s connecting to is not patched for the CredSSP issue. If both systems were patched then this error would not occur.

There are two options:

Update the Target Machine

Update the target machine with the patch for the CredSSP issue (preferable).

Update the Local Machine

In many cases, you don’t have the option to modify anything on the target machine. You may even be prevented from modifying your own machine, but assuming you have administrator rights, you can change the Group Policy on your local machine to use the Vulnerable setting.

Big picture, it’s ridiculous to lower one’s security settings to connect to a machine that wasn’t updated. It would be much better if it prompted or automatically connected to lower level machines without turning off the higher security level for everything else. All it takes is one target machine that you can’t modify to force this change on your machine. But at least you can get your work done.

  1. Enter run “gpedit.msc” to edit group policy, or from Windows start, enter “Group Policy” and select “Edit group Policy”:
    1. Windows 10
    2. Windows 7
  2. From the treeview, choose Computer Configuration -> Administrative Templates -> System -> Credentials Delegation
  3. Select “Encryption Oracle Error reporting e_all php from the right pane (if it’s not there, it probably means your machine wasn’t patched):
  4. Enable and set the Protection Level to Vulnerable:

Hope this helps.


We’ve discovered problems with VPN connection if the PC has Remote set to the higher security level.

The network connection fails with error: Cannot load the Remote Access Connection Manager service. Error 711:

Lower Your Remote Desktop Security to have the Security to Make the VPN Connection

Apparently, the Remote Desktop setting on the client side impacts its ability to connect via VPN to the host side.

By lowering the setting to less secure for others to connect to the PC, the PC can now successfully connect to the VPN. What a mess.

I’ve also been involved in other online discussions:

It’s late August, and it’s shocking that this problem remains after so many months. I am extremely frustrated by the Windows update policies and Microsoft’s inadequate testing before these security patches are deployed. This is very disruptive and dangerous to many organizations trying to fulfill their missions expecting their PCs to be reliable.

Microsoft security “purists” claim the current approach is necessary to address the serious threats facing users. I guess it wouldn’t be an issue if the updates worked without disruption. However, the downside of this medicine may exceed the illnesses they are trying to prevent.

Hope you are windows 7 rdp authentication error to resolve this and move on.


Additional Remote Desktop Connection Resources

This entry was posted in Application Development, cloud computing, Remote Desktop by LukeChung. Bookmark the permalink.

How to resolve RDP authentication error due to the CredSSP encryption oracle remediation on Windows OS

This error occurs if you attempt to establish an insecure RDP connection, and the insecure RDP connection is blocked by an encryption Oracle Remediation policy configuration on the server or client. This configuration defines how to build an RDP session using CredSSP and whether unsafe RDP will be allowed.

credssp1

To resolve this issue, you need to install the update on your servers. However, if you want to connect to a server that does not receive the update, you can downgrade the protection level to Vulnerable. You can do this through a group policy. Also, you can adjust the Remote Desktop Settings to fix Remote desktop authentication errors in a simple way.

To adjust the Remote Desktop Setting

  1. Click on the Windows key to open start and search and then click on the application which is shown in the below image to execute the .

    credssp2

  2. Enter as mentioned in the below image and click on button.

    credssp3

  3. Now windows 7 rdp authentication error the tab and deselect the option which is shown in the below image.

    credssp4

  4. Once the option is deselected then press the and buttons.

To set the protection level to Vulnerable via Group Policy

  1. Click on the Windows key to open start and search and then click on the application which is shown in the below image to execute the .

    credssp5

  2. Enter as mentioned in the below image and click on button.

    credssp6

  3. Now go to the following path: Computer Configuration > Administrative Templates > System > Credentials Delegation

    credssp7

    antiterror alfa accosiation of veterans src="https://www.layerstack.com/img/docs/resources/credssp9.png" alt="credssp9">

  4. Double click on the mentioned in the below image to edit.

    credssp10

  5. Now set it toand set the protection level to as in the below image, and click on the button.

    credssp11

Related Tutorials

After the May 2018 update to Windows 10, most computers running Remote Desktop Windows 7 rdp authentication error functionality are facing RDP authentication error, function requested is not supported issue windows 7 rdp authentication error they get the following error while logging in to a remote computer via RDP.

An authentication error has occurred.
The function requested is not supported

Remove computer: [computername]
This could be due to Drive_layout_information_ex a error encryption oracle remediation.
For more information, see https://go.microsoft.com/fwlink/?linkid=866660

RDP Authentication Error Function Requested Is Not Supported

This is due to a recent vulnerability fixed in Windows 10 and Windows 7. After installing the latest update KB4103727 for Windows 10 Version 1709 and KB4103718 for Windows 7, you will start getting this error.

If you are running Remote Desktop Protocol on your network and allow connections to your server, this error should probably fix this error immediately.

What is RDP authentication error?

Windows uses CredSSP protocol (Credential Security Support Provider) for authenticating clients on the RDP servers.

A serious vulnerability was found in CredSSP protocol which could impact the security of both the server and the client.

To fix this issue, Microsoft introduced the Network Level Authentication (NLA) protocol which works along with CredSSP and pre-authenticates RDP client users over TLS/SSL or Kerberos.

In a situation where the server does not have the required Windows update patch, an updated client computer will refuse to connect to the non-secure server because Microsoft makes it mandatory to enable NLA for secure remote desktop connection.

4 solutions to RDP Authentication Error Function Requested Is Not Supported

Let’s go through some resolutions to this problem.

Solution 1: Install updates on the target computer

The first and most recommended solution to this issue is to update the target computer on which you are trying to connect remotely. Go to Windows Update and check for updates. Install all the updates specifically related to CVE-2018-0886.

Specifically, if the target computer is running Windows Server 2016, you should install KB4103723 and if you are using Windows Server 2012 R2, then you should install KB4103725.

A server reboot will be required after installing windows 7 rdp authentication error updates.

If you do not want to update your computer or if it’s not in your access, then you can try the other solutions listed below.

Solution 2: Using Group Policy

  1. Go to Run –> gpedit.msc to open Group Policy Editor.
  2. Go to the following policy path:
    Computer Configuration -> Administrative Templates -> System windows 7 rdp authentication error Credentials Delegation
    Credentials Delegation group policy
  3. From the right-hand pane, open Encryption Oracle Remediation.
  4. Select Enabled and set the protection level to Vulnerable.
    Encryption Oracle Remediation policy
  5. Go to the command prompt and run the following command:
    gpupdate /force

This will apply the group policy immediately and you will be able to use the Remote Desktop without restarting the computer.

Solution 3: Using Registry Editor

The same can be achieved through Windows Registry. This method is especially useful for Windows Home editions where there is no Group Policy Editor (although you can install gpedit.msc easily). Here are the steps:

  1. Go to Run –> regedit to open Registry Editor.
  2. Go to the following key:
    HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters
  3. In the right-hand pane, edit the DWORD value of AllowEncryptionOracle key to 2.
  4. If you can’t find the key, you will need to create it. Alternatively, you can download the following registry file, double-click to run it and it will automatically create a key and set it up for you.

    Fix RDP Authentication Error Function Requested Is Not Supported 1CredSSP Parameters Registry (364 bytes, 12,934 hits)

This is a simple registry file, windows 7 rdp authentication error. If you don’t want to download it, just create a text file with the following contents:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters] "AllowEncryptionOracle"=dword:00000002

Save the file in with .reg extension and run the file to add these values to the Windows Registry.

Solution 4: Uninstall updates from your computer

Another workaround is to uninstall the updates from your computer. If you are using Windows 10 Version 1709, you should uninstall the update KB4103727 and KB4103718 if you’re running Windows 7. Uninstalling these updates requires the computer to be restarted.

Final words

Although you can use any of the above mentioned methods to resolve this issue of RDP Authentication Error Function Requested Is Not Supported, I recommend that you either use Solution 1 (install latest Windows updates) or Solution 2 (using local group policy) for the resolution.

I had the same issue with my network. All the above mentioned solutions worked for me on my company network. I fixed it by updating all my Windows Server installations and also the client computers. There were some environments which required not updating the server at all. I used the second method to fix RDP authentication error messages from those servers.

What are your thoughts about this?

Also see:

Subscribe to our Newsletter

Fixed: Remote Desktop An Authentication Error Has Occurred [MiniTool Tips]

What will you do when you encounter the error “An authentication error has occurred”? If you don’t know, then this post written by MiniTool is what you need. Windows 7 rdp authentication error can find several efficient methods to fix the error.

When you try to establish a connection with another remote computer using Remote Desktop Connection, you may get an error message saying that “An authentication error has occurred the function requested is not supported”.

So how to fix the “Remote Desktop An authentication error has occurred” error? The methods are shown below.

Method 1: Change the Remote Desktop Settings

In order to fix the “An authentication error has occurred the function requested is not supported” error, the first step you can take is to change the remote desktop settings.

Here is the tutorial:

Step 1: Press the Win key + R key at the same time to open the Run box.

Step 2: Type sysdm.cpl in the box and then click OK to open the System Properties window.

Step 3: Go to the Remote tab and then uncheck the Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended) option. Click Apply and OK to save changes.

change the remote desktop settings

Step 4: Restart your computer and then check if the “An authentication error has occurred” error is gone.

Method 2: Change the Group Policy Settings

You can also try to change the Group Policy settings to fix the “An authentication error has occurred” error. Follow the detailed instructions below:

Step 1: Open the Run box and then type gpedit.msc in the box. Click OK to open the Local Starcraft 2 opengl error Policy Editor window.

Step 2: Click Computer Configuration and then select Administrative Templates > System > Credentials Delegation on the left of the window.

Step 3: Double-click the Encryption Oracle Remediation on the right of the window.

find Encryption Oracle Remediation

Step 4: Choose Enabled and then select the Vulnerable option windows 7 rdp authentication error the Protection Level drop-down menu. Click Apply and OK to save changes.

choose Enabled

Step 5: Close all the windows. Type cmd in the Run box and then click OK to open the Command Prompt window.

Step 6: Type gpupdate /force in the window and then press Enter.

Step 7: Reboot your computer and then check if the error is fixed.

Tip: If your Windows Defender is blocked by Group Policy, then you can read this post - Windows Defender Blocked by Group Policy? Try These 6 Methods to find answers.

Method 3: Edit the Registry

There is another method you can try to fix the “An authentication error has occurred” error – edit the Registry. Here is a quick guide:

Step 1: Type regedit in the Run box and then click OK to open the Registry Editor window.

Step 2: Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters.

Step 3: Double-click the AllowEncryptionOracle DWORD to open its Edit DWORD window.

Step 4: Change the Value data to 2 and then click OK.

edit the Registry Editor

Note: If you can’t see the AllowEncryptionOracle DWORD, set up a new DWORD by right-clicking an empty space on the right of the Registry Editor window and selecting New > DWORD. Enter AllowEncryptionOracle as the DWORD name.

Step 5: Reboot your computer and then check if the “An authentication error has occurred” error is fixed.

Bottom Line

There are three useful methods to fix the “An authentication error has occurred” error in this post: change the remote desktop settings, change the Group Policy settings and edit the Registry.

About The Author

Sonya

SonyaFollow us

Position: Columnist

Author Sonya has been engaged in editing for a long time and likes to share useful methods to get rid of the common problems of Windows computers, such as Windows Update error. And she aims to help more people to protect their data. What’s more, she offers some useful ways to convert audio and video file formats. By the way, she likes to travel, watch movies and listen to music.

User Comments :

Error: "An authentication error has occurred. The function requested is not supported" (4237605)

Product(s):
One Identity Safeguard for Privileged Passwords
6.13.1, 6.13, 6.0.13 LTS, 6.12.1, 6.12, 6.0.12 LTS, 6.11.1, 6.11, 6.0.11 LTS, 6.10.1, 6.10, 6.0.10 LTS, 6.0.9 LTS, 6.9, 6.0.8 LTS, 6.8, 6.0.7 LTS, 6.0.6 LTS, 6.7.3, 6.7.2, windows 7 rdp authentication error, 6.7.1, 6.7, 6.6, 6.0 LTS, 2.11.2, 2.11.1, 2.11 windows 7 rdp authentication error
One Identity Safeguard for Privileged Sessions
6.13.0, 6.12.0, 6.11.1, 6.11.0, 6.10.1, 6.10.0, 6.9.4, 6.9.3, 6.9.2, 6.8.1, 6.7.2, 6.7.0, 6.0.10, 6.0.9, 6.0.7, 6.6.1, 6.0.6, 6.6.0, 6.5.0, 6.4.0, 6.3.0, 6.2.0, 6.1.0, 6.0.5, opened service error 1275, 5.10.0, 5.9.0, 5.8.0, 5.7.0, 5, 5.6.0c, 5.0.10, 5.0.9, 5.0.8, 5.0.7, 5.0.6, 5.5.0b
Safeguard On Demand
windows 7 rdp authentication error Hosted
Safeguard for Error 21 selected disk not exist Sessions On Demand
canon mp495 error code e04 Hosted javascript error cannot convert ge
Topic(s):
Troubleshooting, Configuration, windows 7 rdp authentication error, Best Practices
Article History:
Created on: 8/22/2022
Last Update on: 8/24/2022

Your Request will be reviewed by our technical reviewer team and, if approved, will be added as a Topic in our Knowledgebase.

You can find online support help for*product* on an affiliate support site. Click continue to be directed to the correct support content and assistance for *product*.

© 2022 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy

The One Identity Portal no longer supports IE8, 9, & 10 and it is recommended to upgrade your browser to the latest version of Internet Explorer or Chrome.

Upgrade to IE 11 Click here

Upgrade to Chrome Click here

If you continue in IE8, 9, or 10 you will not be able to take full advantage of all our great self service features.

0 Comments

Leave a Comment