Tech Forum

All,

We've run into a problem that I wanted to see if anyone else is experiencing. Some of our members with Android 5 devices (as well as the one person with a Chromebook ) are having trouble connecting to WiFi at our stake center. Windows, OS X, iOS (and even Linux, AFAIK) all seem to be unaffected, as well as Android 4. Some devices simply won't connect, others throw an error, then still connect anyway.

Has anyone else seen this, and is there a workaround or fix for it? I've just started my troubleshooting, so I'll post anything else I find here.

Thanks y'all!

Jason Lewis
Columbus Ohio South Stake

I wonder if it is related to the DNS problem that Chomecasts run into?

Googling for "Android 5 WiFi Problem" seems to turn up a number of hits. I noticed my Nexus 7 has yet another update.

Edit: My Nexus is now up to 5.1.1

My Nexus 7 is happy to connect to the 1041 WAP. It used a remembered connection and latched on immediately.

Oh man, I just realized that I forgot to come back and post the resolution for this. It turned out to be a rogue access point giving out IP addresses that were completely different from those on our LAN. Something about the Android DHCP client seemed to prefer that DHCP server over the Cisco one, or perhaps the other clients just did better checking to see which DHCP server matched the addresses on the network.

le_jawa wrote:Something about the Android DHCP client seemed to prefer that DHCP server over the Cisco one, or perhaps the other clients just did better checking to see which DHCP server matched the addresses on the network.

As far as I know, it's a "race" condition - the unit picks up the first response. So if the Cisco was a bit slow or otherwise occupied.... Perhaps some clients have figured out a way to deal with it.

How did you find and disable the rogue DHCP?