The logon attempt failed error while connecting Remote Desktop

In the past, we’ve told you the way to enable or disable Remote Desktop connection and troubleshoot it when it disconnects frequently. While using this Remote Desktop feature on Windows 10/8.1, one might encounter a The logon attempt failed error. When you connect the system remotely using another iteration like Windows 7, it may work perfectly, but with Windows 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 differences 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.

GPEDIT Configure & Limit Reservable Bandwidth Setting In Windows 8.1

4. In the left pane, navigate here:

Computer Configuration -> Administrative Templates -> System -> Credentials Delegation


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:


6. Finally, in Show Contents window, put the Value as TERMSRV\Computer Name, where you have to substitute your computer name after TERMSRV\. 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.

Hope this helps.

UPDATE: Dakota North adds in the comments – TERMSRV/*.* is the correct syntax and it allows all servers.

Related read: Your credentials did not work in Remote Desktop.

Posted by on , in Category Windows with Tags
An Electrical Engineer by profession, Kapil is a Microsoft MVP and a Microsoft Content Creator. Please read the entire post & the comments first & create a system restore point before making any changes to your system.


  1. Didn’t work for me, none of it 🙂

  2. wenyibing

    It should be forward slash “/” “TERMSRV/xxxx”

  3. zqsd

    respect bro it worked <3

  4. Owen Genzlinger

    The issue I’m having (not sure if i’m ni the right place for this) but i’m using a wind 8.1 PC to log into a win 10 PC. I can use the ipad app fine though my DDNS, but can’t use my laptop running 8.1

  5. malek hejjeh

    note work : bro

  6. prasaath viki


  7. Yep. Worked for me 🙂

  8. Dakota North

    I know this is old, but the way it works is TERMSRV/*.* is the correct syntax and it allows all servers. bam! easy!

  9. Brennan

    Same for me. I am using my Ipad to connect because it works fine but does not work through any time of computer.

  10. Bas Ganzevles

    err… except my PC cannot find gpedit.msc…

  11. Maybe because its the Home edition…?

  12. Juliet Bell

    Try connecting remotely and login using on premise R-HUB remote support servers. It is easy to use and provides seamless remote desktop experience.

  13. Tim Schoeller

    Try in safe mode.

  14. amunratsi

    Are “*” placeholders or you mean it literally?

Leave a Reply

Your email address will not be published. Required fields are marked *

2 + 5 =