Team, Customer deployed Cisco Aironet 3500 AP's and CT5508 controller in their warehouse. Our MC3190 WM6.1 can connect to the "802.11a" band only when the name of the SSID is broadcasted. Is this a normal behaviour of our terminals? When the SSID is hidden cannot connect. Has anyone experienced such a issue? Thanks Roland
Can't associate to 802.11a when using hidden SSID |
4 Replies
Roland Besides trying the latest Fusion version, can you please check if you have the 802.11d option checked under Fusion options? If yes, can you try to connect the device to the WLAN with the hidden ESSID with 802.11d option unchecked? (You will have to configure the correct country code manually). The reason for asking this, is a while ago (2009), we had a support case, where the Cisco AP was not sending the country information when Hidden ESSID is used. This can be the reason why the device connects only when the SSID is not hidden (if 802.11d is option is checked) As a side note, SSID hiding is not recommended for security purposes, as the SSIDs is present in other frames: e.g. Probe request/response, Association/Re-association request frames. In addition, u nder normal operation, beacons are transmitted 10 times/ second. If the SSID is hidden, the MUs will have to use active scanning to associate and/or roam. Too many probe requests/responses can affect network throughput. Hope this helps.
Fusion version is: 3.00.0.0.311R
Yes, profile is created in Manage Profile
No, because in Find WLAN option, "create profile" is not highlighted
Hi Roland, The Fusion which you are using is a very old. Please try the latest one available from the support central and verify whether the issue still exist.
Hi Roland, It should connect. Can you answer the following questions? 1. What is the Fusion version? 2. Is the profile created in Manage Profile? 3. Is Find Wlan is used to create profiles?