Windows 8 and CUWN 7.4.100.6

[Kyle Nielsen]

  We are having many issues with Windows 8 clients comming onto campus this semeseter. Running 7.4.100.6 (also upgraded one WLC to 7.4.110.0) and many Win 8 devices will not connect, some can't even see SSID's. Then if the bring the notebook to a differnt buildings (differnt WLC) it will connect, when others move between buildings it will not connect at either location. The erros just says "cannot connect to this network". I would look to being a driver issue, but its so many differnt vendors/drivers/nics it seems like its something else. I have had a TAC case open for 5 days, to no avail. Does anyone have any ideas or seen something like this before? When i run client debugs I only see this:

apfMsConnTask_1: Aug 27 13:29:51.487: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_1: Aug 27 13:29:51.792: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_1: Aug 27 13:29:52.479: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_3: Aug 27 13:29:53.612: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_1: Aug 27 13:29:53.971: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_1: Aug 27 13:29:54.269: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_1: Aug 27 13:29:54.964: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_3: Aug 27 13:29:56.153: Association request from the P2P Client Process P2P Ie and Upadte CB

apfMsConnTask_1: Aug 27 13:29:51.487: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_1: Aug 27 13:29:51.792: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_1: Aug 27 13:29:52.479: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_3: Aug 27 13:29:53.612: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_1: Aug 27 13:29:53.971: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_1: Aug 27 13:29:54.269: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_1: Aug 27 13:29:54.964: Association request from the P2P Client Process P2P Ie and Upadte CB

*apfMsConnTask_3: Aug 27 13:29:56.153: Association request from the P2P Client Process P2P Ie and Upadte CB

[Shaoqin Li]

this log is cosmetic.

if can't connect , you may need debug client to further check

Sent from Cisco Technical Support iPad App

[Chris Murray]

We are having the same problem too. We are also running 7.4.100.0 and have many Windows 8 clients that cannot connect or have trouble connecting.

When you try to debug the MAC Address, and all you see is the following scrolling non-stop:

*apfMsConnTask_1: Sep 19 20:13:09.801: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.801: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.801: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.801: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.802: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.802: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.802: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.802: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.802: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.802: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.812: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.847: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.847: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.848: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.848: Stats update: Non Zero value

*apfMsConnTask_1: Sep 19 20:13:09.851: Stats update: Non Zero value

[Kyle Nielsen]

Hi Chris,

Are you using WPA2/Enterprise?

[Chris Murray]

Yes. I know some clients tried WPA as a workaround an had success but for others WPA2 Enterprise and WPA is problematic.

Chris Murray

[Leo Laohoo]

*apfMsConnTask_1: Sep 19 20:13:09.851: Stats update: Non Zero value

Chris,

These debug messages means nothing.  It basically means the controller is waiting.  Post the output to the command "debug client " and get the client to try to log in.

If it still can't log in, then create an SSID with open authentication.

Make sure your wireless NIC drivers are kept up to date.  We've been observing a lot issues caused by outdated drivers.

[Chris Murray]

THank Leo - this message scrolls so quickly you can't even do anything......I don't think its normal that I have to filter through a million of these just to see the debug I need. Is there a way to turn these messages off?

[Leo Laohoo]

Is there a way to turn these messages off?

Log off and log back on.

Enable your connection to log session.

[stamper.brian]

Chris, I believe what Leo was requesting was for you to use the "debug client " and capture the output of this to a text file to post here.  Using Putty or whatever SSH/Telnet client you use you sould be able to have it capture the output to a file.  There will be a lot of text and it will be impossible to read as its scrolling.  The client is relentless and will continue to try to connect thus all of the output. Once you've posted that here many who also fight these issues will be able to take a look.

[Kyle Nielsen]

Chris, in your  post did you run the debut client as that is the debug that I was running also to obtain the output that I had posted.

For us the issue ended up being with the ISE Authentication servers, we had recetly upgraded to 1.1.3.124 and there is now an EAP session limit of 4,500 (per TAC). So we were having too many EAP session on each PSN node, moving the PSN's behind an F5 seemed to fix the issue (students then had to right-click the SSID and select forget this network, then re-connect and they all worked fine).

Also, last spring we had some issues with older laptopt that were upgraded to Win 8 that would not connect if the SSID had "Protected Management Frames" (under the Security-Layer 2 Tab) set to "Optional". I had to change it to Disabled, to get them connecting.