jords91

Just in case anyone is wondering how to remedy this situation, i fixed it by using the following. The following three steps is what I did to achieve the above: 1) Set the following key in the registry (as the OP did): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc\Parameters\Internet > EnableActiveProbing set to: 0 Note: It is unclear to me if this key is specifically for Vista, or if it also applies to Win7 - but I set it in any event. 2) Edited GPO (gpedit.msc for a local machine or gpmc.msc if AD domain wide): Computer Configuration > Administrative Templates > System > Internet Communication Management > Turn off Windows Network Connectivity Status Indicator active tests set to: ENABLE 3) Edited a second GPO: Computer Configuration > Policies > Administrative Templates > Network Connections > Do Not show the “local access only” network icon” set to: ENABLE I only really needed to do step one to get the machines connecting before login.

Hmmmm, the machine has all certificates. When i try to connect at login screen, no matter what username and password combination i try, they are incorrect. When i check the NPS server, the logs say the machine authentication is a Audit Success but doesnt stay connected, when i click connect NPS says it was an Audit Failure.

NPS logs show the exact same events as a 1703 device that is working. It is something that has changed in 1709.

Thanks for the reply. Our problem only started when we moved to Win 10 1709. We have been running on 1703 now for the last 5 months without a problem. Im testing with 1709 and laptops will not machine authenticate. It connects for a second but then disconnects. When you try to connect to the network at the login screen it says that the username and password are wrong.

Hi Mark, Just wondering if you had any luck with working this out? We are having the same issue but we are running server 2016 for our NPS. Thanks