Windows 10: Network Level Authentication Issue

Ok so here is my situation.


I have 50 Windows 2012 R2 servers which I have permission to remote access.

But when I try to initiate an RDP session to any of them I get the error:


"The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support"


I can connect to the servers using a local admin account and I can uncheck the tickbox"Allow connections from computers running Remote Desktop with Network Level Authentication recommended"


After this I can RDP to the servers with my domain admin account.


However, the trouble is that the setting gets re-enabled for security reasons by our security team and then I am back where I started.


The really weird thing is that the error does not occur for everyone. For example, my colleague and I have the exact same Windows 10 laptops. He does not get an error at any stage, even if the setting is ticked or not.


This leads me to believe there is a setting on my Windows laptop which needs to be changed?

:)

 

How to enable Network Level Authentication for RDP?

Hi K.Kong,

The question that you have is too complex to be answered here in the Microsoft Answers forums. For more information regarding
Remote Desktop Configurations and Windows Servers, I suggest that you post your question on our
TechNet forums instead. I found some posts there that might help you. You can access them in the following links:

RDP issues, remote computers
requires network level authentication

Configure Network Level Authentication for Remote Desktop
Services Connections

Regards.

 

Raising the windows domain and forest issues?


hi,

I run a domain that was all 2003 r2 servers. I recently upgraded all my domain controllers to windows 2012 r2.
That went off without any problems.. Our trust relationships had no issues also.

My first step was to raise the Domain and Forest levels past 2003 to 2008. This went off without a hitch.
These are the features for raising the levels to 2008:

• Features and benefits include all default Active Directory features, all features from the Windows Server 2003 domain functional level, plus:
• Read-Only Domain Controllers – Allows implementation of domain controllers that only host read-only copy of NTDS database.
• Advanced Encryption Services – (AES 128 and 256) support for the Kerberos protocol.
• Distributed File System Replication (DFSR) – Allows SYSVOL to replicate using DFSR instead of older File Replication Service (FRS). It provides more robust and detailed replication of SYSVOL contents.

Forest Level Windows Server 2008

• Features and benefits include all of the features that are available at the Windows Server 2003 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2008 domain functional level by default.

My next step is to raise the domain and forest to 2008 r2, then 2012, and finally 2012 r2. I have been trying to find out exactly what I could expect from raising the Domain and Forest for each step.

The step involving 2008 r2 seems relatively a non issue. But getting the couple of new features seem very nice

Domain Level Windows Server 2008 R2

• All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus 2 new features

Forest Level Windows Server 2008 R2

• All of the features that are available at the Windows Server 2003 forest functional level, plus the following features:

• Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. <== New Feature very cool
• All domains subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default.

Here is my big concerns for the next raising of domain and forest to 2012.

Forest Level Windows Server 2012:

• All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features.
• All domains subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.

Domain Level Windows Server 2012 R2: <=====Need to investigate more and why this post

• DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer:

• Authenticate with NTLM authentication <==============(what issues may arise)
• Use DES or RC4 cipher suites in Kerberos pre-authentication
• Be delegated with unconstrained or constrained delegation
• Renew user tickets (TGTs) beyond the initial 4-hour lifetime

Will this affect my exchange anywhere users with remote access authenticating either clear of NTLM???
and what would/may not to work properly day 1 when I raise the domain and forest to 2012. I cant really find anyone that can answer a straight question.

Has anyone gone through this? what problems did you have, if any , if a lot???

Any thoughts and suggestions will be much appreciated??

thanks


- - - Updated - - -

One more point... I am not sure if I posted this to the correct forum.. So if I was wrong and it should be in a different one..
PLEASE LET ME KNOW

 

Issues with network adapters

Hi Alfonso,

To resolve this issue, we suggest that you run the Network troubleshooter when you switch from WiFi to Ethernet connection. The Network troubleshooter can help diagnose and fix common connection problems including clearing the network cache to obtain a new
IP from the new network. Kindly follow the steps below:

• In the search box on the taskbar, type Identify and repair network problems, and then select
  Identify and repair network problems from the list of results.
• Follow the steps in the troubleshooter and see if that fixes the problem.

If the issue persists, kindly try the troubleshooting steps on the following link:

Fix network connection issues in Windows 10.

We recommend that you try the steps on the Update the network adapter driver,
Run the Network troubleshooter followed by networking commands, and Use network reset to reinstall network devices sections.

Let us know how it goes for us to assist you further.