Your client must support one of the EAP types required by your RADIUS server and must supply a valid login.If the only entry in the list is unspecified, you must first add a certificate file to your device.
To do so, copy a certificate to a storage location accessible from your device (see Figure 6).Hint: Email the file to yourself and save it to your device, or upload the file onto Google Drive. Tap Install from storage and choose the storage location of your certificate file.If multiple clients are unable to connect, follow instructions in our wireless network troubleshooting tip to debug probably AP or router or upstream network problems. When Wi-Fi is on, a signal indicator appears at the top right corner of your home screen.Otherwise, proceed to step 2 to debug the affected Android client. Before going any further, make sure that your Android device's Wi-Fi radio is not in Airplane Mode and that Wi-Fi is on and ready to connect. Properly connected Wi-Fi takes precedence over mobile broadband, but it can be helpful to disable your device's mobile network connection while debugging Wi-Fi.Compare security settings on your AP/router and Android Wi-Fi client and attempt to match them.
If you choose the wrong security type when adding a network, it may still be saved.Refer to our network troubleshooting tip, step 8, to check your AP or router's RADIUS settings.If RADIUS is working but your Android Wi-Fi client's connect requests are rejected, look for an 802.1X Extensible Authentication Protocol (EAP) problem.You can change the password (or any other security parameter) associated with a saved network by tapping the network's name.However, it is often easier just to click Forget for any misconfigured network and start fresh. WPA-Enterprise and WPA2-Enterprise log the Android Wi-Fi client into the network and deliver encryption keys using an 802.1X-capable RADIUS server.I can't figure out why I can't get it up and running now.