Hello,
I'm trying to configure a Chromebook to connect to our secured wireless network, but I'm having trouble. I wanted to check here to see if anyone else is experiencing the same issue or if anyone has been successful in connecting their Chromebooks to their secured network.
We have two SSIDs. One is a guest network that is open but requires a guest login. The other is our secured network and uses WPA2-Enterprise/AES, PEAP, and MSChapv2. Users (on devices that connect) enter their AD credentials and login. With the Chromebook, we enter PEAP as the EAP method, MSCHAPv2 as the phase 2 authentication method, no cert, and enter AD username and password, but the Connect button remains grayed out and unclickable. We are able to connect the Chromebooks to our guest WLAN without a problem.
Google searches have returned hits on Google's Chromium site where others are having similar issues, but with no apparent solution. I've found a possible work around, but haven't attempted it because it requires rooting the Chromebook. I'm leaning toward the Chromebook being at fault, but wanted to cover all the bases and check here. Is anyone else having a similar issue/know of a potential solution?
We're running ArubaOS 5.0.2.1 on a mix of 3200 and 3400 controllers, but are planning upgrading to 6.1.3.7 by way of 5.0.4.10 in the next week or so. Our APs are all 125s. Any help is appreciated.
Thanks!
Mark
#3200#3400