Buy or Renew
Buy or Renew
Duo Security forums now LIVE! Get answers to all your Duo Security questions. Learn more
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2522
Views
5
Helpful
7
Replies

PEAP Authentication Failure using NAM to NPS server

Go to solution
Shubham Bharti
Cisco Employee
Cisco Employee

‎12-04-2018 11:22 AM - edited ‎02-21-2020 09:31 PM

We are working to deploy NAM to endpoints. During the test, we are facing issue with wireless connection when NAM authenticates against NPS. The current deployment involves both ISE and NPS as radius server at various location and customer is looking to move seamlessly between the two servers.

 

Setup that needs to be deployed:

NAM Endpoint----> Cisco WLC------>NPS-----> AD - Failure(PEAP)

NAM Endpoint----> Cisco WLC------>ISE-----> AD - Success - EAP-FAST(EAP-TLS/MSCHAPv2)

 

Current Setup(it works with the Native supplicant in opposite order):

Native supplicant----> Cisco WLC------>NPS-----> AD - Success(PEAP)

Native supplicant----> Cisco WLC------>ISE-----> AD - Failure(PEAP)

 

Any help will be highly appreciated.

Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
stsargen
Cisco Employee
Cisco Employee

‎12-04-2018 11:47 AM

Make sure on the NPS server that your policy does NOT have the "Enforce Network Access Protection" (NAP) enabled.  This uses EAP Type of 33 which is not supported by NAM.

 

NAP-Enabled.PNG

View solution in original post

7 Replies 7

Go to solution
Surendra
Cisco Employee
Cisco Employee

‎12-04-2018 11:27 AM

What is the error you see in the ISE?
0 Helpful

Go to solution
Shubham Bharti
Cisco Employee
Cisco Employee
In response to Surendra

‎12-04-2018 11:46 AM

When Native supplicant tries to connect to ISE: Authentication failed "5440 Endpoint abandoned EAP session and started new" error.

0 Helpful

Go to solution
stsargen
Cisco Employee
Cisco Employee

‎12-04-2018 11:47 AM

Make sure on the NPS server that your policy does NOT have the "Enforce Network Access Protection" (NAP) enabled.  This uses EAP Type of 33 which is not supported by NAM.

 

NAP-Enabled.PNG

Go to solution
Shubham Bharti
Cisco Employee
Cisco Employee
In response to stsargen

‎12-04-2018 12:11 PM

We even removed all the EAP types and kept only MSCHAPv2 on NPS. Native supplicant passed with default configuration(PEAP) but NAM failed WITH PEAP. 

0 Helpful

Go to solution
stsargen
Cisco Employee
Cisco Employee
In response to Shubham Bharti

‎12-04-2018 12:12 PM

Did you find the Enforce Network Access Protection option in NPS?  If so, uncheck it and retest.

0 Helpful

Go to solution
Shubham Bharti
Cisco Employee
Cisco Employee
In response to stsargen

‎12-04-2018 12:18 PM

Will try it out tomorrow and let you know.

Thanks.

0 Helpful

Go to solution
Shubham Bharti
Cisco Employee
Cisco Employee
In response to stsargen

‎12-04-2018 10:09 PM - edited ‎12-04-2018 10:25 PM

This is Windows 2012R2 and I read that NAP is deprecated since that. I have attached the images for your reference.

The thing that we found out is that they are using just MSCHAPv2/MSCHAP in their rules, they dont have anything as part of Protected EAP type selected. Allowing PEAP fails on some of the clients for native supplicant too. But I do see the same Radius Type 33 in Dart File. I have pasted the snippet below:

 

