WiFi No Connectivity with 802.1x MSCHAPv2 - Nexus 6P Q&A, Help & Troubleshooting

I just received my Nexus 6p last night. It connected and ran just fine on my home network. I get to school this morning and I can not connect to the school wifi which uses 802.1x MSCHAPv2 authentication. My Computer and my friend's Note 4 next to me can connect with out issue. Anyone else have this issue? Possible solutions?
*UPDATE*
I just tried to connect to our guest Wifi with the same problem. Instead of using MSCHAPv2 Auth, the guest WiFi uses a captive portal. I still can not obtain an IP address from either. It looks like it might be an incompatibility with the access point itself? This is really weird as 1 / 2 of the networks I have tried to connect to succeeded and one was a Asus router (my home). The access points I am having trouble with are Aerohive from what I read on them. I do not know what the controller specs are.

i'm having issues connecting to a regular enterprise PEAP network, it just sits there saying "Connecting...", whereas our public portal it pulls up fine. still can't figure out why.

iceman3kco said:
I just received my Nexus 6p last night. It connected and ran just fine on my home network. I get to school this morning and I can not connect to the school wifi which uses 802.1x MSCHAPv2 authentication. My Computer and my friend's Note 4 next to me can connect with out issue. Anyone else have this issue? Possible solutions?
*UPDATE*
I just tried to connect to our guest Wifi with the same problem. Instead of using MSCHAPv2 Auth, the guest WiFi uses a captive portal. I still can not obtain an IP address from either. It looks like it might be an incompatibility with the access point itself? This is really weird as 1 / 2 of the networks I have tried to connect to succeeded and one was a Asus router (my home). The access points I am having trouble with are Aerohive from what I read on them. I do not know what the controller specs are.
Click to expand...
Click to collapse
For the 802.1X issue, see https://code.google.com/p/android/issues/detail?id=188867#c29

nick.lowe said:
For the 802.1X issue, see https://code.google.com/p/android/issues/detail?id=188867#c29
Click to expand...
Click to collapse
Yep, my company network uses PEAP + MSCHAPv2 and I couldn't connect with my 6P. I forwarded that thread to our IT department and a couple days later it magically started working correctly.

OK, I have discovered a work around. Sadly I don't have a responsive IT department at my school. What I have found is to use the DCHP client from lollipop. Enable developer options, enable "Use legacy DHCP client", reboot. This is just a work around and I hope someone finds a solution to this, either on the android side or on the server side. I know my campus uses windows server 2008 for their radius and auth server so the freeradius TLS 1.2 issue isn't totally relevant. Maybe someone could enlighten me how TLS 1.2 is handled in Windows Server.

Related

Off topic - Wireless - What am I doing wrong?

