The logon attempt failed for the remote desktop connection
Remote Desktop is one of the rich features of Windows 10 which enables users to remotely connect to computer devices. With the help of an internet connection, users can share their desktop screen with any other computer device located remotely. Here are some guides that I have written on RDP, how to allow saved credentials for RDP connection, how to remove saved RDP credentials entries in Windows 10, and please visit the following link for more articles on RDP. Here are some articles I have written relating to Active Directory; How to set up a Domain Controller, what is Active Directory Forest, Trees, Domain and Sites, how to install and configure Active Directory Certificate Services, how to set up Azure AD Tenant and methods for integrating Azure Active Directory with on-premise Active Directory.
Sometimes this Remote Desktop Feature will not work correctly for multiple reasons as described below
– Remote Desktop cannot connect to the computer
— Windows 10 RDP client stopped working
— The user is not part of the right security group allowed to connect via RDP
— Remote Desktop stopped working after Windows update
— The feature won’t connect over the internet
While using this Remote Desktop feature on Windows 10, you might encounter a “logon attempt failed” error as shown in the figure above. The following are the various user IDs I tried and none of them was successful “user@domain.com”.
– Note: This does not relate to the Password issues: The password is correct and existing authentication via RDP was possible.
If you are able to ping the server, and the following below are correct, then the issue is half solved. Verify the following settings
– Check if RDP is enabled and allowed on your firewall as this can be easily overwritten by mistake or broken by Windows Update.
– Temporarily disable your Anti-Virus agent to test for possible issues. If everything is fine, then RDP should work. This means you do not have PC or Domain related issues.
Other recommendations
1: Instead of just copying and pasting the password, simply type the password
2: Also check for allowed programs Allow an app or feature through Windows Firewall
Screenshot 2020 11 09 at 11.25.03
3: Check if the “RDP service” is running on the server as shown below
Screenshot 2020 11 09 at 11.26.54
4: Other checks you may want to check.
– For me, it was not necessary to check the GPO enabled for limiting remote desktop and how many can logon at time. You may also have to check this. For more information on GPO, see the following article “Group Policy Object: What is Group Policy Object and how does it work” For other articles I have written on GPO, see the following link.
I hope you found this blog post helpful. If you have any questions, please let me know in the comment session.
The logon attempt failed error while connecting Remote Desktop
In the past, we’ve told you the way to enable or disable the Remote Desktop connection and troubleshoot it when it disconnects frequently. While using this Remote Desktop feature on Windows 11/10, one might encounter a The logon attempt failed error. When you connect the system remotely using another version like Windows 7, it may work perfectly, but with Windows 11/10/8.1, one might get this error.
In order to fix this hitch, we first ensured that Windows Firewall was set to turn off. We also tried to use Remote Desktop Modern App, but it made no difference in the situation. This solution mentioned on a Technet thread suggests a method, which can fix this issue.
The logon attempt failed for Remote Connections
1. Press Windows Key + R combination, type Firewall.cpl in the Run dialog box and hit Enter to open the Windows Firewall.
2. In the above-shown window, click on Allow an app or feature through Windows Firewall, you’ll get the below-shown window. Click Change settings first then in the Allowed apps and features section, scroll down the list to look for Remote Desktop app and put a check mark against it. Click OK.
Reboot the machine; your problem should be fixed. However, if your computer is part of a domain, by default you aren’t still allowed to save your credentials when you connect to a remote computer. Here is how you can get rid of this problem:
3. Moving on, press Windows Key + R combination, type put gpedit.msc in the Run dialog box and hit Enter to open the Local Group Policy Editor.
4. In the left pane, navigate here:
5. Now in the right pane of this location, look for policy setting Allow delegating saved credentials with NTLM-only server authentication and double click on it. Select Enabled and hit Show in the following window:
Click OK; Apply; OK. Close the Group Policy Editor.
So far, we’re done with fixing the issue. All you now need to do is to reboot the machine; your issue should be fixed.
UPDATE: Dakota North adds in the comments – TERMSRV/*.* is the correct syntax and it allows all servers.
The logon attempt failed что делать
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I am trying to take remote of Domain B windows 7 machine with local user account which has local administrator right and getting below error.
«Your credentials did not work. The logon attempt’s pt failed.»
I work in Domain A and I am taking remote of Domain B win 7 machines from Domain A windows 7 machine.
I don’t have any trust with Domain B but I have connectivity like I can ping, telnet on RDP port 2239 from Domain A to Domain B win 7 system.
Now I have multiple computers account in one OU in AD.
I can take remote of Domain B win 7 system from 1 or 2 system and cannot take remote from 3 to 4 system.
Answers
I have logged case with MS and got the solution. The solution is given below:
MS has enabled first in local GPO the below setting.
«Network Security: LAN Manager authentication level» : NTLMv2
Then after it, we were able to login of cross domain windows 7 machines with local credentials.
And we have enabled this settings in GPO.
All replies
I have separate domain to which I have 3389 port opened and pinging as well.
Now I can take remote from other machine which are in different OU but i cannot login from other machine which are other OU with other domain machines’s local credentials.
But This is for windows server, I am talking about only windows 7 machines.
I have test user which is added local administrators group of other domain windows 7 machines.
Now I am trying to take remote from my domain windows 7 machines which is one OU and can take remote. And if I move this machine to different OU on which i have linked «generic account autologin policy» then I cannot login from this machine to other domain machine.
Also, I don’t have trust with other domain. Only I have connectivity and 3389 port open to take remote and have other domain local window 7 system credentails.
Ther error message is that «The login attempt failed»
The logon attempt failed что делать
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
We setup an Azure Windows 10 VM for use by a remote contractor. We joined the machine to our Azure AD domain and created credentials for the contractor. Using the contract’s credentials, 2 workstations in our office connect fine via RDP. Using the same exact RDP file, when me or the contractor try to connect from our workstations we get «The logon attempt failed».
We don’t have a local AD. The contractor and I can connect fine via his credentials against the portal. It is only our attempts at connecting via RDP that faile.
We have scoured event logs but can’t find any errors. We have tried turning off «Only allow connections from computers running Remote Desktop with NLA» but it makes no difference.
All replies
We would request you to create a Technical Support Ticket on this, as our engineers would need to work with you on the issue and would also require sensitive information like the subscription and tenant details.
—————————————————————————————————
Do click on «Mark as Answer» on the post that helps you, this can be beneficial to other community members.
We did create a support ticket on this last week. We got one reply which we responded to along with screen shots but have now been waiting 4 days to get another response. I have followed up asking what the status is for 2 days now. Still no response. That is why yesterday I put the request here hoping this forum might be able to help out.
—————————————————————————————————
Do click on «Mark as Answer» on the post that helps you, this can be beneficial to other community members.
I created the ticket under Office365 support as we are trying to connect to our O365 Azure Directory.
We have notified the team to get in touch with you for the same.
I see a lot of posts from 2015 saying that RDP to an AAD joined workstation was not supported yet. Has that changed?
I haven’t found any documentation to suggest that it is supported. There are workarounds that require less secure authentication and editing your RDP file, neither of which are ideal.
—————————————————————————————————
Do click on «Mark as Answer» on the post that helps you, this can be beneficial to other community members.
I have not yet been contacted by support but looking forward to resolving this.
I can confirm the same as regards Windows version; host workstation and client are both running build 1703. Windows 10 Pro (not enterprise).
In my case, I’m trying to connect to a Hyper-V VM in my development lab. I can connect to the VM using Hyper-V Manager but Enhanced Mode fails to connect. There is a key difference between Hyper-V Enhanced Mode and regular RDP:
With RDP I get a credential error. With Hyper-V Enhanced Mode I get a certificate error:
«A certification authority could not be contacted for authentication. If you are using a Remote Desktop Gateway with a smart card, try connecting to the remote computer using a password. For assistance, contact your system administrator or technical support.»
This is a brand new VM and I have not enabled Remote Credential Guard. For testing, I created a new registry DWORD as instructed to enable Remote Credential Guard, but I set the value to «1» instead of «0». This has no effect.
In my case, the client (source) computer is signed on with my Microsoft account and the destination is signed on with my O365 credential. In O365 I do NOT have AAD DS configured. According to that documentation, with Remote Credential Guard disabled it should just work.
I don’t know if any of this is helpful for anyone else, but if my situation shows any similarities to Tim’s then it’s a good bet we found a bug (or at least an «Undocumented feature»).
Additional details:
I do not have an RDS Gateway in this environment.
I do not have on-prem AD in this environment.
Azure AD is not on-perm AD integrated.
Based on the documentation linked above, the local (client) machine must be domain joined to an integrated on-prem AD or to AAD. I might guess that this is because a client that is not part of the domain will not know where to send the authentication request? Maybe? But that only makes sense if Remote Credential Guard is enabled.
The logon attempt failed что делать
Вопрос
I am taking the Windows 8 MCSA and as such would like to setup Winodws 8.1 in a lab environment for study/practice. I have Windows Server 2012 R2 Standard installed on a Server and would like to run Windows 8.1 Enterprise in Hyper-V for the purpose of quick rebuilding. I have installed both OSs successfully however if I attempt to RDP into the VM from my desktop running 8.1 Pro I get the message «Logon attempt failed». Google tells me I need to allow RDP through Windows Firewall but this has not worked and I have even tried disabling Windows Firewall both on the Windows 8.1 VM and Win Server 2012. Curiously, I can RDP into the VM from Windows Server 2012.
Any advice would be appreciated.
Все ответы
In addition, please check the security event log on the Windows 8.1 VM and find if there is any error or failed information.
Please also check the local security policy: «Network security: LAN Manager authentication level» on the Windows 8.1 VM and Windows 8.1 desktop, and make sure these two OS can use the same authentication method, for more detailed information, please refer to this article:
This has not resolved the issue.
I know this might be a bit on the obvious side, and apologies if it is, but have enabled «Remote Access» on the Windows 8/8.1 VM? You do this through the System Properties/Remote of the client VM.
It’s also a good idea to domain join the client VM, in the virtualized environment, and to have your client management machine, the machine you are using to access the virtualized environment, joined to the same virtualized domain environment. Then ensure that you, as an administrator, are a member of the Remote Management Group as well as the Remote Users’ Group, I know there is a bit of replication here but bear with me here; membership of the Domain Administrators Group is normally a default, but check to make sure. Speaking of which, pop your user account into the Administrators Group as well. If you use two separate accounts one in the VM environment and one for your external client management machine, then put both accounts into the groups.
Now you can put yourself as a «Selected» User on the client Windows 8/8.1 VM.
If this doesn’t work or only works partially, then there might be a need to look at the Advanced Firewall Rules, but that’s something that can be tried later.
