cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
8375
Views
0
Helpful
17
Replies
Vasco Costa
Beginner

Problems with Windows 10 clients when using WLC 8.2.161+AIR-CAP1602

Hi,

 

Anyone with AIR-CAP1602 experiencing problems with laptops running Windows 10?
All other type of wifi clients (smarphones, mac book, even surface with windows 10) use the network without any problem. It's only when they are connected to the 1600 AP, they are branded as being in "RUN" state by the WLC but the laptops don't have connectivity. Once they connect to any different type of APs, they are up an running.

 

2x 2504 with AirOS 8.2.161

They have several APs; 2700, 1700, 1600 and 1140.

-smarphones + all APs= ok
-windows surface with windows 10 + AP 1600 = ok

-windows 8.1 laptop + AP 1600 = ok
-windows 10 laptops + 1600 AP = NOK
-windows 10 laptops + any AP other than 1600 = ok

Regards,
Vasco

Cheers,
Vasco
1 ACCEPTED SOLUTION

Accepted Solutions

Upgrading to 8.2.166 solved the problem.

 

The 1602i are now running with image ap1g2-k9w8-mx.153-3.JC14 and now I have DHCP packets from windows 10 clients arriving to the WLC.

Cheers,
Vasco

View solution in original post

17 REPLIES 17
Scott Fella
Hall of Fame Guru

Have you tried a different code by chance? I ran into issue also with the 3800’s and changing to a different code help fix the issue. Maybe v8.2.151.0
-Scott
*** Please rate helpful posts ***

Hi Scott,

Thanks for the quick reply but we detected the problem in 8.2.151.

Ugraded to 8.2.161 but the problem remains.

 

Haven't tried to downgrade back to 8.0 but I really want to avoid that.

Cheers,

Vasco 

Cheers,
Vasco

Well you did discover that in v8.0 everything worked fine. I guess your only other choice might be v8.3. We don’t run any 1600’s to test with. We are actually running v8.2 MR3 with no issues but on 3702’s.
-Scott
*** Please rate helpful posts ***
Leo Laohoo
VIP Community Legend

Currently using 8.2.141.0 and 3700 with Windows 10. We don't see this issue at all.

Can you please update the firmware of the wireless NIC drivers and see if there are any improvements?

Temporary solved by downgrading a WLC back to 8.0.140.

 

Have a lot of packet capture frames to look at and see if I can "find the fish"

Cheers,
Vasco

What about with 8.3.122? 
This time was in my company's corporate network (2500 w/ 8.3.122 and 3702i).
Some laptops with windows 10 were having performance issues. Not so serious as what I have seen at the customer but again, downgrading to 8.0.140 solved the issue.

Cheers,
Vasco

Odd; I have only DHCP Discover from win10 laptops connected to 1600 with version 8.2.


In any of the other combinations (other clients+1600v8.2 or anyclient+1600v8.0) there are also DHCP Request followed by DHCP ACK.

Cheers,
Vasco

That sounds like you really need to open a TAC with Cisco.

Also, did you capture the data on a mirror/span port to where the AP is connected? Does the DHCP Server send a DHCP reply and the AP simply doesn't forward it or does the DHCP server not send the reply?

From the tests I've ran in the lab, with the previous versions (tested 8.2.141, 8.2.161), I have DHCP packets leaving the windows 10 clients but there wasn't any DHCP packet reaching the WLC.

No problems with linux, apple or android clients.

 

Aparently, the problem is solved in 8.2.166. With that version, the DHCP packets leaving windows 10 clients reach the WLC.

 

I would love to see the caveats of ap1g2-k9w8-mx.153-3.JC14 but I haven't found its Rel. Notes yet.

Cheers,
Vasco

Upgrading to 8.2.166 solved the problem.

 

The 1602i are now running with image ap1g2-k9w8-mx.153-3.JC14 and now I have DHCP packets from windows 10 clients arriving to the WLC.

Cheers,
Vasco

View solution in original post

Hello

 

I'm having similar issues for  AIR-CAP1602E-A-K9 except with Autonomous setup

 

CAP1602+ Windows 10 = Cannot connect to Wifi

CAP1602+ Windows 7 =  Working

 

AIR-AP1231G-A-K9 + Windows 10 / Windows 7 (same configuration as CAP1602) = Working

 

Is there a bug that I am not aware of or does anyone know a work-around?

 

Here is a Debug I ran for Windows 10 and Windows 7

 

 

Win10

*Apr  2 03:19:01.805: dot11_auth_dot1x_parse_aaa_resp:

*Apr  2 03:19:01.805: dot11_auth_dot1x_parse_aaa_resp: found eap pak in server response

*Apr  2 03:19:01.805: dot11_auth_dot1x_parse_aaa_resp: Found AAA_AT_MS_MPPE_SEND_KEY in server

*Apr  2 03:19:01.805: dot11_auth_dot1x_parse_aaa_resp: AAA_AT_MS_MPPE_SEND_KEY session key leng

*Apr  2 03:19:01.805: dot11_auth_dot1x_parse_aaa_resp: Found AAA_AT_MS_MPPE_RECV_KEY in server

*Apr  2 03:19:01.805: dot11_auth_dot1x_parse_aaa_resp: AAA_AT_MS_MPPE_RECV_KEY session key leng

*Apr  2 03:19:01.809: dot11_auth_dot1x_run_rfsm: Executing Action(SERVER_WAIT,SERVER_PASS) for

*Apr  2 03:19:01.809: dot11_auth_dot1x_send_response_to_client: Forwarding server message to cl

*Apr  2 03:19:01.809: dot11_auth_dot1x_send_response_to_client: Started timer client_timeout 30

 

 

 

Win7

*Apr  2 03:31:51.225: dot11_auth_dot1x_parse_aaa_resp: Received server response: PASS

*Apr  2 03:31:51.225: dot11_auth_dot1x_parse_aaa_resp: found eap pak in server response

*Apr  2 03:31:51.225: dot11_auth_dot1x_parse_aaa_resp: Found AAA_AT_MS_MPPE_SEND_KEY in server response

*Apr  2 03:31:51.225: dot11_auth_dot1x_parse_aaa_resp: AAA_AT_MS_MPPE_SEND_KEY session key length 32

*Apr  2 03:31:51.225: dot11_auth_dot1x_parse_aaa_resp: Found AAA_AT_MS_MPPE_RECV_KEY in server response

*Apr  2 03:31:51.225: dot11_auth_dot1x_parse_aaa_resp: AAA_AT_MS_MPPE_RECV_KEY session key length 32

*Apr  2 03:31:51.225: dot11_auth_dot1x_run_rfsm: Executing Action(SERVER_WAIT,SERVER_PASS) for 6067.205d.946c

*Apr  2 03:31:51.225: dot11_auth_dot1x_send_response_to_client: Forwarding server message to client 6067.205d.946c

*Apr  2 03:31:51.225: dot11_auth_dot1x_send_response_to_client: Started timer client_timeout 30 seconds

*Apr  2 03:31:51.245: %DOT11-6-ASSOC: Interface Dot11Radio0, Station PHAPOWAP12 6067.205d.946c Associated KEY_MGMT[WPAv2]

 

It looks like client is never responding back or something is blocking the client from forming the connection. Maybe the firewall? After below message, it should have been associated to Dot11Radio 0

*Apr 2 03:19:01.809: dot11_auth_dot1x_send_response_to_client: Started timer client_timeout 30

anumpand
Cisco Employee

 

He resolved it by upgrading to 8.2.166.0 (at least Vasco Costa did).
Create
Recognize Your Peers
Content for Community-Ad