Pardon me because this isn't entirely a Wizard specific questions although I am able to replicate the problem with my Cingular 8125 (new ROM) 100% of the time.
I'm not a stupid person. I've setup numerous wireless networks for corporations and home users. I always use WEP or WPA and never unencrypted (no) security.
In most situations, the wireless router does NOT supply the DHCP to the clients. It usually comes from another DHCP server on the same LAN segment. Typically, this is a Windows server although it could be a DHCP-assigning device, such as a Cisco router.
PCs have no trouble seeing the wireless network and connecting to it and getting addresses assigned to them. For a while, I couldn't do this on WPA security but upgrading firmware and software on the laptops (usually Dell) rectified this.
With my Wizard, both old and new ROMs, I can SEE the wireless networks and connect to them but I can NEVER get an IP address. It tries and tries and fails and fails and eventually gives up. (Yes, the Cingular proxy is turned off)
Yet, at the airport or other public places with free wireless, I have no problems connecting my Wizard to the access point and surfing away. Thus, I know its not (entirely) a Wizard issue. Of course, these public access points aren't encrypted which could be one of the reasons but I doubt its the only one.
As a test, I just built a new wireless router with a SSID (other than "default") and security turned on (WPA) and let the router act as the DHCP server. Wizard connected in seconds and was surfing away. So the obvious next question is: why doesn't this work when the wireless router ISN'T the DHCP server? Other machines (laptops and such) have no problem connecting to one wireless router and getting a DHCP address from another box yet my Wizard cannot.
I've tested this with D-Link and Belkin wireless routers (consumer-grade).
I've seen other people post that they cannot get their wireless to work on their Wizard and while the fix may not be on the side of the Wizard, I think others may be in the same boat I'm in so I'm hoping that maybe we can compare enough stories to narrow this down so that we CAN use our Wizards wirelessly!
Ken
Confusing...
maybe you should try assign a fix ip to your pocket's wifi adapter and see if it would work. or just let the wlan security turn OFF on your access point to see what would happen.
i guess that the network protocol stack is slightly different between a PC and a PPC, which limit the DHCP request route.
I have just purchased the Wizard, aka o2 XDA Mini S, and use it with my Belkin Wireless Access Point (WPA-TKIP Enabled, DHCP & NAT disabled) and Cisco ADSL Router (DHCP Server) without any problems.
I have assigned the Belkin Wireless Access Point a fixed IP address however, but I don't think this would make a difference.
The other thing I found was that the Wizard would not connect correctly to the Belkin using WPA with AES encryption, but switching it to WPA with TKIP works flawlessly.
Well, I suppose its encouraging that others with the same wi-fi routers are getting this to work but its discouraging that I'm having so much trouble!
Fixed IP does work (therefore, its unlikely a Wizard-only problem) but obviously a fixed IP doesn't let me roam from one hotspot (home) to another (work) very easily.
Haven't tried it sans-security yet although that might just prove a point, rather than be a perminant solution. I have tried WPA-PSK and WEP with the same (negative) results.
I personally have found that unless I change the power settings for the WiFi adapter to full power, its hit or miss.
Never have a problem maing connections, geting leases, etc with it there.
YMMV though
Regards - John
prob irrelevent
i found that before i active sync'd. the wireless monitor on my wizard showed a strong signal from the router. then after it synced, it picked up an IP from the servers dhcp fine.
also for lightweight simple security i use mac address filtering on the AP

XDA WiFi Access through Radius Server Authentication???

We have a corporate WiFi network and our access is protected via Radius server authentication and WPA encryption.
I have done all the necessary steps to import the personal certificate and added the profile on our XDA Mini S model.
Looking at the logs of the Radius server, everything is connecting and authenticating fine. However, the XDA fails to get any IP from our DHCP server. Not sure where the problem lays?
I have tried an access point on the same LAN with all security disabled and open and the XDA gets an IP with no problem.
Please help - this is very frustrating and I want to know if anybody has got their XDA working through a radius server?
Im having a similiar problem, Only mines is with a MDA compact II, I can find all access points no probs, But it seems as if my handset is trying to connect via GPRS instead of the wifi and that is without a sim card present :|
Nah, the issue is different for me. I can connect to an access point that does not use radius authentication fine, and get an IP and use the internet etc.
With radius authentication I am unable to get an IP.
I have been trying to get this working too and talked to XDA about it, however they said that the Atom does not support WPA-EAP
I used to be able to connect to a WPA-PSK network OK but since my ROM upgrade it doesn't work anymore.. Grr.
We are not using WPA-EAP. We are using PEAP authentication, with trusted certificate and WPA TKIP Encryption.
I have not spoken to O2/XDA about this yet. As I have said, authentication works fine, the IAS Radius logs confirm that connection is permitted - its an IP that fails to get associated with the device! Even Static IP seems to connect, but you cannot reach anything on the network.
I wonder how tech-savy the XDA support will be when I do actually ring them?
What is frustrating is the fact that the device explicitly supports this kind of connection (why does it exist in the Wifi settings otherwise) but with all correct settings it just fails on the IP and traffic flow (with static IP)...??
No Bios upgrades done yet? The device is Windows Mobile and all this kind of thing is surely software/OS driven - cannot understand how a bios/rom upgrade would make it work?
Coxy said:
We are not using WPA-EAP. We are using PEAP authentication, with trusted certificate and WPA TKIP Encryption.
Click to expand...
Click to collapse
PEAP is an EAP method - I've been reading up on it
I have not spoken to O2/XDA about this yet. As I have said, authentication works fine, the IAS Radius logs confirm that connection is permitted - its an IP that fails to get associated with the device! Even Static IP seems to connect, but you cannot reach anything on the network.
I wonder how tech-savy the XDA support will be when I do actually ring them?
Click to expand...
Click to collapse
I'm not very impressed with their technical support so far, it's took them a while to _understand_ the problem, let alone try and fix it.
What is frustrating is the fact that the device explicitly supports this kind of connection (why does it exist in the Wifi settings otherwise) but with all correct settings it just fails on the IP and traffic flow (with static IP)...??
Click to expand...
Click to collapse
I tried to connect to a WRT54G running OpenWRT I could see that it would associate fine but would not become authorized - it will appear to 5 seconds and then drop out and try again.
I wonder if there is some timeout that needs to be increase, however I can't find any options in the AP to adjust
No Bios upgrades done yet? The device is Windows Mobile and all this kind of thing is surely software/OS driven - cannot understand how a bios/rom upgrade would make it work?
Click to expand...
Click to collapse
Me either, and it doesn't seem like a particularly uncommon scenario...
(Unless they think workplaces should use WPA-PSK )

