Honestly I have no idea why this is happening on my android 4.0+ devices. I will get stuck on obtaining IP address connecting to certain networks and the only thing that worked for my home network is static IP. But for instances when I don't have access to the router to know what the static IP should be, is there a way to get this working? This happened on my phone as well. I was at a local cafe which had wifi and before I upgraded my samsung galaxy s2 to ICS, I could connect to their wifi no problem, now it has the same issue, and so does my Nexus 7. I don't know what to enter for static IP, I entered some random IP, it connected but internet still didn't work. Why is this problem plaguing ICS onward, and does anyone have a workaround when static IP is not an option?
This is definitely not a universal problem (I've never heard of it before). Are you running stock roms? If not, then do you have these problems with stock roms?
C2Q
Why are you posting this to multiple threads?
There is no "proper way" to use a static IP for a router that is setup for DHCP only. For routers that use both, many times the static IP's are reserved for specific devices.
Sent from my Nexus 7
Because I didn't notice the other thread before I posted this one. Anyway then why is this obtaining IP address loop a problem on ICS? As I said, my phone on GB would manage to connect/obtain an IP address just fine before I upgraded to ICS. This happened with my home router and other areas as well. The solution that worked for me at home was to assign a random static IP within my routers IP range. But if I don't know the gateway IP this won't work. So what gives? I'm kind of confused what you mean by routers set up for DCHP only. If I use static or DCHP options on the android device to connect, they will both work (this was before ICS).
I ran into similar issues with my nexus 7 and my work open wifi. It needs you to connect to a web login page where you accept a use policy before you can surf. My nexus would connect but never redirect to that login page.
The issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Changing those settings lets me finally use my work wifi. My phone also has the same issue (its an ICS phone, whilst the nexus is jelly bean) but is not resolved with this change.
Sunburn74 said:
the issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Click to expand...
Click to collapse
Sure that is not 8.8.4.4 ?
Thanks for posting this question. I have exactly the same problem with my Samsung S3 (ICS) and Nexus 7 (Jellybean). My old Samsung S2 (Gingerbread) worked fine.
I am trying to connect to a hotel open network. When I try I get the looping "Obtaining IP..." message. I have a strong network signal.
What gives? How come earlier versions of Android worked but later ones don't?
As the OP stated, the static option works insofar as I can then connect to the network but the made up static IP numbers do not actually let me download (or upload) data. As the OP wrote, you need to know some valid values for the static IP setting.
Does anyone have a solution for this (apart from downgrading to Gingerbread)?
Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
BT routers always start with 192.168.1.254 so there's another option dunno why my devices do it but im used to it. My Wifes Xoom 2 and wildfire S are stock and do not have the issues my rooted ones do but i have just put it down to coincidence
First off. Is your modem in service? Do other devices connect? Have your restarted your tab? Does it connect to other networks? Meaning going to another WiFi hotspot If you can answer yes to all of these questions we move on....
What modem/router are you connecting to?
What type of WiFi encryption are you using? Wep-open, WPA, wpa2-psk
On the tab does it fail to obtain the IP address? Meaning it says "remembered"?
Not going to lie more the 3/4ths of the time you have the wrong WIFI PASSWORD. CHECK IT AGAIN usually its on the modem/router or if you have no clue here is a hint: on windows vista and windows 7 under control panel>network and sharing center>manage WiFi networks if your right click on the network name such as "Ilovepancakes"and go to properties it will have a security tab that you can click on and show password.
Sent from my Nexus 7 using XDA Premium HD app
bonesy said:
Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
Click to expand...
Click to collapse
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.
Did you dirty-flash your Nexus? A while back my Gnex wifi connections would take longer to complete the handshake. I did a factory reset/fresh install & it has been much faster.
strongergravity said:
Did you dirty-flash your Nexus?
Click to expand...
Click to collapse
My Nexus (and GS3) is completely stock (I have only added a launcher).
This problem seems to be caused by older routers, which don't seem to like something about newer versions of Android.
I'm not sure if it's something Google can fix, but the combination of old router and new Android seems to make logging onto wi-fi networks a problem.
Bump.
Ive been struggling with this problem for a week now since getting a transformer infinity. My s3 gets stuck when I try to connect to it. The tab cycles through connecting, obtain a valid address and saved.
I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Sent from my Nexus 7 using xda app-developers app
Warrior1975 said:
I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Click to expand...
Click to collapse
This worked for me also (Infuse 4G on JB), but it seems like this is only a problem on WiFi AP's that have marginal signal strength, even though they appear to have full bars. I personally have never have seen this issue on a network that was performing properly.
Same here!
Same thing is happening to me! Im using he htc desire c running ics.. my phone detects the wifi network, shows that it has excellent strength, but it gets stuck at "Obtaining IP Address"! My friend and I both bought the same model a couple of weeks earlier and till now neither of us have been able to connect to a wifi network! Please Help!!!
its a DHCP bug
This is probably not a problem with your network configuration unless it works everywhere else; im having the same problem as well as other people i know and its definitely a bug with DHCP, so the only way to work around this is by using a static ip as far as i know
bobbyelliott said:
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.
Click to expand...
Click to collapse
What he's saying is that most routers will begin assigning addresses starting with 192.168.1.1 or 192.168.2.1 for itself (you can access the router configuration page by typing in this address into a web browser), and then increment upwards afterwards. If you knew that the router started its DHCP addressing with 192.168.1.1, for example, you could try 192.168.1.2, and so on and soforth.
If you did a "dirty" upgrade, I'd recommend doing a factory wipe (after an appropriate backup-- there are some good apps out there that can handle this). In-place OS upgrades have a bad habit of being finicky. Android is also generally less tolerant of network "misconfigurations" than, say, Windows, OS X, or iOS. Many networks that use captive portals (your standard coffeeshop Wi-Fi) deliberately use an altered network setup to support their access policies, such as a captive portal.
However, with the exception of corporate/enterprise networks (which may require fine-tuning because of increased security), you really shouldn't be messing around with this if you don't have at least a rudimentary understanding of how networking works. That's not meant to be insulting, but when people plug in random values and find it doesn't work, it tends to lead to more frustration than utility.
(fyi: The reason you can "connect" by tossing in a random set of octets your your IP and DNS is because you've properly authenticated against your router, but you'll never be able to receive data unless your router's DHCP lease lines up with your self-assigned IP, because the router never handed that address out to you. It's the digital equivalent of building a mailbox in front of your house without registering with the post office, and wondering why you never get mail).
Hopefully this will help others.
My N10 stock 4.4, I put PPP Widget on and it appeared to not work, initially it was "no driver found", on searching the forums it was basically "tough". To make it works involves:
The stock kernel from Google in 4.4 does not support PPP. Pick another kernel which does support PPP. Examples are tce-manta-krt16s_3_boot.zip. Many do.
Disable Wifi before you connect, or have a Wifi static setting with an Internet-visible DNS server IP (e.g. 8.8.8.8). This is because PPP Widget on stock 4.4 will use the DNS settings from your Wifi, not over-write them when using the dongle, which in most cases won't work as they are the Wifi router itself's own LAN IP which is not accessible when on the 3G/4G dongle. If you don't want to disable Wifi then go to your router and make it offer up an Internet-visible DNS IP address.
It will "connect" but not show any signs it is actually working, but it is.
I'm very pleased I got my Nexus 10 on both Kitkat 4.4 and get online with 4G dongle
I'm on PAC kitkat but it didn't work with rom kernel. The kernel you mentioned does work with multirom?
I did a clean flash, but cannot connect internet through wifi. There wasn't such problem before lollipop.
Other devices connect without problem.
Chrome says DNS_PROBE_FINISHED_NO_INTERNET
Mobile network works fine btw.
What might cause that?
halloga said:
I did a clean flash, but cannot connect internet through wifi. There wasn't such problem before lollipop.
Other devices connect without problem.
Chrome says DNS_PROBE_FINISHED_NO_INTERNET
Mobile network works fine btw.
What might cause that?
Click to expand...
Click to collapse
Is it happening with all WiFi networks that you are connected to? Because it seems related to the DNS configuration.
speedsys said:
Is it happening with all WiFi networks that you are connected to? Because it seems related to the DNS configuration.
Click to expand...
Click to collapse
No, only University's WiFi
I have the same, really annoying problem.
I use a local DNS to resolve my LAN name server, but the device on Android Lollipop never use the Local DNS and it ends with a 404.
I use "Fing" / "Ping and DNS" to do my network test, it says the hostname can't be resolved... and the DNS used is one on IPV6 (2a01:e00::1)
I have a lot of applications inside my private domain ( *.dk.lan ) managed by a bind9 / dnsmasq (I have tested both) server on Raspbian, and all was pretty good with Kitkat and lower (and on Mac OS / Linux )...
I have 8 devices, 5 on Lollipop with this problem and 3 on kitkat without it.
Some thread seems to appear on Internet about this kind of problem...
And, after investigation, it seems the Android Lollipop device use an Ipv6 DNS name resolver instead those send by the DHCP server...
If you have an idea... I'm listening !
About this problem, I've opened a issue on the Android tracker : https://code.google.com/p/android/issues/detail?id=79504
I've been investigating this issue and it's seems that it's a kind of problem on how the OS stores the DHCP parameters.
If you try to make static the same configuration in my case it takes a /20 (255.255.240.0) network like /29 (255.255.255.248) ..... and this doesn't happen if the network it's the ussual /24 (255.255.255.0)
Not fixed in 5.0.1
Finally fixed in 5.1
Hi, i have my Samsung Note 4 phone and O.S. ver. 5.1.1 stock firmware, no root and build N910FXXU1COH4.
I've noticed problems on Google Search, Facebook and upgrading on Play Store when I'm connected to some wifi network.
Recently I configurated at my friend a station to receive Internet connection (Adsl) from his brother and I installed him a TpLink Cpe and an access point with ddwrt software installed.
Then...my Note 4 has the problems I said and pc, Samsung S3 Neo and another Samsung work regurarly for all apps, upgradings and searchings!
I don't know why I have this issue in my Note 4!
I configurated the Cpe setting as dns (not obbligatory) the ip of his brother's router connected to internet.
I tried to insert 8.8.4.4 with static ip but I don't fix the issue.
P.e.: i noticed that the issue is caused by upload that is about 0 Kb/s and others devices don't have this issue.
Do you know why?
I also upgraded my stock firmware to COJ3 but i haven't solved the issue...[emoji53]
Sent from Note 4 device - Rome - Italy
From what I can understand there is an issue with Lollipop where if it sees IPv6 on your network it will always try to do DNS over IPv6, even if its not actually functional. As such, DNS completely breaks when using IPv6 capable routers (guaranteed if you run DD-WRT, OpenWRT, pfSense, etc) if you do not have IPv6 support enabled on your Internet connection.
I ran into this myself recently as I was trying to disable IPv6 on my network as it was not fully functional, but it completely broke connectivity on my Note 4.
The March security update seems to have made this worse, as even after restoring partial IPv6 I can now do DNS but actual connectivity still fails instead of falling back to IPv4 like its supposed to.
Alex Atkin UK said:
From what I can understand there is an issue with Lollipop where if it sees IPv6 on your network it will always try to do DNS over IPv6, even if its not actually functional. As such, DNS completely breaks when using IPv6 capable routers (guaranteed if you run DD-WRT, OpenWRT, pfSense, etc) if you do not have IPv6 support enabled on your Internet connection.
I ran into this myself recently as I was trying to disable IPv6 on my network as it was not fully functional, but it completely broke connectivity on my Note 4.
The March security update seems to have made this worse, as even after restoring partial IPv6 I can now do DNS but actual connectivity still fails instead of falling back to IPv4 like its supposed to.
Click to expand...
Click to collapse
Thank you my friend. I read only now your message..
I don't know if we have the same problem.
Now my phone is going with the latest MM stock firmware and I have always the same problem..
Some other phones work good except someone..
I don't know if it's a issue about IPv6 but I can ensure you that I linked all phones in same way to wifi but their behaviour is absolutely different related those apps..
So .. i was Using Custom Rom of the S5e for Quiet a while.. but i noticed this.. Our Router is set that New Devices that where never in the Network before can't Login to WIFI.
So after a Rom Update.. the Tablet has no WIFI.. so we always have to Open The Router Back up to Enable All Devices.. Connect it again and Close The Router again.. then.. it works.. you have todo this always after an Update like.. the Tablet always assign's a New IP-Adress sort of.. witch Sadly made me go Back Stock what i usally don't want.
Want to use LuisRom or LineageOS instead.
I had the Issue a while ago with the: Samsung Galaxy Tab A (2019)
And never with other Manufactures Devices.. is this a Known issue on Samsung Devices if you use a Custom Rom?
Is it maybe Fixable?
Could it be a combination of the randomised MAC setting being enabled on the tablet, and MAC filtering of some sort on the router?
If it has a random MAC address each time it connects, the yeah, the router will treat it as though it's a different device and assign a new IP address to it
I went from stock 10, to lineage 18.1, then to stock 11,and can't say that I saw anything like this happen.
GioCustomROM said:
Is it maybe Fixable?
Click to expand...
Click to collapse
If I am understanding your issue, it's because the tablet's MAC address is changing. This is normal and is done for security, but you can change it.
- This is not on by default, but double check it. Under developer options (you can search for "mac" in settings it will bring this up) "Wi-Fi-enhanced MAC randomization". Make sure this is off. Otherwise your MAC address will definitely be different every reboot.
- Next under Wi-Fi Mac address in About Tablet under each saved network there is a "Privacy" option, by default it is set to use randomized MAC, you can change this to use "Use Device MAC" for your home network. You'll likely find this fixes your issue.
Note these instructions are for Lineage, but they should be similar for other ROMs? At least get you started.