- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good day. We have updated wireless NIC drivers to fix and issue where clients could not authenticate at all to the wireless network . But now we are having an issue where clients take a long time to authenticated wit 802.1X and EAP-TLS to network with less and 100ms latency between RADIUS server and client. The clients wireless NIC are all Intel. Client will not respond to the WLC/AP that is sending the EAP-START.WLC/AP is sending EAP-Identity-Request to the client.
Clients will go into a loop of authenticating but eventually three to four minutes in will connect. It is a common occurence and extremely hard to troubleshoot. Debugs show the traffic and it stops at the WLC/AP ..this is a Cisco implementation.
Feb 09 09:25:00.891 | *apfMsConnTask_7 | Client made new Association to AP/BSSID BSSID |
Feb 09 09:25:00.891 | *apfMsConnTask_7 | The WLC/AP has found from client association request Information Element that claims PMKID Caching support |
Feb 09 09:25:00.891 | *apfMsConnTask_7 | The Reassociation Request from the client comes with 0 PMKID |
Feb 09 09:25:00.892 | *apfMsConnTask_7 | Client is entering the 802.1x or PSK Authentication state |
Feb 09 09:25:00.892 | *apfMsConnTask_7 | WLC/AP is sending an Association Response to the client with status code 0 = Successful association |
Feb 09 09:25:00.959 | *Dot1x_NW_MsgTask_2 | WLC/AP is sending EAP-Identity-Request to the client |
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @compughter
Thank you for posting on the Intel® communities.
In order to review this further, could you please provide us with the following information?
1- Just to make sure we understand correctly, is the issue only "slow authentication without failing the connection"?
Or when you say "slow authentication" and "Clients will go into a loop" do you mean the authentication fails a couple of tries until it successfully authenticates?
2- Is this occurring with a particular Intel® Wireless card model or with different models? Also, could you please confirm the driver version(s) affected by this behavior?
3- How many systems (clients) are affected by this behavior? Is this occurring on different computer models or with specific models? Please provide details and maker and models of the computers:
4- Are the wireless cards the original ones that came pre-install on the systems? Or did you integrate/replace them on the computers?
5- Run the Intel® System Support Utility (Intel® SSU) to gather more details about the systems:
- Download the Intel® SSU and save the application on your computer
- Open the application, check the "Everything" checkbox, and click "Scan" to see the system and device information. The Intel® SSU defaults to the "Summary View" on the output screen following the scan. Click the menu where it says "Summary" to change to "Detailed View".
- To save your scan, click Next and click Save.
- Once you have saved the file (.txt file), please attach it to your reply.
To upload and attach a file, use the "Drag and drop here or browse files to attach" option below the response textbox.
Best regards,
Andrew G.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello compughter
We are checking this thread and we would like to know if you need further assistance. Please do not hesitate to contact us back if you have additional inquiries.
Best regards,
Andrew G.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello compughter
We have not heard back from you so we will proceed to close this thread now. If you need any additional information, please submit a new question as this thread will no longer be monitored.
Best regards,
Andrew G.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes please : you can close it out. We are trying other things ie updating the Cisco Anyconnect supplicant - as well as Intel drivers .
![](/skins/images/45C6C2D737ED71F4C51F0145C8CB1E9C/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page