Can't connect to Wi-Fi

I have a brand new wireless router; BELKIN N1 VISION.
I have set the security for this router as followed:
- Security Mode: WPA/WPA2-Personal(PSK)
- Authentication: WPA-PSK +WPA2-PSK
- Encryption Technique: TKIP + AES
Unfortunately my Qtek 9100 (with WM5) does find my wireless connection, but it refuses to make a connection after input of the WPA-code.
I'd try setting the security to either WPA-PSK or WEP. Some older laptops and wireless cards have issues with WPA2 and that could be causing it. Anyways, I'm probably wrong, thought I'd just throw it out there.
or also that you have a MAC (Media Access Control) Binding enabled on he router as a security measure.
I had the same problem yesterday, figured it out by adding my Wizard in the Access Control Enabled list.
Then there was the problem of not connecting automatically which I fixed by enabing IEEE.
Did anyone get this fixed ? - I have also bought a Belkin N1 - not MAC Enabled, no security enabled (WAP et al) - I live on a farm so that's not an issue !. My Nokia N95 *M works well with this over WiFi however my K-Jam finds the Router but cannot connect, comes back as unavailable all the time. HELP PLEASE !!!
hey guess what
my ignorant ass has.. the same problem!
my linksys router (WRT54G) has both b and g broadcasting (mixed)
i use static ip addresses and i'm not seemingly capable of assigning a static ip address on the G3.. before i attempted to assign the IP on the wiz, it would draw the connecting icon and eventually come back with "unable to obtain ip address"
so i knew that i needed to assign the ip.. so i gave it my best shot (i was able to do this on the laptop) and now it doesn't complain about not getting an ip address, it just never stops drawing the connecting icon, never connects, and i'm (obviously) unable to connect to the net via wifi.
any ideas or help or will this be a thread that just slowly rots without one of the xda-developer gods stepping in and solving problems for us brainless members?
hey man if it was a Ford i'd fix it for ya..

This WiFi issue is killing me!

