The client could not be authenticated because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server

I have 1 Windows 7 client on a LAN that is unable to connect to Wi-Fi using a Windows server 2008 IAS authentication. All other clients can connect. This is a new laptop which has been added to the domain. The connection was working properly before. Its also had a user profile transferred to it from a previous laptop. Whenever I attempt to connect this client to Wi-Fi the server logs the following error.

I tested this authentication with multiple users and against two IAS servers which are authenticating clients successfully.

Please let me know any suggestions.

Event Type:      Warning
Event Source:      IAS
Event Category:      None
Event ID:      2
Date:            9/10/2013
Time:            1:36:43 PM
User:            N/A
Computer:      PMAPRINT
User PMA\jmzann was denied access.
 Fully-Qualified-User-Name = pma.domain/Ann Arbor Office/Ann Arbor Users/John Zann
 NAS-IP-Address =
 NAS-Identifier = <not present>
 Called-Station-Identifier = 64-AE-0C-EB-A9-D0:p1451
 Calling-Station-Identifier = 84-3A-4B-CD-86-E0
 Client-Friendly-Name = AA-WAP1
 Client-IP-Address =
 NAS-Port-Type = Wireless - IEEE 802.11
 NAS-Port = 0
 Proxy-Policy-Name = Use Windows authentication for all users
 Authentication-Provider = Windows
 Authentication-Server = <undetermined>
 Policy-Name = AA Wireless
 Authentication-Type = EAP
 EAP-Type = <undetermined>
 Reason-Code = 22
 Reason = The client could not be authenticated  because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server.

For more information, see Help and Support Center at
0000: 00 00 00 00               ....
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

uncheck the box specifying using EAP to connect in the network connection properties
rpeterslllAuthor Commented:
I only have MS-CHAP v2 selected under authentication and under EAP Methods I have Protected EAP (PEAP) listed. There isn't a check box to de-select to no use EAP.

Also, every client is authenticating properly. I don't believe the problem resides on the server but only on this 1 client that wont authenticate.
Jackie ManCommented:
The info below will be helpful for you.

According to DRSLT, it says:-

"the hotfix did not fix it, but the method 3 on that kb article did fix it..  

Click Start, click Run, type regedit, and then click OK.
Locate and then click the following registry subkey:
On the Edit menu, point to New, and then click DWORD Value.
Type SendTrustedIssuerList, and then press ENTER to name the registry entry.
Right-click SendTrustedIssuerList, and then click Modify.
In the Value data box, type 0 if that value is not already displayed, and then click OK.
Exit Registry Editor."


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rpeterslllAuthor Commented:
Thanks. I will try this and report back if it worked.
I've requested that this question be deleted for the following reason:

Not enough information to confirm an answer.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.