Try Now. Products Solutions Partners Support Company. Sign In Help. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
New Contributor. Hello Today we upgrade SA from 8. Before upgrade system log has next message [ Users on bit mashine have authentication Error 0x when connect to RDP link Where are problem - on client, 8. Tags 2. Tags: Pulse Desktop Client.
All forum topics Previous Topic Next Topic. Community Manager. Hello llia, This would be a two part problem. The dspwasasehandler process crash would be a known issue between 8.
Fix: RDP Authentication Error Has Occurred – The Function Requested Is Not Supported
This issue was resolved in 8. In an effort to resolve our previously limitation with NLA support, this is now support in 8. I did some searching online and found a similar issue reported with the native RDP client. Could you try the following steps and see if this helps resolves your issue?
Another possibility that has been discussed is the issue may be related to having logging enabled. Hello We had no time therefore for the fast decision we made rollback. If the problem appears again we are update to 8. I check my setting for. Occasional Contributor. Any word on this issue? I upgraded from 8.An Authentication error has occured. The specified data could not be encrypted.
All other operation stop, start etc work perfectly. This problem occurs because the CredSSP incorrectly encrypts the data when the size of the security token for the user account exceeds 16 kilobytes KB. To resolve this issue, install this hotfix on the terminal server that is running Windows Server R2 and on any Remote Desktop clients that are running Windows 7 or Windows Server R2.
You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email.
Notify me of new posts via email. Enter your email address to subscribe to this blog and receive notifications of new posts by email. Sign me up! The cluster nodes have this hotfix installed. Rate this:.
Fix: An Authentication Error Has Occurred (Code: 0x80004005) – Remote Desktop
Like this: Like Loading Comments 1 Trackbacks 1 Leave a comment Trackback. Maarten Wijsman. Hi, I ran into this some time ago. Cheers, Maarten Wijsman.
Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email required Address never made public. Name required. Join 1, other followers. Search for:. Linux Integration Services Version 3. So What is New?!!! This blog covers Virtualization technology and Cloud Computing.
This weblog does not represent the thoughts, intentions, plans or strategies of my employer.I have researched a number of articles regarding this error and none of them seem to really address the issue am I getting. Hoping someone can help me out.0x80004005 error fixing method on windows7 32bit and 64bit Computing
That's probably a problem with your profile. You should try another logn to access the server and delete that profile that cannot login. US is an IT service provider. Can they resolve the server's name with nslookup at the command prompt?
Yes, they are able to perform a nslookup froom command prompt, yet another thing to add to this weird issue. Resolve the webportal address both with SSL and without : does it resolve correctly both ways?
Is there a dual homed scheme going on? Hate to ask the easy question but We installed the Remote Desktop Services on this Server. More specifically, this server in particular is the Remote Apps Server. Sounds like you took the simpler road then which is good We do have this server putting out a self signed certificate.
However, I changed the certificate to one issued by our CA server. This was after the error was occurring. The AD servers are separate, but on the same domain obviously. Well it could be having issues communicating with the authentication servers AD then, or the certificate could be throwing errors that stop the process We are having the same 0x when attempting to RDP into other servers, though that also is intermittent as well. Both of the Authentication servers are virtual, one is running on a VMWare box and the other is on a brand new Hyper-V box.
If it's only in the afternoon it sounds like you're hitting a limit somewhere Are they trying to log into a workstation on the network, or is it just remoting in to the server that's giving them the error?
Is it possible that multiple people are trying to RDP into the same workstation? Windows workstations are limited to a single user logged in at a time Maybe check your DNS server itself to see if there are some old records in need of scavenging?
Flush dns didn't work, still giving the same error code. The servers that we are trying to connect to are all Server R2 servers, so they have the newest records within DNS. Is there a GPO that auto appends addresses for the clients? Perhaps it's not letting you see that it is automatically trying to add xyz. I'm grasping at straws at this point. We do not have a GPO that auto appends addresses for any of the clients.
Though we do need to update our GPO's because of the functional level upgrade. Nothing looks out of the ordinary to me. To continue this discussion, please ask a new question.My laptop is running Windows 10, and I am only having problems connecting to the servers through an isolated VPN.
I am able to connect to the servers via this isolated VPN on another laptop, so it must be a setting on this specific laptop that is preventing my connection. Hi Nicole. I removed it, and attempted connecting - same issue. Sure enough, I go back to RDM, and put in a domain into the credential entry, and now it works locally, and the other PC I made sure to refresh the data source to be sure.
So - I still don't know why the lack of domain name only became a problem AFTER the credential change, but it appears to be working now! Could you please confirm the OS version of another workable laptop? If it is running windows 10 as well, please check and compare the patch updates between two laptop as as it would be helpful for keep the patch same.
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff microsoft. Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance. Don't use the traditional rdp client, use the app from windows 10 store, then you can able to connect to it. Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in.
United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Remote Desktop clients. Sign in to vote. Hello, I am trying to RDP to a Windows server and receiving the following error message: an authentication error has occurred code 0x My laptop is running Windows 10, and I am only having problems connecting to the servers through an isolated VPN. Please let me know if you have any ideas. Thank you, Nicole. Friday, February 8, PM.
Thanks, Jenny Please remember to mark the replies as answers if they help. Monday, February 11, AM. Hi, Just checking in to see if the information provided was helpful.When I specify the RDP server name in the mstsc. After I uninstalled the latest updates and rebooted my computer, I was able to connect to a remote server via RDP.
As I understand, this is a temporary workaround. A new cumulative Windows update package will arrive and will be installed next month, and the RDP authentication error will return.
Can you advise me something? You are absolutely right.
Why is this happening? The fact is that the latest security updates released after May are installed on your Windows 10 desktop. Your computer simply blocks the remote desktop connection to a server that uses the vulnerable version of CredSSP. What can you do to fix this problem and connect to your RDP server? In Windows 7 Windows Server R2this option is called differently. After that, you should successfully connect to the remote desktop.
Thanks you for this information. I deploy the virtual machine from ISO win10 ent. Notify me of followup comments via e-mail. You can also subscribe without commenting. Leave this field empty. Home About. Remote Desktop Connection An authentication error has occurred. The function requested is not supported. Related Reading. October 6, Now, use the Default.
You no longer have to provide credentials before establishing a remote desktop connection. This really fixed my RDP issue to a particular server. I was getting this error when i connect to only a particular server.
I was however able to connect to any other machine except for one. After having tried all the options available on the net, I had given up. This solution solved my problem. Thank you. This did NOT work for me until I added the last line but with "i:0".
Search Become The Solution:. Great advice. Cancel Reply. Great advice Solved! Cancel Update Comment. Matumbo Mwange on Wednesday, 27 May Weeks of failed attempts until I found your article!!
Much appreciated!!!!! Abi on Monday, 16 December Anonymous on Monday, 09 December This worked! Patrick on Monday, 11 November Karthik G on Monday, 04 February You are Awesome.
Thank you so much. Thank you so much:D You are Awesome. Thank you so much:D. Anubhav Gupta on Wednesday, 23 January Thanks a lot!! Dinesh on Thursday, 11 October The Local Security Authority cannot be contacted. Posted in TroubleshootingVirtualization. Subscribe to comments with RSS. Woah, you make my day. I am searching for weeks for this error. Never thought about the Hyper-V physical host.
Thanks a lot. I am having the same problem but I am unsure how to do what you described. What exactly am I suppose to change? IT Core. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account.
You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. Enter your email address to subscribe to this blog and receive notifications of new posts by email. Sign me up! IT Core Blog Never stop questioning. Curiosity has its own reason for existing…. Hyper-V Error: An authentication error has occurred. Rate this:. Share this: Twitter Facebook. Like this: Like Loading Michael Reukauff April 6, at PM. Jeff Barton May 15, at PM. Got it!
It worked after that. Jeff Barton May 16, at AM. Anonymous June 4, at AM. I got this error when my password expired. After I changed my password things worked again.
Leave a Reply Cancel reply Enter your comment here Fill in your details below or click an icon to log in:. Email Address never made public.