ExtremeWireless (WiNG)

  • 1.  Microsoft RADIUS and AAA Authentication 802.1x EAP

    Posted 10-25-2021 13:07
    Is it possible to make it work together?
    I have RFS6000 and some APs and want to setup EAP authentication over Microsoft RADIUS server (AD Domain).
    AAA policy on RFS pointing to radius server, WiFi SSID with this AAA policy and EAP authentication - the connection to server is successfull, but request is always rejectedbecause of "the client could not be authenticated because the eap type cannot be processed by the server".
    On radius server, in network policy, EAP-MSchapv2 is chosen as authentication method. Access to WLAN is based on AD user-group.


  • 2.  RE: Microsoft RADIUS and AAA Authentication 802.1x EAP

    Posted 10-26-2021 03:46
    EAP is between the client and the authentication server. So if the server says 'because the eap type cannot be processed', you have to check the settings on your wlan client. MSCHAPv2 is the inner authentication, what do you use as outer EAP method? PEAP? This must be the same and supported on both server and client.  


  • 3.  RE: Microsoft RADIUS and AAA Authentication 802.1x EAP

    Posted 10-26-2021 09:14

    Good Afternoon,

    The following articles relates to wing side configuration

    https://extremeportal.force.com/ExtrArticleDetail?an=000082131

     

    on the Radius server network policy try  authentication method  "Microsoft Protected EAP (EAP) " together with -less secure authentication methods-   "ms-chap-v2",  

     

    Regards

     

     

    Dimitri Corzano

    Technical Support Engineer

    dcorzano@extremenetworks.com

    Office / 1800-872-8440

    ExtremeNetworks.com

    Advance With Us™

    ~*~

     

     






  • 4.  RE: Microsoft RADIUS and AAA Authentication 802.1x EAP

    Posted 10-27-2021 02:38
    Thanks all.
    Problem solved. Just recreated all the rules from scratch in wizard on Radius server, as did in first time, but this time everything works.
    Can't understand what was wrong in first.... but now it works!