Wireless 802.1 EAP stuck at "obtaining IP address" on KitKat stock (can't connect)
Hello everybody,
i know that it seems to be a common bug but i've found a lot of complaining about it but no solutions, so i hope i'm gonna be more lucky opening a more recent post.
I have a Nexus 4 and i was using Paranoid Android 3.99 (based on Jelly Bean 4.3) and then yesterday i decided to come back to Android AOSP stock in order to upgrade to KitKat 4.4.2.
I followed this procedure that is the official Google procedure, by the way.
I've wiped everything, including SD Card, and flashed every piece of the stock KitKat 4.4.2 for Nexus 4 (Android 4.4.2 KOT49H): boot, bootloader, flash, radio, system, userdata and recovery.
Now, i'm not able to connect to the wireless of my office that is protected with 802.1 EAP (PEAP + MSCHAPV2). The authentication is passed but then i get stuck at "obtaining IP address" and after a few attempts i receive the message "network disabled poor connection".
Once every 1000 attempts, i am able to connect successfully.
The signal is excellent, i'm really close to the access point.
I'm the only having this problem; we have a lot of Android phones and iPhones and they all work great.
I can't use a static IP address and i can't change the router/access point settings.
I have no problem with domestic wireless, protected with WPA or WPA2 PSK. I've tested 2 different wifi.
I had no problem with Jelly Bean AOSP stock or Paranoid.
Any suggestions?
Maybe a different radio?
I really don't want to wipe and flash everything back the second time in a couple of days. It's frustrating.
Thank you in advance.
By the way, i think i've found a workaround: the problem seems caused by the fact that the access point in my office transmits using both frequency 2.4 and 5 Ghz.
This bug seems to affect the 5 Ghz.
So i went to the menu Setting > Wi-Fi > Advanced > Wi-Fi frequency band and i've changed from "Automatic" to "Only 2.4 Ghz".
Noe everything's working fine with the office's wireless and every other network.
the employer blocked the WIFI from employees (obtaining the ip address issue)
we cant access the WIFI in the hotel at where we work and although there are a password you put at the hotel's WIFI website but they did something lately to all of us and it is when any of the staff open the WIFI on his mobile it just keep showing obtaining IP address and no result so if you guys could help me in this and do i have to get a new phone or to try hiding my IP i tried a lot of apps but no way plz help
Related
All WiFi issues consolidated into 1 topic
[Q] Wifi signal?
Does anyone get a weak wifi signal with their Nexus S? Whenever I connect to my at home wifi I never get full bars and something I'll just randomly lose signal. Also it seems to go pretty slow. I used to have the Mytouch4G and it work flawlessly with the wifi. Anyone else having this problem?
damrong18 said:
Does anyone get a weak wifi signal with their Nexus S? Whenever I connect to my at home wifi I never get full bars and something I'll just randomly lose signal. Also it seems to go pretty slow. I used to have the Mytouch4G and it work flawlessly with the wifi. Anyone else having this problem?
Click to expand...
Click to collapse
OMG yesss I do.
Just about a room away I loose signal, almost completely. = 0
IDK, but I see more flaws every day that passes
Mine's been working fine over Wi-Fi. I'm pretty glad it does too, because my only data option with it is Wi-Fi..
Sent from my Droid using XDA App
Wifi has been working great for me. It reconnects automatically and doesn't drop. The signal seems on par with my nexus one.
Speed wise, is it on par with the 3G network?
[Q] Wifi does not work anymore after rooting :(
So, I unlocked my Android 2.3.1 and rooted it ... But if I click on wifi so I could connect to my modem it says Error and wont even search or anything. I tried reseting too but still no luck .. What is the problem and how to fix this ??
That's odd, I didn't have any issues with wifi as I connected to Android Market to downloaded ROM Manager during my rooting process earlier. Have you tried flashing a custom ROM on your device to see if it'll fix it?
No I didnt, would that work? .. A friend told me to install a new "kernel" but I dont want to overwhelm my android with custom made kernels .
your problem is you used one of the quick methods of rooting your phone, which used a kernel that wasn't from the exact rom you have.
if your on stock 2.3.1, you will need the stock 2.3.1 boot.img, and then you'll need to root it manually the long way via adb command line. search the nexus s development section for how-to's. they are all there.
i too had this problem, had to install MoDaCo ROM to fix it, but i dont regret rooting, i now have custom rom and over clocked cpu on the nexus s
you have two options, either to flash NANDROID backup to un-root and return to stock or install a custom ROM, i choose MoDaCo bcoz of its UI, it looks and feels just like the stock one.
golu12 said:
you have two options, either to flash NANDROID backup to un-root and return to stock or install a custom ROM, i choose MoDaCo bcoz of its UI, it looks and feels just like the stock one.
Click to expand...
Click to collapse
Yes, that's the point of MoDaCo roms, to make minimal changes to the look and feel of the phone, but to improve performance with his custom optimizations.
[Q] Nexus S wifi issue. Unable to access wifi from my nexus s.
Hi Guys,
I was able to connect to my wifi network for a day. I am using windows 7 machine as hotspot with connectify. From second day I am unable to connect to any wifi network. I did factory reset my nexus s but no results . Can some one help me how to solve this issue?
Observations:
*when i use static ip, It shows connected but the bars are in white instead of green color and i am unable to browse.
*When i use dynamic ip I am unable to connect to wifi. It shows obtaining Ip and never connects.
*In connectify when I was able to connect to wifi the device is shown with an android device name. but now the device is shown as unknown.
Sorry for my bad english, I m not a native english speaker.
[Q] Nexus S Wifi Settings - force close
Hi all,
Just got a new Nexus S - all was well at home. Took it to work today and noticed something very odd. It was fine until entering the wifi settings menu - at which point it dramatically slowed down. I got two 'not responding,close or wait' messages before being able to join the network.... all other settings are fine - just the wifi area.
Weird - wondering what could cause this... too many wifi networks broadcasting (am in middle of London)...?
Anyone seen anything similar?
Rich
rakh1 said:
Hi all,
Just got a new Nexus S - all was well at home. Took it to work today and noticed something very odd. It was fine until entering the wifi settings menu - at which point it dramatically slowed down. I got two 'not responding,close or wait' messages before being able to join the network.... all other settings are fine - just the wifi area.
Weird - wondering what could cause this... too many wifi networks broadcasting (am in middle of London)...?
Anyone seen anything similar?
Rich
Click to expand...
Click to collapse
Too many WiFi around you shouldn't cause that.
Try rebooting and setting again if you haven't already.
Hmmm - rebooted and still have the same issue. At home, or even a block away from the office it all works fine. But in the office itself, although it connects and uses the wifi fine, the settings page is VERY slow to load and gives me the wait/force close message.
Out of interest - I also have 'wifi analyser' from the marketplace. This too is very slow and unresponsive when in the office.
So - it is definately something to do with the wifi here.... but have not got a clue what. Before I join the wifi, or when I am physically somewhere else it all works fine.
Wifi is WPA-TKIP, the key is a very long jumble of letters but surely that is not an issue.
Strange eh!!!
Rich
[Q] Possible WiFi problem?
Hi there, just bought a Nexus S, also used to have Nexus One.
The thing is for some wireless networks even though I enter the password correctly, it says connected and still there is no connection at all. (I mean browser tries to connect but at the end it says page could not be found) I even tried with an ad-hoc network that I created with my laptop but still the problem exists.
At home I'm able to my network without a problem. The type of network I'm trying to connect is: WPA2 Personal with AES. Is there any known issue about AES at Android system? Afaik there is no way to change the encryption used right?
this might actually not be a nexus S issue.
some modems/switches/routers are configured to block certain devices/applications/package's
we have a modem and router with both wifi.
but my psp/nDS cant connect to the modem,but can connect with the router
kharikishan said:
Hi Guys,
I was able to connect to my wifi network for a day. I am using windows 7 machine as hotspot with connectify. From second day I am unable to connect to any wifi network. I did factory reset my nexus s but no results . Can some one help me how to solve this issue?
Observations:
*when i use static ip, It shows connected but the bars are in white instead of green color and i am unable to browse.
*When i use dynamic ip I am unable to connect to wifi. It shows obtaining Ip and never connects.
*In connectify when I was able to connect to wifi the device is shown with an android device name. but now the device is shown as unknown.
Sorry for my bad english, I m not a native english speaker.
Click to expand...
Click to collapse
i have a similar problem. My Nexus S connects to my router only within a few hours after a router reset. Then it stucks at "obtaining ip" and never connected before I do another router reset.
My home wifi is WPA2 type, and for WEP type wifi my NS never got connected.
I just flashed to jelly bean 4.1.1 on my verizon GS3. I can't get wifi to stay connected. It continuously rotates between "Authenticating", and "Saved, Secured". Eventually it gives up and just says "Disconnected". Anybody else having that problem?
skygirl said:
I just flashed to jelly bean 4.1.1 on my verizon GS3. I can't get wifi to stay connected. It continuously rotates between "Authenticating", and "Saved, Secured". Eventually it gives up and just says "Disconnected". Anybody else having that problem?
Click to expand...
Click to collapse
Probably wont help but try a different channel on your router. Change from "Auto" to something else. Are you using WPA2 security? Try removing the security settings (TEMPORARILY) as a test. Try resetting your router to factory defaults and set back up again.
In the end... sometimes certain routers appear to have connectivity issues.
My Netgear WNDR3400 can be very problematic
Galaxy s3 WiFi Authentication Issue
skygirl said:
I just flashed to jelly bean 4.1.1 on my verizon GS3. I can't get wifi to stay connected. It continuously rotates between "Authenticating", and "Saved, Secured". Eventually it gives up and just says "Disconnected". Anybody else having that problem?
Click to expand...
Click to collapse
I've had my Verizon Galaxy s3 for about a month without any wifi connection problems - until yesterday. It worked with my old router (Linksys) and several other secured routers (when visiting friends) with no problems. I installed a new Netgear WNR2000 in my system after the Linksys developed problems. I had the "Authenticating - Saved, Secured" rotation problem as soon as I tried to connect. For lack of any other ideas, I tried all of the encryption codes available on the Netgear - one at a time. When I got to WEP, it worked perfectly.
I called Samsung. The tech I spoke with said the WMR2000 is supposed to be compatible with the GS3. For the present, the solution is to stay with the WEP encryption. I intend to contact Netgear to see why I can't connect with their WPA or WPA2 options.
Hello.
So let's get straight to the point. I have a Samsung Galaxy Note 10.1 tablet with 4.1.2 installed. Since the new update, my tablet won't connect to schools network, which had EAP method TTLS and phase 2 authentication PAP. It doesn't need a User certificate, but we have a CA certificate.
Previously it worked flawlessly on 4.0.4 and on 4.1.2 for about a month, but then suddenly a weird error appeared. It says, "the password is incorrect". I tried modifying the network numerous of times, forgetting it and resetting the tablet, but none of it helped. I'm using the Wi-fi hotspot from my telephone to connect to the internet in school. I can assure, that there are no problems with the school network since all of my friends can connect to it (applies for every operating system) and the speed also isn't the problem, it's a 100/100.
I don't know if this is the right or wrong Category, but I look forward to every answer.
Best regards.
So since I got the Marshmallow update on my Moto G (XT1540) I am unable to connect to the WiFi at work, I have the correct SSID and password and it worked fine on Lollipop, but keep getting "Authentication error" now that I have Marshmallow. I have tried doing a Forget Network and rejoining it and doing a Network Reset in the Backup and Reset settings menu.
Our internal help desk and myself are puzzled by it isn't working... We have a fairly current Ruckus WiFi deployment, using WPA2 and EAS encryption. This WiFi SSID is specifically intended for employee's mobile devices, and no one else has reported any issues, but to our IT staff's knowledge mine is the first Marshmallow device attempting to access the WiFi.
Any thoughts, or any way to track down what the real cause is? Would a logcat show me anything?
BUMP
Anyone else having issues with WiFi since Marshmallow? I only have this issue at this one site, always the same Authentication Error and I know it is not the password (on my company issued iPhone I have deleted and added the WiFi network several times, so the password is correct). Our help desk is stumped. I am assuming this is related to encryption type (TKIP/AES) from the error. This worked fine on Lollipop...
acejavelin said:
BUMP
Anyone else having issues with WiFi since Marshmallow? I only have this issue at this one site, always the same Authentication Error and I know it is not the password (on my company issued iPhone I have deleted and added the WiFi network several times, so the password is correct). Our help desk is stumped. I am assuming this is related to encryption type (TKIP/AES) from the error. This worked fine on Lollipop...
Click to expand...
Click to collapse
I am always getting my mobile reboot when connected with wi fi on marshmallow
gopikrishnachowdaru said:
I am always getting my mobile reboot when connected with wi fi on marshmallow
Click to expand...
Click to collapse
Factory default... If problems continue, flash factory image or return to Motorola
Sent from my MotoG3 using Tapatalk
acejavelin said:
So since I got the Marshmallow update on my Moto G (XT1540) I am unable to connect to the WiFi at work, I have the correct SSID and password and it worked fine on Lollipop, but keep getting "Authentication error" now that I have Marshmallow. I have tried doing a Forget Network and rejoining it and doing a Network Reset in the Backup and Reset settings menu.
Our internal help desk and myself are puzzled by it isn't working... We have a fairly current Ruckus WiFi deployment, using WPA2 and EAS encryption. This WiFi SSID is specifically intended for employee's mobile devices, and no one else has reported any issues, but to our IT staff's knowledge mine is the first Marshmallow device attempting to access the WiFi.
Any thoughts, or any way to track down what the real cause is? Would a logcat show me anything?
Click to expand...
Click to collapse
Were you able to resolve? I had no wifi issue until today. I am in the process of changing routers and just installed a Linksys 1900ACS. When connecting my phone to wifi, it gets stuck on "Obtaining IP address". However, when I try to connect to the guest network, there are no issues.
Update: I wanted to keep WEP to avoid changing the settings in all my wifi cameras. But when I changed to WPA2 Personal, all worked. Don't know why WEP did not work as it did with my previous router.
MrTooPhone said:
Were you able to resolve? I had no wifi issue until today. I am in the process of changing routers and just installed a Linksys 1900ACS. When connecting my phone to wifi, it gets stuck on "Obtaining IP address". However, when I try to connect to the guest network, there are no issues.
Click to expand...
Click to collapse
No, we were not able to find a solution other than I connected to the guest network, which oddly is on the same APs, using the same encryption, just a different SSID and passphrase, which works fine. Can't explain it or find a solution, sorry.
I have updated from CyanogenMod 12.1 to CyanogenMod 13 SNAPSHOT (no nightly), OTA update, everything went fine, but WIFI at work, which is open with proxy login afterward, is not working anymore.
When trying to connect to that WIFI, the phone is stuck with: "Obtaining IP Address"
It was working correctly on CyanogenMod 12.1. It is working with any other device, so no issue on the WIFI itself.
I tried to Wipe/FactoryReset (TWRP 3.0.0) and reinstall CyanogenMod 13, but still the same issue.
If I check logcat:
03-22 10:05:20.862 5779 11137 D DhcpClient: Broadcasting DHCPDISCOVER
03-22 10:05:29.052 5779 11137 D DhcpClient: Broadcasting DHCPDISCOVER
Any other WIFI (home WIFI with WPA) is working correctly.
Are you experiencing the same issue?
Any solution for that?
I am stuck, I think I have to come back to CyanogenMod 12.1...
Thanks!
I am having the exact same issue
WIFI says no internet but has internet Marshmallow install,
After installing Marshmallow and GAPS 6.0 TWRP 3.0.0.0 I'm getting the WIFI display problem. First, The WIFI notification does not show up/down arrows like it used to when reading/writting data. Second, in Settings on WIFI screen when connected it says no internet. Internet is working in Firefox and google play just fine. Tried to reset the router with the instructions from other post, no change. Tried the forget, reboot, re-add, no change. changed setting in developer network section, Aggressive WIFI to Cellular handshake, no change and all the other stuff in that section and still no change. At least I'm getting on the internet. Someone let me know when there is a fix?
I fixed this by using the legacy dhcp client (one from android 5.1), you can enable it in the developer settings, where you enable adb. The marshmallow dhcp client is very buggy when connecting to public wifi.