Share via

Win10 RDP issue - Your credentials did not work - The logon attempt failed

Question

Tuesday, January 8, 2019 3:23 AM

I want to use one win10 laptop to connect one 2012 R2 server via RDP but always failed and get the error: Your credentials did not work - The logon attempt failed. After trying day and night, I give it up. Hope somebody could help me with this issue, thanks!

  1. Source machine: Win10 Pro, 1709, a working laptop with corporate image installed; Destination machine: Windows Server 2012 R2, client's jumping server with public access, the default RDP port 3389 is changed for safe purpose
  2. I can see the authentication window, but failed to logon with the error "Your credentials did not work - The logon attempt failed" (sorry I'm not allowed to paste picture here...)
  3. the username and password input is absolutely correct
  4. both [email protected] and domain\username have been tried, both return the error "Your credentials did not work - The logon attempt failed"
  5. i didn't choose Remember me, so nothing matters with those GPOs about save credentials
  6. all related services are started, else I won't be able to see the authentication window
  7. to prevent corporate firewall impact, I also tested with non-corporate network, both failed
  8. the laptop was added into corporate domain before, to prevent any impact from GPO, the laptop now left the domain (checked with gpresult/r, no applied GPO), both failed
  9. turned off windows firewall and tried again, failed
  10. checked in gpedit.msc, Network Security: LAN Manager authentication level setting was Send LM & NTLM – use NTLMv2 session security if negotiated
  11. uninstall anti-virus software and tried, failed
  12. uninstall all Microsoft Windows update/security update and tried, failed
  13. tested with my own laptop (Win10 home edition, 1803) at home, I can successfully logon the destination server...
  14. briefly, i think the difference between my own working laptop and my issued corporate laptop is Windows version...

Any suggestions? Thanks in advance!

All replies (9)

Tuesday, January 8, 2019 4:58 AM

Hello,

See if this fix helps you:

https://www.kapilarya.com/fix-your-credentials-did-not-work-for-remote-desktop-connection-windows-10

Let us know if this helps!

Microsoft MVP (Windows and Devices for IT)

Windows Insider MVP

Windows Help & Support [www.kapilarya.com]

Tuesday, January 8, 2019 9:42 AM

Hello,

See if this fix helps you:

https://www.kapilarya.com/fix-your-credentials-did-not-work-for-remote-desktop-connection-windows-10

Let us know if this helps!

Microsoft MVP (Windows and Devices for IT)

Windows Insider MVP

Windows Help & Support

Hi Kapil,

for FIX1, the previous security setting was Send LM & NTLM – use NTLMv2 session security if negotiated.

for FIX2, it did not work..

but thank you all the same for your reply~

Wednesday, January 9, 2019 7:57 AM

hi,
0 could the problematical win10 1709 rdp to server 2012r2 before?

we can try to do these steps on win10 1709 .
1.Click Start, click Run, type regedit in the Open box, and then click OK. Then backup the full regsitry.
2.Locate and then click the following subkey and set the LmCompatibilityLevel to 1.Finally ,reboot your system and chekc the result.
HKLM\SYSTEM\CurrentControlSet\Control\Lsa
 LmCompatibilityLevel
 REG_DWORD
 Value:1

3 if ther problem persist ,we can try to fix system
 Open 'Windows Powershell' or 'Command Prompt' with Admin privileges (right click -> Run as Administrator)
4 Let's check the System Health first, by running these commands:
  3.1 dism /online /cleanup-image /scanhealth
  3.2 dism /online /cleanup-image /checkhealth
  3.3 dism /online /cleanup-image /restorehealth
5 run sfc /scannow
6 reboot the system to check the result .

Network security: LAN Manager authentication level
https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-security-lan-manager-authentication-level

ARCHIVED: What is the LAN Manager Authentication Level setting?
https://kb.iu.edu/d/atvn

Please Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Tuesday, January 22, 2019 9:22 AM

hi,
0 could the problematical win10 1709 rdp to server 2012r2 before?

we can try to do these steps on win10 1709 .
1.Click Start, click Run, type regedit in the Open box, and then click OK. Then backup the full regsitry.
2.Locate and then click the following subkey and set the LmCompatibilityLevel to 1.Finally ,reboot your system and chekc the result.
HKLM\SYSTEM\CurrentControlSet\Control\Lsa
 LmCompatibilityLevel
 REG_DWORD
 Value:1

3 if ther problem persist ,we can try to fix system
 Open 'Windows Powershell' or 'Command Prompt' with Admin privileges (right click -> Run as Administrator)
4 Let's check the System Health first, by running these commands:
  3.1 dism /online /cleanup-image /scanhealth
  3.2 dism /online /cleanup-image /checkhealth
  3.3 dism /online /cleanup-image /restorehealth
5 run sfc /scannow
6 reboot the system to check the result .

Network security: LAN Manager authentication level
https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-security-lan-manager-authentication-level

ARCHIVED: What is the LAN Manager Authentication Level setting?
https://kb.iu.edu/d/atvn

Please Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Hi Andy,

thanks for your advice and sorry for late reply as I was busy these days..

1, on our corporate laptops, the value for LmCompatibilityLevel is 1 by default..

2, according to your guidance, I have fix system and rebooted the machine, still the same error. below is the cmd log FYI

Microsoft Windows [Version 10.0.17134.285]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\Windows\System32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.285

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\Windows\System32>dism /online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.285

No component store corruption detected.
The operation completed successfully.

C:\Windows\System32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.285

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\System32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\System32>

Tuesday, January 22, 2019 9:56 AM | 2 votes

thanks Kapil and Andy for your reply. this issue has been resolved now.

tried on a test laptop leave corporate domain, changed NTML level piece by piece in local policy, below 3 options did work

  1. Send NTLMv2 response      only
  2. Send NTLMv2 response      only. Refuse LM
  3. Send NTLMv2 response      only. Refuse LM & NTLM

guess the issue was caused by client's DMZ policy settings.

Wednesday, January 23, 2019 6:46 AM

Glad the issue is resolved, thanks for update :)

Good day!

Microsoft MVP (Windows and Devices for IT)

Windows Insider MVP

Windows Help & Support [www.kapilarya.com]

Tuesday, January 29, 2019 3:50 AM

You are welcome!

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Monday, March 18, 2019 6:43 PM

Yu, what was the fix? You didn't mention the steps you used to finally fix it.  I am having the same issue and would like to know :-)

Monday, February 3, 2020 3:44 AM

steps:

Local Group Policy Editor -> Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> Network security: LAN Manager authentication level -> change the security settings as Yu suggested.