locked
Aruba controller authentication on Windows 2012 R2 RADIUS server fails RRS feed

  • Question

  • Aruba support says the configuration of Aruba controller and the Windows server is correct. Yet authentication fails when using MS CHAPv2. I am out of ideas, below is the security log entrees from an authentication attempt.

    An account failed to log on.

    Subject:

                    Security ID:                            SYSTEM

                    Account Name:                     KALE$

                    Account Domain:                  DOMAIN

                    Logon ID:                               0x3E7

    Logon Type:                                          3

    Account For Which Logon Failed:

                    Security ID:                            NULL SID

                    Account Name:                     username

                    Account Domain:                  DOMAIN

    Failure Information:

                    Failure Reason:                      Unknown user name or bad password.

                    Status:                                    0xC000006D

                    Sub Status:                            0xC000006A

    Process Information:

                    Caller Process ID:  0x3ac

                    Caller Process Name:           C:\Windows\System32\svchost.exe

    Network Information:

                    Workstation Name:             

                    Source Network Address:    -

                    Source Port:                          -

    Detailed Authentication Information:

                    Logon Process:                     IAS

                    Authentication Package:     MICROSOFT_AUTHENTICATION_PACKAGE_V1_0

                    Transited Services:                -

                    Package Name (NTLM only):              -

                    Key Length:                           0

    This event is generated when a logon request fails. It is generated on the computer where access was attempted.

    The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

    The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

    The Process Information fields indicate which account and process on the system requested the logon.

    The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

    The authentication information fields provide detailed information about this specific logon request.

                    - Transited services indicate which intermediate services have participated in this logon request.

                    - Package name indicates which sub-protocol was used among the NTLM protocols.

                    - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

    Network Policy Server denied access to a user.

    Contact the Network Policy Server administrator for more information.

    User:

                    Security ID:                                            NULL SID

                    Account Name:                                     username

                    Account Domain:                                  DOMAIN

                    Fully Qualified Account Name:           DOMAIN \ username

    Client Machine:

                    Security ID:                                            NULL SID

                    Account Name:                                     -

                    Fully Qualified Account Name:           -

                    OS-Version:                                           -

                    Called Station Identifier:                      001A1E00F390

                    Calling Station Identifier:                     0.0.0.0

    NAS:

                    NAS IPv4 Address:                                172.19.1.48

                    NAS IPv6 Address:                                -

                    NAS Identifier:                                       Blizzard

                    NAS Port-Type:                                     Wireless - IEEE 802.11

                    NAS Port:                                               0

    RADIUS Client:

                    Client Friendly Name:                          Blizzard

                    Client IP Address:                                 172.19.1.48

    Authentication Details:

                    Connection Request Policy Name:     Secure Wireless Connections new

                    Network Policy Name:                         -

                    Authentication Provider:                     Windows

                    Authentication Server:                         kale.ad. DOMAIN.edu

                    Authentication Type:                            MS-CHAPv2

                    EAP Type:                                               -

                    Account Session Identifier:                 -

                    Logging Results:                                   Accounting information was written to the SQL data store and 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.

    Thursday, August 11, 2016 4:45 PM

Answers

  • Hi,

    Check this for more information about NPS accounting and logging:

    NPS Accounting

    https://technet.microsoft.com/en-us/library/dd197475(v=ws.10).aspx

    NPS Events and Event Viewer

    https://technet.microsoft.com/en-us/library/cc753898(v=ws.10).aspx

    ________________________________________
    Best Regards,
    Cartman
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
    tnmff@microsoft.com.

    Tuesday, August 16, 2016 4:10 AM

All replies

  • Hi,

    >>Aruba support says the configuration of Aruba controller and the Windows server is correct. Yet authentication fails when using MS CHAPv2. I am out of ideas, below is the security log entrees from an authentication attempt.

    Base on my knowledge,if EAP-MSCHAPv2 is used than user can login only with DOMAIN\USERNAME+ PASSWORD.

    If MSCHAPv2  is used than NPS accept only USERNAME + PASSWORD. You could have a test for this.

    ________________________________________
    Best Regards,
    Cartman
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
    tnmff@microsoft.com.

    Friday, August 12, 2016 5:47 AM
  • i have tested for that.

    is there additional loggoing i can turn on?

    Friday, August 12, 2016 6:55 PM
  • Hi,

    Check this for more information about NPS accounting and logging:

    NPS Accounting

    https://technet.microsoft.com/en-us/library/dd197475(v=ws.10).aspx

    NPS Events and Event Viewer

    https://technet.microsoft.com/en-us/library/cc753898(v=ws.10).aspx

    ________________________________________
    Best Regards,
    Cartman
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
    tnmff@microsoft.com.

    Tuesday, August 16, 2016 4:10 AM
  • Hi,

    I am checking to see if the problem has been resolved. If there's anything you'd like to know, don't hesitate to ask.

    ________________________________________
    Best Regards,
    Cartman
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
    tnmff@microsoft.com.

    Tuesday, August 23, 2016 7:46 AM