I know Google has said they are looking into it. But this is ridiculous. The N1 can not handle WPA2 connections. Even though it saves the connection and password, it almost never reconnects automatically. From what I was reading on the Google help forum, it appears to have compatibility issues with many retail routers and they suggest upgrading the firmware on our routers. Throughout my day, I may connect to 3 different APs. One is a standard Linksys wrt54g with sveasoft, the others I connect to are Cisco APs.
None of them automatically reconnect. Most of the time on the Linksys, I have to delete the connection on the phone and re-add it.
I still like this phone but between the 3g and wifi issue, it is a pain to use.
I won't pretend to understand all that you just said, but I can tell you that my router is set up using WPA2-PSK. Not sure if it is the same as just WPA2 but my N1 reconnects to mine whenever I get in range. Then at the office it will connect to the WPA2-PSK set up in there, and one more regular open connection that is available at our pool. Pretty much every time I look at it, it is connected to one of those 3. Or else if I am OOR of any of those, I am on 3G.
My home router is a Belkin -N. Work routers are a Netgear -N and a D-Link -N.
I've got a Netgear WNR2000 on WPA2, and I can confirm I occasionally have this issue with the phone not connecting to the network automatically. It usually does if I go into settings and touch it to reconnect again.
There is an easy solution for any WIFI problems, use a Mac Filter!!
I have to go into Settings > Wireless & Networks > WiFi Settings before my Nexus One will reconnect to my home router, which is also using WPA2-PSK.
Hopefully it'll be sorted in a firmware update, it is annoying having to go through 3 screens to do something that my Nokia Symbian phones have been doing without issue for almost5 years...
I am having no problems auto connecting to my home WPA2 network, I am using AES encryption and running DD-WRT firmware if it helps.
philaldred said:
There is an easy solution for any WIFI problems, use a Mac Filter!!
Click to expand...
Click to collapse
Mac Filters are no replacement for WPA2 or encryption. Almost every device has the ability to spoof a mac address. Using a mac filter might help quickly eject roaming devices nearby, but it is NOT security.
Its like using a No Trespassing sign to replace locking your doors and windows.
i found that APNDriod may be a possible culprit....
Before I installed APNDriod , every times I go back home, my N1 will connect to my home WiFi almost immediately.
But after I install APNDriod, my N1 will not connect to my home WiFI.....I need to go into the Wireless setting screen, once i am on that screen WiFi it will connect.
But it is strange this I don't have this issue in my office, it just connect automatically before and after installing APNDriod.
Today I tried NOT to use APNDriod for a day and my N1 connect to my home WiFi without issue..... will do more experiment tmr.
Netgear WNR3500 w/ WPA2-PSK. Reconnects every time I am in range.
I find that my Linksys is the worst. The Cisco Aironet 1121 is better, but still has occasional connection issues. And I have not installed APNDroid.
On another note, when my phone switches from 3g to 2g and vice versa, it takes a long time for the data connection to resume
My network at home is setup with WPA2. I have no problems connecting to it... I click on the little wireless icon, and wait for it to say "wireless settings updated" and also wait for the wireless icon to show up near the time... then i will start browsing
I have a Dynalink RTA1025W
My wifi is working now. See h**p://forum.xda-developers.com/showpost.php?p=5773148&postcount=26
No problem reconnecting to my home network with WPA2 . Apple's Airport Extreme.
No problems here connecting to my Belkin N1 router. Connects the moment its in range.
Setup using WPA2-PSK
im having this exact same problem on my D-link Dir 615!
Pisses me off alot, i hope Google fix it!
I found that unless I was on channel 6 or 11 I had issues
AES-CCMP, TKIP or WPA Cisco521G will not connect
My cisco 521AP does not connect using any type of encryption, it only works with open authentication. Expensive phone like this that doesnt work with business class products is a joke.
xoveruk said:
My cisco 521AP does not connect using any type of encryption, it only works with open authentication. Expensive phone like this that doesnt work with business class products is a joke.
Click to expand...
Click to collapse
@xoveruk - Someone must be able to help sort out this issue !
xoveruk said:
My cisco 521AP does not connect using any type of encryption, it only works with open authentication. Expensive phone like this that doesnt work with business class products is a joke.
Click to expand...
Click to collapse
My suggestion is - check what you're doing wrong before assuming the phone is at fault. And check that you're using PSK.
SEC AUTH ENCRYPTION
No security None Open - working
WEP WEP Open - no
WPA-PSK TKIP WPA-PSK - no
WPA2-PSK AES CCMP WPA-PSK - no
android 2.2 on N1, FRF91

(Solved) [Q] Android devices connects to wifi but no internet

