Comment 10 for bug 284211

Revision history for this message
Mitch Anderson (metarx) wrote :

I'm having the same issue.

Connecting to an Aruba Networks AP with WPA2-Enterprise.

I authentication against a Windows 2003 Radius Server, with PEAP and MSCHAPv2

The Error I see in the Windows Log file is:

 Authentication-Type = PEAP
 EAP-Type = <undetermined>
 Reason-Code = 66
 Reason = The user attempted to use an authentication method that is not enabled on the matching remote access policy.

When a valid one looks like:

 Proxy-Policy-Name = Use Windows authentication for all users
 Authentication-Provider = Windows
 Authentication-Server = <undetermined>
 Policy-Name = Aruba Wireless
 Authentication-Type = PEAP
 EAP-Type = Secured password (EAP-MSCHAP v2)

It appears as if network-manager isn't passing the type as MSCHAPv2...

This worked fine yesterday before I upgraded to Intrepid.