Just to chime in on this…
I’ve had similar experiences when connecting to WPA2 Enterprise using Linux (multiple distros). Settings are correct, I am using the radius.uvm.edu cert. The first initial connection takes several attempts. Once I connect all is good, reconnects flawlessly throughout the day as I move around campus. WPA2 Personal always works fine for me.
That being said, this doesn’t seem to be unique to UVM wireless, friends of mine at other institutions have the same issue when connecting to WPA2 Enterprise networks.
Interesting, it was fine all day – I left it here overnight and I’m having exactly the same issue as Matt. Haven’t seen this on any other device I’ve used with the UVM network before.
UVM School of Business
I know it’s late in the thread, but I can confirm similar behavior with my Nexus 9 tablet. Running 6.0.1, it can take up to 10-15 minutes for it to reconnect to the UVM wireless network (even now after being connected to it successfully at least once daily). At home I don’t notice the same delay in reconnecting to WiFi after pressing the power button to wake it up.
The symptoms discussed here are similar, it goes through the “connecting -> obtaining IP -> saved -> connecting” loop. Usually I have to bring it out of standby (hit the power button to wake it up) well before I know I will need it because of this. It will show the WiFi signal icon as an empty outline while it attempts to reconnect multiple times.
There were some threads related to the “doze” feature in marshmallow and how it affected WiFi and I’m wondering if this might be somehow related.
Just a few thoughts,
Just a follow up – After trying unsuccessfully a couple more times it just connected on its own earlier today and it’s been connected all day without changing anything on the device.
UVM School of Business
There have been issues connecting to Google Play -- with unclear cause/solution --predating Marshmallow. I had problems connecting to Google Play on two different devices for a period of a few months in 2014, on both the UVM WiFi and my home network, but it eventually cleared up. I started a forum thread about it at the time, and the thread has had activity as recently as a few months ago. And for what it's worth, I have not had this trouble on my current phone (though it is on 6.0.0, not 6.0.1 if that makes any difference).
Department of Mathematics & Statistics
University of Vermont
Yeah, I would 2nd that as I doubt I’m going to see anything interesting in the wireless controller logs. Greg, if you come up empty though certainly let me know.
I’ll also mention some interesting problems with Android phones on 6.0.1 not being able to get on the Google Play store when connected to the UVM ssid. I’m trying to diagnose that issue but running into roadblocks that I’ve yet to overcome. I mention it though b/c something seems odd about Android 6.0.1….perhaps an issue with PEAP and MSchap v2?