I think it's high time we start splitting off our dual band SSID's and move towards 5 GHz only, and this is another reason to do so. I appreciate you taking the time to come back here and post this, as I never got any traction anywhere else. 1 Helpful Reply Rich R...
We haven't applied any service packs or anything other than just upgrading the controller (then subsequently the AP's) to whatever the default service pack would be for controller code 17.12.1. Leo Laohoo Hall of Fame In response tot3rebello ...
Your reason code is 23. Unfortunately this reason code is associated with a few different kinds of problems, but let’s start by trying to get the correct certificate on your NPS server (the Computer certificate) and editing the PEAP settings so that this certificate is used for authentication...
###RX,packet type ==0x00 eapol-packet, code=Request/type=0x5a(PEAP_90), type data = 明文 “服务器”->“客户”:你好,我是服务器,这里是数字证书的内容(包含公钥),请查收。 ###TX,packet type ==0x00 eapol-packet, code=Response/type=0x5a(PEAP_90), type data=0x00 “客户”->“服务...
It looks like the reason code 0 is stating that there was IAS_Success? Does that mean it passed authentication? But then we are getting an Access Chalenge (Code 11). I found this article on Access Challenge: l4.4. Access-Challenge
The main reason is that the aperture of the working platform is different, the 16 series is 16mm, and the 28 series is a straight hole of 28mm. The 16 series is mainly used in the welding and assembly of smaller workpieces; the 28 series is mainly used in the w...
What code are you running by the way. I know it didn't work with the 6.x but did work with 4.2. I can test it out on the 7.0.x code. Sent from Cisco Technical Support iPhone App -Scott*** Please rate helpful posts *** 0 Helpful Reply Chandra Sinnarajah Level 1 In ...
Turning off the 2.4 GHz on our production SSID was coincidentally a topic of discussion for other purposes. I think it's high time we start splitting off our dual band SSID's and move towards 5 GHz only, and this is another reason to do so. ...
MSCHAPv2. I am having that issue when i use a local CA the clients can authenticate but as soon as i use a third party certificate from Godaddy i get the reason code 22. It's not reading the EAP types. It's just reading my windows logon and not taking the Active Directory user ...
It looks like the reason code 0 is stating that there was IAS_Success? Does that mean it passed authentication? But then we are getting an Access Chalenge (Code 11). I found this article on Access Challenge: l4.4. Access-Challenge