1080: KIRIT-P: Dec 04 2018 14:50:01.586 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Network ABCCORP-WIFI: AccessStateMachine new state = ACCESS_CONNECTING
1081: KIRIT-P: Dec 04 2018 14:50:01.586 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: ...received EapCredentialRequestEvent.
392: KIRIT-P: Dec 04 2018 14:50:01.586 -0530: %NAMSSO-7-DEBUG_MSG: %[tid=3960]: Tx CP Msg: <?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ssc="http://www.cisco.com/ssc" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"> <SOAP-ENV:Body> <networkStateEvent> <sequenceNumber>32</sequenceNumber> <groupName>Local networks</groupName> <networkName>ABCCORP-WIFI</networkName> <networkState>Authenticating</networkState> <adapterName>Intel(R) Dual Band Wireless-AC 8265</adapterName> <serverVerifiedName></serverVerifiedName> </networkStateEvent> </SOAP-ENV:Body></SOAP-ENV:Envelope>
1082: KIRIT-P: Dec 04 2018 14:50:01.586 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: processing credential request: sync=8, session-id=1, eap-handle=00BF7CB4, eap-level=0, auth-level=0, protected=0, type=CRED_REQ_SESSION_START
393: KIRIT-P: Dec 04 2018 14:50:01.587 -0530: %NAMSSO-7-DEBUG_MSG: %[tid=3960]: leaving cs...
1083: KIRIT-P: Dec 04 2018 14:50:01.587 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Starting new authentication session, last negotiated top EAP method = eapPeap
1084: KIRIT-P: Dec 04 2018 14:50:01.587 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Client certificate list has been cleared
1085: KIRIT-P: Dec 04 2018 14:50:01.587 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Fast reauthentication allowed in profile
1086: KIRIT-P: Dec 04 2018 14:50:01.587 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Disabling fast reauthentication
1087: KIRIT-P: Dec 04 2018 14:50:01.587 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Fast reauthentication disabled for current session
1088: KIRIT-P: Dec 04 2018 14:50:01.593 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: CA certificate store handles set: sync=8
1089: KIRIT-P: Dec 04 2018 14:50:01.593 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: session start sent: sync=8
1090: KIRIT-P: Dec 04 2018 14:50:01.593 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 8: state transition: PENDING -> RESPONDED
1091: KIRIT-P: Dec 04 2018 14:50:01.593 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Authentication state transition: AUTH_STATE_FAILURE -> AUTH_STATE_STARTED
1092: KIRIT-P: Dec 04 2018 14:50:01.593 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Sending NOTIFICATION__AUTHENTICATING to subscribers
1093: KIRIT-P: Dec 04 2018 14:50:01.593 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Network auth request NOTIFICATION__AUTHENTICATING
1094: KIRIT-P: Dec 04 2018 14:50:01.593 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request completed, response sent: sync=8
1095: KIRIT-P: Dec 04 2018 14:50:01.593 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 8: state transition: RESPONDED -> COMPLETED
1096: KIRIT-P: Dec 04 2018 14:50:01.593 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP-CB: credential requested: sync=9, session-id=1, handle=00BF7CB4, type=AC_CRED_IDENTITY
1097: KIRIT-P: Dec 04 2018 14:50:01.600 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP: credential request deferred: sync=9
1098: KIRIT-P: Dec 04 2018 14:50:01.600 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP-CB: sending EapCredentialRequestEvent...
1099: KIRIT-P: Dec 04 2018 14:50:01.600 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: ...received EapCredentialRequestEvent.
1100: KIRIT-P: Dec 04 2018 14:50:01.600 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: processing credential request: sync=9, session-id=1, eap-handle=00BF7CB4, eap-level=0, auth-level=0, protected=0, type=CRED_REQ_IDENTITY
1101: KIRIT-P: Dec 04 2018 14:50:01.600 -0530: %NAM-6-INFO_MSG: %[tid=3696]: EAP: Identity requested
1102: KIRIT-P: Dec 04 2018 14:50:01.600 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Performing full authentication
1103: KIRIT-P: Dec 04 2018 14:50:01.601 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Disabling fast reauthentication
1104: KIRIT-P: Dec 04 2018 14:50:01.601 -0530: %NAM-6-INFO_MSG: %[tid=3696]: Getting credentials from user.
1105: KIRIT-P: Dec 04 2018 14:50:01.603 -0530: %NAM-6-INFO_MSG: %[tid=3696]: Sending unprotected identity = 41000225.
1106: KIRIT-P: Dec 04 2018 14:50:01.603 -0530: %NAM-6-INFO_MSG: %[tid=3696]: EAP: Identity sent
1107: KIRIT-P: Dec 04 2018 14:50:01.603 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: identity sent: sync=9
1108: KIRIT-P: Dec 04 2018 14:50:01.603 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 9: state transition: PENDING -> RESPONDED
1109: KIRIT-P: Dec 04 2018 14:50:01.603 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Authentication state transition: AUTH_STATE_STARTED -> AUTH_STATE_UNPROTECTED_IDENTITY_SENT_FOR_FULL_AUTHENTICATION
1110: KIRIT-P: Dec 04 2018 14:50:01.603 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request completed, response sent: sync=9
1111: KIRIT-P: Dec 04 2018 14:50:01.603 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 9: state transition: RESPONDED -> COMPLETED
1112: KIRIT-P: Dec 04 2018 14:50:01.621 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP-CB: credential requested: sync=10, session-id=1, handle=00BF7CB4, type=AC_CRED_EAP_METHODS
1113: KIRIT-P: Dec 04 2018 14:50:01.622 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP: credential request deferred: sync=10
1114: KIRIT-P: Dec 04 2018 14:50:01.622 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP-CB: sending EapCredentialRequestEvent...
1115: KIRIT-P: Dec 04 2018 14:50:01.622 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: ...received EapCredentialRequestEvent.
1116: KIRIT-P: Dec 04 2018 14:50:01.622 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: processing credential request: sync=10, session-id=1, eap-handle=00BF7CB4, eap-level=0, auth-level=0, protected=0, type=CRED_REQ_EAP_METHODS
1117: KIRIT-P: Dec 04 2018 14:50:01.622 -0530: %NAM-6-INFO_MSG: %[tid=3696]: EAP: EAP suggested by server: eapPeap
1118: KIRIT-P: Dec 04 2018 14:50:01.622 -0530: %NAM-6-INFO_MSG: %[tid=3696]: EAP: EAP requested by client: eapPeap
1119: KIRIT-P: Dec 04 2018 14:50:01.622 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: EAP methods sent: sync=10
1120: KIRIT-P: Dec 04 2018 14:50:01.622 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 10: state transition: PENDING -> RESPONDED
1121: KIRIT-P: Dec 04 2018 14:50:01.622 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Authentication state transition: AUTH_STATE_UNPROTECTED_IDENTITY_SENT_FOR_FULL_AUTHENTICATION -> AUTH_STATE_UNPROTECTED_IDENTITY_ACCEPTED
1122: KIRIT-P: Dec 04 2018 14:50:01.622 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request completed, response sent: sync=10
1123: KIRIT-P: Dec 04 2018 14:50:01.622 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 10: state transition: RESPONDED -> COMPLETED
1124: KIRIT-P: Dec 04 2018 14:50:01.660 -0530: %NAM-6-INFO_MSG: %[tid=3804][comp=SAE]: CERT (0) looking up: "/DC=com/DC=ABC/CN=ABC-AHDMSEXCA-CA"
1125: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP-CB: credential requested: sync=11, session-id=1, handle=00BF7CB4, type=AC_CRED_SERVER_VERIFY
1126: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP: credential request deferred: sync=11
1127: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP-CB: sending EapCredentialRequestEvent...
1128: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: ...received EapCredentialRequestEvent.
1129: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: processing credential request: sync=11, session-id=1, eap-handle=00BF7CB4, eap-level=0, auth-level=0, protected=0, type=CRED_REQ_SERVER_VERIFY
1130: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-6-INFO_MSG: %[tid=3696]: Validating the server: RADIUSSRV.ABC.com
1131: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-6-INFO_MSG: %[tid=3696]: Server certificate validated: RADIUSSRV.ABC.com
1132: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: server verification result sent: sync=11
1133: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 11: state transition: PENDING -> RESPONDED
1134: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request completed, response sent: sync=11
1135: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 11: state transition: RESPONDED -> COMPLETED
1136: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP-CB: credential requested: sync=12, session-id=1, handle=00BF7CB4, type=AC_CRED_USER_CERT
1137: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP: credential request deferred: sync=12
1138: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP-CB: sending EapCredentialRequestEvent...
1139: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: ...received EapCredentialRequestEvent.
1140: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: processing credential request: sync=12, session-id=1, eap-handle=00BF7CB4, eap-level=0, auth-level=0, protected=0, type=CRED_REQ_USER_CERT
1141: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Client certificate doesn't exist
1142: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request completed, response sent: sync=12
1143: KIRIT-P: Dec 04 2018 14:50:01.668 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 12: state transition: PENDING -> COMPLETED
1144: KIRIT-P: Dec 04 2018 14:50:01.734 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP-CB: credential requested: sync=13, session-id=1, handle=00BF7CB4, type=AC_CRED_IDENTITY
1145: KIRIT-P: Dec 04 2018 14:50:01.734 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP: credential request deferred: sync=13
1146: KIRIT-P: Dec 04 2018 14:50:01.734 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP-CB: sending EapCredentialRequestEvent...
1147: KIRIT-P: Dec 04 2018 14:50:01.734 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: ...received EapCredentialRequestEvent.
1148: KIRIT-P: Dec 04 2018 14:50:01.734 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: processing credential request: sync=13, session-id=1, eap-handle=00BF7CB4, eap-level=1, auth-level=1, protected=1, type=CRED_REQ_IDENTITY
1149: KIRIT-P: Dec 04 2018 14:50:01.734 -0530: %NAM-6-INFO_MSG: %[tid=3696]: EAP: Inner Identity/(Username) requested.
1150: KIRIT-P: Dec 04 2018 14:50:01.734 -0530: %NAM-6-INFO_MSG: %[tid=3696]: Protected identity/(Username) sent.
1151: KIRIT-P: Dec 04 2018 14:50:01.734 -0530: %NAM-6-INFO_MSG: %[tid=3696]: EAP: Identity sent
1152: KIRIT-P: Dec 04 2018 14:50:01.751 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: identity sent: sync=13
1153: KIRIT-P: Dec 04 2018 14:50:01.751 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 13: state transition: PENDING -> RESPONDED
1154: KIRIT-P: Dec 04 2018 14:50:01.752 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Authentication state transition: AUTH_STATE_UNPROTECTED_IDENTITY_ACCEPTED -> AUTH_STATE_PROTECTED_IDENTITY_SENT
1155: KIRIT-P: Dec 04 2018 14:50:01.752 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request completed, response sent: sync=13
1156: KIRIT-P: Dec 04 2018 14:50:01.753 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 13: state transition: RESPONDED -> COMPLETED
1157: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP-CB: credential requested: sync=14, session-id=1, handle=00BF7CB4, type=AC_CRED_EAP_METHODS
1158: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP: credential request deferred: sync=14
1159: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-7-DEBUG_MSG: %[tid=3800]: EAP-CB: sending EapCredentialRequestEvent...
1160: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: ...received EapCredentialRequestEvent.
1161: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: processing credential request: sync=14, session-id=1, eap-handle=00BF7CB4, eap-level=1, auth-level=1, protected=1, type=CRED_REQ_EAP_METHODS
1162: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-4-WARNING_MSG: %[tid=3696]: EAP: Extended EAP types not supported. Server specified vendor: 311.
1163: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-4-WARNING_MSG: %[tid=3696]: EAP: Unsupported EAP method type suggested by server: 33
1164: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Authentication state transition: AUTH_STATE_PROTECTED_IDENTITY_SENT -> AUTH_STATE_PROTECTED_IDENTITY_ACCEPTED
1165: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-6-INFO_MSG: %[tid=3696]: EAP: EAP requested by client: eapMschapv2
1166: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: EAP methods sent: sync=14
1167: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 14: state transition: PENDING -> RESPONDED
1168: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request completed, response sent: sync=14
1169: KIRIT-P: Dec 04 2018 14:50:01.803 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: credential request 14: state transition: RESPONDED -> COMPLETED
1170: KIRIT-P: Dec 04 2018 14:50:01.821 -0530: %NAM-7-DEBUG_MSG: %[tid=3804]: EAP-CB: EAP status notification: session-id=1, handle=00BF7CB4, status=AC_EAP_STATUS_INTERMEDIATE_EAP_FAILURE
1171: KIRIT-P: Dec 04 2018 14:50:01.822 -0530: %NAM-7-DEBUG_MSG: %[tid=3804]: EAP-CB: sending EapStatusEvent...
1172: KIRIT-P: Dec 04 2018 14:50:01.822 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: ...received EapStatusEvent: session-id=1, EAP handle=00BF7CB4, status=AC_EAP_STATUS_INTERMEDIATE_EAP_FAILURE
1173: KIRIT-P: Dec 04 2018 14:50:01.822 -0530: %NAM-6-INFO_MSG: %[tid=3696]: EAP: Eap status AC_EAP_STATUS_INTERMEDIATE_EAP_FAILURE.
1174: KIRIT-P: Dec 04 2018 14:50:01.822 -0530: %NAM-6-INFO_MSG: %[tid=3696]: Intermediate EAP failure: No failure message from the server
1175: KIRIT-P: Dec 04 2018 14:50:01.824 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: processing EapStatusEvent in the subscriber
1176: KIRIT-P: Dec 04 2018 14:50:01.824 -0530: %NAM-6-INFO_MSG: %[tid=3696]: Intermediate EAP failure: No failure message from the server
1177: KIRIT-P: Dec 04 2018 14:50:01.839 -0530: %NAM-7-DEBUG_MSG: %[tid=3804]: EAP-CB: EAP status notification: session-id=1, handle=00BF7CB4, status=AC_EAP_STATUS_EAP_FAILURE
1178: KIRIT-P: Dec 04 2018 14:50:01.839 -0530: %NAM-7-DEBUG_MSG: %[tid=3804]: EAP-CB: sending EapStatusEvent...
1179: KIRIT-P: Dec 04 2018 14:50:01.839 -0530: %NAM-7-DEBUG_MSG: %[tid=3804]: EAP-CB: EAP status notification: session-id=1, handle=00BF7CB4, status=AC_EAP_STATUS_ERR_CLIENT_EAP_METHOD_REJECTED
1180: KIRIT-P: Dec 04 2018 14:50:01.839 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: ...received EapStatusEvent: session-id=1, EAP handle=00BF7CB4, status=AC_EAP_STATUS_EAP_FAILURE
1181: KIRIT-P: Dec 04 2018 14:50:01.839 -0530: %NAM-7-DEBUG_MSG: %[tid=3804]: EAP-CB: sending EapStatusEvent...
1182: KIRIT-P: Dec 04 2018 14:50:01.839 -0530: %NAM-6-INFO_MSG: %[tid=3696]: EAP: Eap status AC_EAP_STATUS_EAP_FAILURE.
1183: KIRIT-P: Dec 04 2018 14:50:01.840 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: processing EapStatusEvent in the subscriber
1184: KIRIT-P: Dec 04 2018 14:50:01.840 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Protected identity accepted, authentication failed before credential was sent.
1185: KIRIT-P: Dec 04 2018 14:50:01.840 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Disabling fast reauthentication
1186: KIRIT-P: Dec 04 2018 14:50:01.841 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Authentication state transition: AUTH_STATE_PROTECTED_IDENTITY_ACCEPTED -> AUTH_STATE_FAILURE
1187: KIRIT-P: Dec 04 2018 14:50:01.841 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Sending NOTIFICATION__FAILURE to subscribers
1188: KIRIT-P: Dec 04 2018 14:50:01.841 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Network auth request NOTIFICATION__FAILURE
1189: KIRIT-P: Dec 04 2018 14:50:01.842 -0530: %NAM-6-INFO_MSG: %[tid=3804][mac=1,6,04:d3:b0:f4:a4:a2]: {DBD30713-8887-4EBE-B314-820B39D8CA03}: Port State UNAUTHENTICATED and status EAP_FAILURE
1190: KIRIT-P: Dec 04 2018 14:50:01.843 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Network ABCCORP-WIFI: NetworkStateMachine current state USER_T_NOT_DISCONNECTED, received auth request AUTHENTICATION_FAILED
1191: KIRIT-P: Dec 04 2018 14:50:01.843 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Network ABCCORP-WIFI: NetworkStateMachine new state USER_T_NOT_DISCONNECTED
1192: KIRIT-P: Dec 04 2018 14:50:01.843 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Finishing authentication
1193: KIRIT-P: Dec 04 2018 14:50:01.843 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Authentication finished
1194: KIRIT-P: Dec 04 2018 14:50:01.844 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: ...received EapStatusEvent: session-id=1, EAP handle=00BF7CB4, status=AC_EAP_STATUS_ERR_CLIENT_EAP_METHOD_REJECTED
1195: KIRIT-P: Dec 04 2018 14:50:01.844 -0530: %NAM-6-INFO_MSG: %[tid=3696]: EAP: Eap status AC_EAP_STATUS_ERR_CLIENT_EAP_METHOD_REJECTED.
1196: KIRIT-P: Dec 04 2018 14:50:01.844 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: EAP: processing EapStatusEvent in the subscriber
1197: KIRIT-P: Dec 04 2018 14:50:01.844 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: Auth[ABCCORP-WIFI:user-auth]: Ignoring EAP status AC_EAP_STATUS_ERR_CLIENT_EAP_METHOD_REJECTED
1198: KIRIT-P: Dec 04 2018 14:50:01.844 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: ACE: adapter SM current: state(STATE_AUTHENTICATING), event(EVENT_AUTH_FAIL)
1199: KIRIT-P: Dec 04 2018 14:50:01.844 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: ACE: adapter SM state change: STATE_AUTHENTICATING -> STATE_AUTH_FAILED
1200: KIRIT-P: Dec 04 2018 14:50:01.844 -0530: %NAM-7-DEBUG_MSG: %[tid=3696]: handleEventAndDoStateTransitionAction action : ACTION_AUTH_FAIL
1201: KIRIT-P: Dec 04 2018 14:50:01.844 -0530: %NAM-3-ERROR_MSG: %[tid=3696]: {DBD30713-8887-4EBE-B314-820B39D8CA03}: Authentication Failed

 

 

 

Preview file
50 KB
0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents