Why can't users connect to my new Wi-Fi profile in the Knox container or the device side?
Article ID: 115013145427
| Last updated:
Any Samsung devices running the Knox framework
When a second WiFi profile has been created on a device with the same Service set identifier (SSID) as an existing profile, the user is unable to connect.
If a device has already been provisioned with a Wi-Fi profile and a second profile is created with the same SSID, the device won't be able to connect to the Wi-Fi network.
This behavior is intentional. For security reasons, end users and other IT admins aren't allowed to create profiles with the same SSIDs. To solve this, create a new Wi-Fi profile with a different SSID.
Was this article helpful?
Sorry about that
Why wasn't this helpful? (check all that apply)
Thanks for taking the time to give us some feedback.