topic Android 8.x cannot reach internet in Wireless

Android 8.x cannot reach internet

techpez34 — Mon, 05 Jul 2021 15:56:30 GMT

So work just gave me a new Pixel 2 running android 8.1. I can connect to the wireless but it tells me "Connected, No Internet". My coworker is having the same issue with a Sony running Android 8. It only affects Android 8.x, Android 7 works just fine.

Our wireless is managed by a 5508 controller running 8.0.152.0 and the SSID uses a PSK for security.

Anybody have any ideas as to what's going on?

Re: Android 8.x cannot reach internet

Scott Fella — Sat, 04 Aug 2018 19:32:13 GMT

Make sure that the wlan is set for WPA2/AES and not WPA/TKIP also. Does the device connect to an open SSID?

Re: Android 8.x cannot reach internet

techpez34 — Sat, 04 Aug 2018 19:38:09 GMT

We are using wpa2/aes. Haven't tried it on an open network yet. Will try it on Monday.

Re: Android 8.x cannot reach internet

Scott Fella — Sat, 04 Aug 2018 20:58:13 GMT

Best thing to do is try different scenarios and see what works and doesn’t.

Re: Android 8.x cannot reach internet

Leo Laohoo — Sun, 05 Aug 2018 00:52:05 GMT

Does the phone get a valid IP address?

Re: Android 8.x cannot reach internet

thomasd20141 — Mon, 06 Aug 2018 22:52:18 GMT

This might be nothing to do with your issue, but we recently had problems with Android 8.x devices connecting to the Internet on our guest network. Turned out it was due to the WLC Virtual interface address being set to 1.1.1.1 (now a legitimate Internet address). As soon as we changed it to an address from the Documentation reserved space (192.0.2.1) as recommended by Cisco docs anyway, the Android 8.x devices worked.
I believe they were complaining about certificates. This issue did not affect iOS devices or earlier Android devices.

Re: Android 8.x cannot reach internet

eekmiester — Tue, 07 Aug 2018 02:14:16 GMT

Howdy,

In addition to what has already been stated, are you certain that the device actually associated with the AP? I have had devices say they were connected, but didn't actually associate, usually because of encryption conflicts as mentioned. I have also seen this happen when the device has no IP, as well, which was also mentioned. Did you try forgetting the network on the device and connecting from scratch?