SSIDs Switch Over Problem

Unanswered Question
Jan 30th, 2008

Hi, We are facing issues with wireless SSID switch over. We have deployed

WiSM with 270 Access Points. We have created 3 SSID on Controllers. Out of 3, 2 are

broadcasted & 1 is not broadcasted. Now when we try to connect Corporate SSId (PEAP

Authentication) it connects perfectly. When I try to switchover to not broadcasted Comms

SSID (Web-Auth, we are able to connect first time only. Second time when we try to switch

from corporates ssid to comms ssid laptops does not connect to hidden SSID. It with every

laptops in network. While troubleshooting we observed that when we use any third party

wireless software to connect to these SSID it works but when we try to connect with

Windows Wireless Adapter it does not work. & there are almost 80% users are using Windows

Wireless Adapter to connect to wireless network.

Couple of interesting observation which we did that when you manually add comms (hidden

ssid) into windows wireless adapter we get status "comms (Automatic)" & we can able to

connect to hidden ssid. Now if we say disconnect from comms ssid & connect to corporate

ssid it works. & if we again try to connect back to comms (hidden ssid) it does not work &

status of this hidden ssid becomes "comms (manual) in windows wireless adapter settings.

We tried so many thing but this switch over is not happening with Windows Wireless Adapter

& this problem is appearing only when you switch from broadcasted ssid to non broadcasted

ssid & vice-versa. All laptop users are using windows XP service pack 1 & 2.

Please help us to resolve this issue. I am not sure whether its controller config problem or bug in windows.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
rduke Wed, 01/30/2008 - 12:10

Before you spend too much time on this problem, you probably want to check to see if the Windows WPA2 update fixes this. It is supposed to address several issues, one of which is for non-broadcasting SSIDs. See below link to Microsoft. It is not included in the usual patch process.



This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode