WIndows 7 Workstations not authenticating

Tim OBrien
Tim OBrien used Ask the Experts™
Our Windows 7 workstations are not authentication wirelessly. When we ask users to hardwire in they connect fine.
Windows 8 and Windows 10 are fine.

My teammate confirm certificate is not expired and from what we were told by another group no changes were made to Group Policies for WIndows 7 OU

Please see logs I am seeing on Windows 7 PC
Skipping: Eap method DLL path validation failed. Error: typeId=25, authorId=9, vendorId=0, vendorType=0
Skipping: Eap method DLL path validation failed. Error: typeId=17, authorId=9, vendorId=0, vendorType=0
Skipping: Eap method DLL path validation failed. Error: typeId=43, authorId=9, vendorId=0, vendorType=0

On the Raduis Server

Client Machine:
      Security ID:                  NULL SID
      Account Name:                  -
      Fully Qualified Account Name:      -
      OS-Version:                  -
      Called Station Identifier:            8A-15-14-8C-60-B0: test_wireless
      Calling Station Identifier:            18-5E-0F-A6-5C-A2

      NAS IPv4 Address:  
      NAS IPv6 Address:            -
      NAS Identifier:                  -
      NAS Port-Type:                  Wireless - IEEE 802.11
      NAS Port:                  5

RADIUS Client:
      Client Friendly Name:  
      Client IP Address:        

Authentication Details:
      Connection Request Policy Name:      Use Windows authentication for all users
      Network Policy Name:            wireless
      Authentication Provider:            Windows
      Authentication Server:  
      Authentication Type:            PEAP
      EAP Type:                  -
      Account Session Identifier:            34323537373032463445343838424242
      Logging Results:                  Accounting information was written to the local log file.
      Reason Code:                  16
      Reason:                        Authentication failed due to a user credentials mismatch. Either the user name provided does not map to an existing user account or the password was incorrect.
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2016

are you using PEAP or chap
The 'validate server certificate' checkbox is honored by Windows 8 and newer but not necessarily by Windows 7. If the subject name of the certificate that the NPS server is using is blank then Windows 7 will throw these errors while Windows 8 and newer  connects happily. The fix was to use the RAS and IAS Server template in Certificate authority per this article.
JohnBusiness Consultant (Owner)
Most Valuable Expert 2012
Expert of the Year 2018

Look at answer 6 below

Delay domain login until network has started.  

Windows 8 and 10 are usually faster to get connected.
Tim OBrienSystems Engineer


We are using PEAP

The Group Policy states that this setting  is ignored on server 2008 and above (see attached), our NPS is Server 2012R2, I don't believe this relates to a login delay.  There is something about the certificate and passing the login credentials of the user which "something" doesn't like.
I don't know the order of the authentication steps so unclear of where in the process it is having the problem. Strange the error started on Monday as everything was working fine for years.
Tim OBrienSystems Engineer


Problem is now resolved, not sure what we did to fix it. Rebooted both the Domain Controller and NPS and problem solved. Thanks guys for your help!
Systems Engineer
Rebooted DC and NPS, not sure exactly I did to fix problem.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial