Can't remote into a computer because "the remote computer requires Network Authentication"

8

1

I'm trying to remote into one Windows 7 computer from another Windows 7 computer, and am getting this error:

The remote computer requires Network Level Authentication, which your computer does not support

Screenshot of error

I believe my computer does support Network Level Authentication, because:

  1. I'm on Windows 7
  2. I have remoted into the target computer from this computer before, with Network Level Authentication required on the target computer
  3. The "About" dialog of mstsc.exe says that it is supported:

Screenshot of About dialog

Has anyone seen this issue before, or know how I can fix it?

Eric

Posted 2012-02-13T22:41:24.710

Reputation: 304

Answers

4

It looks like settings were changed on the remote computer, not yours.

The easiest way to go around this, although not as safe, is to to enable "Allow connections from computer running any version of Remote Desktop (less secure)"

It is found in System Properties Win + Pause/Break -> Advanced system settings -> Remote.

Should you not want to allow login to computers without NLA, let me know and we'll sort it out.

extremko

Posted 2012-02-13T22:41:24.710

Reputation: 428

Any luck with this? – extremko – 2012-03-16T09:24:37.803

It's been more than 2 months now. Care to post results? – extremko – 2012-05-04T12:32:56.400

1I didn't have access to the remote computer, so I had a coworker restart the computer manually. It worked after doing so. – Eric – 2012-06-08T19:03:33.137

P.S., sorry I didn't see your comments. Since they weren't commented on the question I wouldn't see them unless they were addressed to @Eric – Eric – 2012-06-08T19:07:04.817

@Eric thanks for the feedback, and answer mark! Also, I'm glad it was easy to sort out the problem :) – extremko – 2012-06-11T10:59:46.567

2

In my case, it was a problem with a custom RDP file we were using, and also seemed to affect our Windows 10 remote hosts, but not our Windows 7 remote hosts.

The solution was to edit the .RDP file in a text editor and change enablecredsspsupport:i:0 to enablecredsspsupport:i:1 or deleting the line altogether. It didn't seem to matter whether or not requiring Network Level Authentication was enabled on the remote Windows 10 host.

GuitarPicker

Posted 2012-02-13T22:41:24.710

Reputation: 1 137

2

Our problem was caused by a corrupted crypto database catalog:

Solution

  • Stop Cryptographic Services (cryptsvc) by running "net stop cryptsvc".
  • Delete or rename the C:\Windows\System32\catroot2 folder.
  • Start cryptsvc by running "net start cryptsvc".
  • Restart the computer.
  • C:\Windows\System32\catroot2 will be recreated.
  • Wait for all the catalog files from C:\Windows\System32\catroot to be imported into the catroot2 database. This may take up to an hour, so be patient.

Ryker Abel

Posted 2012-02-13T22:41:24.710

Reputation: 121

1Was this on the client side, or on the server side? – Daniel.S – 2017-02-16T02:51:15.510

I followed your steps and its been 20 min now, Cannot see catroot2 folder in System32/. There is total of 45MB of data in C:\Windows\System32\catroot. and how come it will take upto an hour to copy ? – Anum Sheraz – 2018-05-29T14:05:53.253

0

Deleting the computer cert, then requesting a new computer cert fixed the issue for me.

  • MMC
  • Add Snap-In (Certificates, Computer, Local Computer)
  • Certificates -> Personal -> Certificates
  • Right click the cert, All Tasks, Request Certificate with New Key
  • Remove old cert

KERR

Posted 2012-02-13T22:41:24.710

Reputation: 329