02-22-2024 02:23 PM
Good morning
at my home I have 2x Cisco 1815 AP with Mobility Express.
Everything is working fine with all my clients, except a new Samsung Galaxy Tab A8: it can not connect to my home SSID saying "WRONG PASSWORD". All other clients connect perfectly to the SSID, I have just one WLAN that is configured with default parameters. The only personalzation is the SSID, with PSK WPA2.
Any suggestion?
Looking at the log on the controller I see:
Thu Feb 22 2024 23:12:38 GMT+0100 (Central European Standard Time) | Dot11 | INFO | ASSOC_REQ | MESSAGE_RECEIVED | None |
Thu Feb 22 2024 23:12:38 GMT+0100 (Central European Standard Time) | Dot11 | INFO | ASSOC_REQ | INVALID_RSN_IE | None |
Thu Feb 22 2024 23:12:38 GMT+0100 (Central European Standard Time) | PEM | INFO | PEM_EVENT_MSG | IP_ACQUIRED_AND_AUTH_NOT_REQ_OR_STATIC_DYNAMIC_WEP_SUPPORTED | None |
Thu Feb 22 2024 23:12:38 GMT+0100 (Central European Standard Time) | Dot11 | INFO | ASSOC_REQ | CLIENT_MOVED_TO_ASSOCIATED_STATE | None |
Thu Feb 22 2024 23:12:38 GMT+0100 (Central European Standard Time) | Dot1x | ERROR | AUTH_DOT1X | WLAN_REQUIRES_802_1X_AUTH | None |
Thu Feb 22 2024 23:12:38 GMT+0100 (Central European Standard Time) | Dot1x | ERROR | EAPOL_KEY | ERROR_INITIALIZING_KEY | None |
Thu Feb 22 2024 23:12:43 GMT+0100 (Central European Standard Time) | Dot1x | ERROR | EAPOL_KEY | UNABLE_TO_ALLOW_USER | None |
Thu Feb 22 2024 23:12:43 GMT+0100 (Central European Standard Time) | Misce | ERROR | MISC_ROAM_EVENTS | 00:00:00:00:00:00, 4,c4:f7:d5:92:1e:40, 4, KEY_HS_TIMEOUT | |
Thu Feb 22 2024 23:12:43 GMT+0100 (Central European Standard Time) | Dot1x | ERROR | EAPOL_KEY | ERROR_INITIALIZING_KEY | None |
Thu Feb 22 2024 23:12:43 GMT+0100 (Central European Standard Time) | Dot1x | ERROR | EAPOL_KEY | UNABLE_TO_ALLOW_USER | None |
Thu Feb 22 2024 23:12:43 GMT+0100 (Central European Standard Time) | Misce | ERROR | MISC_ROAM_EVENTS | 00:00:00:00:00:00, 4,c4:f7:d5:92:1e:40, 4, KEY_HS_TIMEOUT | |
Thu Feb 22 2024 23:12:43 GMT+0100 (Central European Standard Time) | Dot1x | ERROR | EAPOL_KEY | ERROR_INITIALIZING_KEY | None |
Thu Feb 22 2024 23:12:43 GMT+0100 (Central European Standard Time) | Dot11 | ERROR | AUTH_RES | NOT_FROM_RELAY | slot 1 (claller 1x_ptsm.c:693) |
Thu Feb 22 2024 23:12:43 GMT+0100 (Central European Standard Time) | Dot1x | ERROR | EAPOL_KEY | RETRANSMITTING_EAPOL_KEY | None |
Thu Feb 22 2024 23:12:43 GMT+0100 (Central European Standard Time) | Misce | ERROR | MISC_ROAM_EVENTS | 00:00:00:00:00:00, 4,c4:f7:d5:92:1e:40, 4, KEY_4WAY_TIMEOUT | |
Thu Feb 22 2024 23:12:43 GMT+0100 (Central European Standard Time) | Dot1x | ERROR | EAPOL_KEY | IDENTITY_PACKET_RECEIVED | None |
02-22-2024 03:47 PM
Forgot to mention the software release: it was the 8.10.105.0 since years.
I upgraded first to 8.10.185.0 and then to 8.10.190.0, so the most recent one.
The problem is the very same.
02-22-2024 03:57 PM
@SonusFaber wrote:
ERROR_INITIALIZING_KEY
Samsung WiFi settings are incorrect.
What is the SSID configured for, PSK, Enterprise?
02-22-2024 04:05 PM
There is not so much to configure on the Samsung tablet... moreover I tested this tablet on many other AP \ wireless router and it works.
Anyway the config for the SSID is Personal WPA2: some of these APs are istalled in my home\office and work perfectly with any other devices since years.
I created a new SSID from scratch to test, using the very default configuration but no improvement at all.
02-22-2024 08:48 PM
Start with OPEN SSID. Does the Samsung client work?
If it does, how about cranking up to PSK?
02-22-2024 11:47 PM
Good morning.
With an OPEN SSID, it works
Module | Severity | Message Type | Message Subtype | Details |
Dot11 | INFO | ASSOC_REQ | MESSAGE_RECEIVED | None |
PEM | INFO | PEM_EVENT_MSG | WLAN_SUPPORTS_STATIC_DYNAMIC_WEP | None |
Dot11 | INFO | ASSOC_REQ | CLIENT_MOVED_TO_ASSOCIATED_STATE | None |
switching on the PSK WPA2, the Samsung says "wrong password" and the Cisco log what I alredy shared in the opening post of this thread.
What is also strange to me, regarding the Cisco, is that somewhere it says
Dot1x | ERROR | AUTH_DOT1X | WLAN_REQUIRES_802_1X_AUTH |
but why do I see 802.1x messages? I am not in the condition to use 802.1x
02-23-2024 06:45 AM
The debugs sometimes mention 802.1x even when it's PSK so don't get hung up on that.
Make sure your PSK doesn't have any extra exotic special characters that might not be handled correctly. Try a simple alphanumeric key for a start, also not too short or too long either.
Make sure the tablet software is fully updated.
Try disabling non-essential features on the WLAN - device may not be compatible with something.
02-23-2024 12:17 AM
- Use client debug(s) too according to : https://www.cisco.com/c/en/us/support/docs/wireless/aironet-1200-series/100260-wlc-debug-client.html , these can be analyzed with Wireless Debug Analyzer
- Have a checkup of the mobility express controller configuration using : WirelessAnalyzer input (procedure) for AireOs controllers
and feed that output into : Wireless Config Analyzer
M.
02-24-2024 05:51 AM
I still did not tried the client debug as suggested, but...
My SSID on the Cisco is set to WPA2 and also all my devices are WPA2 and all of them, but the Samsung A8, connect perfectly.
I configured a new SSID for testing and it is, as I said, the same story, but... enabling both WPA2 and WPA3 on the Cisco... it lets the Samsung A8 to connect, even if it is WPA2 only.
Strange?
02-24-2024 06:55 AM
> enabling both WPA2 and WPA3 on the Cisco... it lets the Samsung A8 to connect
How is the test WLAN different from the original WLAN?
02-24-2024 02:45 PM
HOME SSID: WPA2 only, works since years with no problem, but now this new Samsung does not connect saying BAD PASWORD
TEST SSID: created from scratch, leaving everything at DEFAULT. Same story, does not connect
TEST SSID: enabled WPA3 togheter WPA2... the Samsung connects
02-25-2024 03:20 AM
The fact that the problem only affects that one device suggests a bug in the device software.
But best to get an OTA (Over The Air) packet capture so that you can see whether it's device or WLC/AP at fault and open a case with TAC or Samsung depending on which is at fault.
02-25-2024 03:32 AM
Delete the existing (not working) SSID and re-create it.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide