Small (just me) problem connecting my Pixel 3L with Android 11. We have a private VLAN for BYOD. Users enter their network credentials, same as workstations. No issues for the most part, but only a handful of people in our office still. I'm running into the connection being made, then disconnecting. Then after a while it lets me know there's an authentication problem. I've got another user on an Android, I don't think 11, with no issues.I've set the connection to not randomize the MAC, thinking Aruba might have a problem with that, but no joy. On the controller, I actually see my MAC, but it's got 0.0.0.0 and NOFP, which I think is it's way of saying it can't recognize the OS. But I know this phone's been on this VLAN before. But since then both the controller and phone have been updated.
What am I missing?
Ha! Yes, you did.I will say, I do have eyes into our admin side, but we're a small shop where 1-2 people have to know everything about all systems, which means I know very little about a lot of things. Wifi architecture low on that list. Our MS teams is helping, but I was hoping to find out more to speed that up since that takes a while.
We think having a non-CA cert might be helpful, so the next step is having a *.ourdomain.org available on the controller.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.