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

  • Question

  • wireless authentication not working 

    I found the following in the radius

    Log Name:      Security
    Source:        Microsoft-Windows-Security-Auditing
    Date:          1/15/2014 2:07:57 AM
    Event ID:      6273
    Task Category: Network Policy Server
    Level:         Information
    Keywords:      Audit Failure
    User:          N/A
    Computer:     NAP01.test.local
    Description:
    Network Policy Server denied access to a user.

    Contact the Network Policy Server administrator for more information.

    User:
     Security ID:   doamin \user.a
     Account Name:   user.a


    Client Machine:
     Security ID:   NULL SID
     Account Name:   -
     Fully Qualified Account Name: -
     OS-Version:   -
     Called Station Identifier:  00-0F-7D-C4-45-20:staff
     Calling Station Identifier:  0C-74-C2-EF-Dd-0B

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

    RADIUS Client:
     Client Friendly Name:  wcont1
     Client IP Address:   192.168.9.10

    Authentication Details:
     Connection Request Policy Name: Wireless
     Network Policy Name:  wism
     Authentication Provider:  Windows
     Authentication Server:  NAP01.test.local
     Authentication Type:  EAP
     EAP Type:   -
     Account Session Identifier:  -
     Logging Results:   Accounting information was written to the local log file.
     Reason Code:   22
     Reason:    The client could not be authenticated  because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server.

    Please help


    • Edited by supportsib Wednesday, January 15, 2014 11:28 AM
    Wednesday, January 15, 2014 11:28 AM

Answers

  • You receive this message when there is an incompatibility in authentication between the client and server.

    check the authentication protocol on the client and verify if its the same as the authentication protocol configured in your network policy.


    Johan Loos

    • Marked as answer by Susie Long Monday, January 27, 2014 1:30 AM
    Wednesday, January 15, 2014 12:58 PM

All replies

  • You receive this message when there is an incompatibility in authentication between the client and server.

    check the authentication protocol on the client and verify if its the same as the authentication protocol configured in your network policy.


    Johan Loos

    • Marked as answer by Susie Long Monday, January 27, 2014 1:30 AM
    Wednesday, January 15, 2014 12:58 PM
  • Hi,

    Anything updates?

    In addition, this issue may also because your client didn't have CA certificate of your domain. Please make sure that your client has CA certificate.

    Besides, the error "The client could not be authenticated because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server" may be due to that the default maximum transmission unit that NPS uses for EAP payloads is 1500 bytes. You can lower the maximum size that NPS uses for EAP payloads by adjusting the Framed-MTU attribute in a network policy to a value no greater than 1344:

    Configure the EAP Payload Size

    Best regards,

    Susie



    • Proposed as answer by Susie Long Monday, January 27, 2014 1:30 AM
    • Edited by Susie Long Tuesday, February 24, 2015 7:27 AM
    Wednesday, January 22, 2014 5:31 AM
  • How do I check the auth protocol on the client and server?

    Many thanks

    Wednesday, January 7, 2015 4:36 PM
  • Did you manage to fix this issue? Would love to know how? :)
    Wednesday, January 7, 2015 4:37 PM