I have three Android devices and two laptops, all of which I have been using on my home wifi network for years with only minor issues now and again. All of which I have been able to resolve. Two of the Android devices are phones and are rooted with custom roms and one is an unrooted Nexus 7.
Sunday, the 6th of April (yesterday) all 3 of the Android devices lost internet connectivity spontaneously but both laptops still access the internet with no problems over wifi. I was not doing anything with the network or any of the 3 devices. The Android devices all still connect to the wifi and they can all access all the other devices on the home network. I can ping my phone from my laptop and I can ping my laptop from the phone. I can access the files on my phone using AirDroid. I have reset every device on the network including the wifi access point and the cable modem. I called my ISP and they are saying that it might be due to the fact that my cable modem has reached "End of Life" and does not support newer Docsis 3.0 technology which for some reason now precludes Android devices from accessing the internet. I don't buy it. I read up briefly on Docsis 3.0 and it is supposed to be backward compatible with Docsis 1.0 and 2.0. I have not had a chance to see if my phone or the other devices will connect to the internet through other wifi networks but I suspect they will. My phone does connect through the 3g network.
Anybody having this issue and if so have you found a fix? My only solution at this point is to buy a newer cable modem that supports Docsis 3.0. It's not all that expensive but I don't want to buy one if I can't confirm that is the problem. The one I have seems to be working fine with the laptops and was working fine with the Android devices before it quit working. If that is the problem.
If anybody has any suggestions as to how I might test this I would be grateful.
Do you have a terminal app? Start pinging your router then 8.8.8.8. Then if you can ping Google, then it is something else.
Sent from my Nexus 5 using xda app-developers app
That did the trick. At least for now.
MrObvious said:
Do you have a terminal app? Start pinging your router then 8.8.8.8. Then if you can ping Google, then it is something else.
Click to expand...
Click to collapse
Dude, you nailed it. I pinged google and that didn't work and when I pinged the IP it worked. I also was able to ping that 8.8.8.8 ip. I knew then it had to be a DNS issue.
I then set my IP on the phone to static and then I used the Google dns server IPs 8.8.8.8 and 8.8.4.4 as my DNS servers and Bingo, it worked. Why was it working before? What changed overnight? And why did it occur to all three Android devices at the same time. Up until now I had been using DHCP and everything worked fine. I even went for a walk around the block and found a couple of unsecured wifi networks and connected to them and subsequently the internet. But when I got home and connected to my network, no joy. However, as stated in the OP, our wireless laptops work just fine. Maybe Comcast is sending out the wrong DNS IP or they just somehow no longer support Android???
Electraglider said:
Dude, you nailed it. I pinged google and that didn't work and when I pinged the IP it worked. I also was able to ping that 8.8.8.8 ip. I knew then it had to be a DNS issue.
I then set my IP on the phone to static and then I used the Google dns server IPs 8.8.8.8 and 8.8.4.4 as my DNS servers and Bingo, it worked. Why was it working before? What changed overnight? And why did it occur to all three Android devices at the same time. Up until now I had been using DHCP and everything worked fine. I even went for a walk around the block and found a couple of unsecured wifi networks and connected to them and subsequently the internet. But when I got home and connected to my network, no joy. However, as stated in the OP, our wireless laptops work just fine. Maybe Comcast is sending out the wrong DNS IP or they just somehow no longer support Android???
Click to expand...
Click to collapse
I am having this exact same problem. My laptop connects to wifi and my desktop, ps3, and TV via Ethernet but all of a sudden about an hour ago my Nexus 5 and Nexus 7 can no longer access the internet. They are connected to the network however the signal indicators in the quick settings is orange and I can't access the internet.
Could you tell me exactly what you did to fix this as I am not good with networking type stuff at all...you mention pinging and DNS servers and I have no clue what you're talking about.
BTW I have AT&T U-Verse.
EDIT: I ping'd google in my phones terminal and it didn't work....I ping'd my router and that worked(I think it did anyway...it kept pinging and I had to close terminal to stop it)
I ping'd 8.8.8.8 and got Destination Net Unreachable.
Jonnyredcorn said:
I am having this exact same problem. My laptop connects to wifi and my desktop, ps3, and TV via Ethernet but all of a sudden about an hour ago my Nexus 5 and Nexus 7 can no longer access the internet. They are connected to the network however the signal indicators in the quick settings is orange and I can't access the internet.
Could you tell me exactly what you did to fix this as I am not good with networking type stuff at all...you mention pinging and DNS servers and I have no clue what you're talking about.
BTW I have AT&T U-Verse.
EDIT: I ping'd google in my phones terminal and it didn't work....I ping'd my router and that worked(I think it did anyway...it kept pinging and I had to close terminal to stop it)
I ping'd 8.8.8.8 and got Destination Net Unreachable.
Click to expand...
Click to collapse
I don't know what AT&T U-Verse is but the problem I had was that for some reason my Android devices would no longer access anything outside my home network. I used a terminal app that I have on my phone and I was able to ping 8.8.8.8 which I understand is one of Google's DNS servers. DNS stands for (Domain Name Service) which allows us humans to type in meaningful names in a browser rather than the IP address. If you can enter this http://74.125.224.72/ into your browser on your Android device you should get to Google. If that works then you need to point your device to a DNS other than the one assigned by your ISP. I just used 8.8.8.8 and that solved my problem. You can also change the DNS server in your gateway device, whatever it happens to be, and that would fix the problem as well. That is assuming you can reach Google using the IP address I have mentioned previously.
There should be all sorts of tutorials and suggestions regarding how you can make the necessary changes. It all depends on your device and network appliances.

Categories

Resources