Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-11-2019 12:08 PM
Hello,
We have 2 SSID here, "public" and "private". There is a password on each.
But someone told me he can't see the "public" SSID, he sees "public2" and the "public" 's password doesn't work on it. So he can't connect.
Why does it create another SSID like that? And what I have to do to connect him to "public"?
Thank you.
We have 2 SSID here, "public" and "private". There is a password on each.
But someone told me he can't see the "public" SSID, he sees "public2" and the "public" 's password doesn't work on it. So he can't connect.
Why does it create another SSID like that? And what I have to do to connect him to "public"?
Thank you.
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-12-2019 01:51 PM
It's solved.
public SSID was saved in its wireless connections. I removed it and it was again possible to see the public SSID and connect to it.
It's maybe the reason why there were a "public2" SSID...
*just thinking*
public SSID was saved in its wireless connections. I removed it and it was again possible to see the public SSID and connect to it.
It's maybe the reason why there were a "public2" SSID...
*just thinking*
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-11-2019 01:59 PM
Hello Jo,
Chris
- Is this limited to this one wireless client or is it widespread?
- Please make sure that 'public' ssid is being broadcast: https://gtacknowledge.extremenetworks.com/articles/Q_A/Why-aren-t-the-APs-broadcasting-the-WLAN-SSID
- Make sure that the SSID is enabled: #show wireless wlan config
- Make sure the SSID is mapped to the radios: #show wireless radio wlan-map
Chris
Christoph S.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-11-2019 01:50 PM
Hello Jo_Biblio,
I am assuming the wireless device you are using is a Windows Laptop or PC.
If this is the case more than likely what the end user is seeing is a duplicate wireless profile created on the Windows device.
This does not mean there is a duplicate SSID from the perspective of WiNG.
As Robert noted you can always confirm by executing "show wireless wlan" from the controller or suspected AP.
I am assuming the wireless device you are using is a Windows Laptop or PC.
If this is the case more than likely what the end user is seeing is a duplicate wireless profile created on the Windows device.
This does not mean there is a duplicate SSID from the perspective of WiNG.
As Robert noted you can always confirm by executing "show wireless wlan" from the controller or suspected AP.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-11-2019 01:30 PM
Unless you created and mapped the WLAN public2 to radio WiNG would not duplicate it.
Its possible that the wlan public2 is not even yours but its in your airspace.
Please verify if that WLAN is even yours via CLI run the following command ' show wireless wlan '
Its possible that the wlan public2 is not even yours but its in your airspace.
Please verify if that WLAN is even yours via CLI run the following command ' show wireless wlan '
