In the last week, I suddenly had problems connecting to one of my Server 2008 R2 HyperV virtual machines. I have been using the virtual machine for many months and have not made any changes, but when I attempted to connect using Remote Desktop Connection, I received this error:
"The remote computer requires Network Level Authentication, which your computer does not support."
I knew that the error message related to the Remote Desktop settings on the Server 2008 R2 machine, specifically the "Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)". I have my virtual machines set to use the NLA option, but that hasn't been a problem in the past--I've been connecting to the servers fine from my desktop and laptop.
After further testing, I realized that I only had the problem when I attempted to connect using my laptop. My desktop still connected fine. Both systems run Windows 7, so both should be able to connect with NLA.
After poking around on my laptop, I found this clue in the About menu of the Remote Desktop Connection app on my laptop.
Note the message "Network Level Authentication not supported". On my desktop, it says NLA is supported. So it seems that something changed or broke on my laptop, disabling NLA.
After a few more rounds of searching, I finally came across this TechNet forum thread where user "Millerus" graciously posted the solution that happened to work for me.
The resolution is based on instructions for enabling NLA on Windows XP, which were listed here:
UPDATE: Apparently the URL for the blog post has changed to:
http://blog.powercram.com/2009/07/enabling-network-level-authentication.html
I had previously ignored all Windows XP related information, since I didn't think it would be relevant to Windows 7. But it appears that something removed or modified a registry entry, disabling NLA on my laptop.
In my case, when I checked the HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\Control\SecurityProviders key in my registry, it was missing the credssp.dll file in the list. Once I added that DLL to the security providers list, my Remote Desktop Connection app suddenly showed that NLA was supported. I did not have to reboot my laptop--I just had to close and restart the Remote Desktop Connection app.
Finally. Another hour wasted on some trivial issue. Now back to work...
Steve Endow is a Dynamics GP Certified Trainer and Dynamics
GP Certified IT Professional in Los Angeles. He is also the owner of
Precipio Services, which provides Dynamics GP integrations, customizations, and
automation solutions.
9 comments:
You totally rock, dude. I was having the exact same problem with RDP on Win7. The SEO on your post enabled me to find it right away, and your solution fixed the problem within moments. Thanks a lot for you post!
You know it's people like you who make it easier for people like me. Many, many thanks for taking the time to relay your experience and the solution. Also the fact that you "wasted an hour" certainly makes me feel a bit better about all the HOURS I have wasted in similar trivial "stuff"...we just can't know it all, can we...
Thank you for the clear steps...fixed my problem...Much appreciated!
Worked like a charm on Windows 7, thanks a lot.
I had the same problem, think it was because my laptop was originally XP but upgraded to windows 7, all fixed now many thanks
unfortunately does not work for windows 10. I am suddenly getting this error in windows 10. everything worked fine until last week. now this. tried your fix. no good. there are no files at all in that registry setting. I added this like you posted. no good. will keep hunting.
this did not work for me but I am using windows 10. anyone see this in 10 yet? RDP worked fine until last week. not sure what broke.
Thanks for information.
This URL was not working:
The resolution is based on instructions for enabling NLA on Windows XP, which were listed here:
http://www.powercram.com/2009/07/enabling-network-level-authentication.html#
Good updated URL is:
http://blog.powercram.com/2009/07/enabling-network-level-authentication.html
Post a Comment