Related
I've had the captivate about 24 hours now and dig it. I've rooted it and remove the att bloatware (per titanium backup), I've also performed a backup using Rom Manager.
I'm having trouble getting it up and running on an enterprise wireless what uses 802.1x PEAP authentication. I can get through all the auth. steps, and the device is assigned an IP, but I am unable to do anything that requires an internet connection; browser, market, etc.
Has anyone else ran into this issue?
*****EDIT*****
sigh i just realized that this is in the wrong area, it should have been over in development...i'm an idiot
I had a similar problem on a WEP-encrypted network, which I fixed by setting a static IP on the phone and then setting it back to DHCP (the correct setting). However, your problem could be entirely different than mine (not that I even am sure what my problem was, just that I fixed it!)
Best of luck!
Having the same problem on enterprise access points regardless of encryption. Home wifi netwroks work great (open and WPA2). Enterprise APs (open and WEP) connect and give me an IP, but will not transfer data. Think its a driver issue with the Wifi, it happens on every captivate ive tested, and seems to be more widespread than the GPS issue.
I have had the same issue with my work at work. I can get it to connect and get a ip but can not pass any data.
Sent from my SAMSUNG-SGH-I897 using XDA App
Had the same problem at work. Luckily I'm an admin and figured mine out. Our monowall portal was the issue. I can give a detailed answer for my problem tomorrow when I get to work.
I actually had the cap wiped to go back, then I literally figured out the problem. Thanks go out to my team mate for helping me talk through this.
Sent from my SAMSUNG-SGH-I897 using XDA App
can't wait to hear what your fix was!
Sent from my SAMSUNG-SGH-I897 using XDA App
This sounds more like your network not being allowing your device rather then the device having an issue.
it's been frustrating as I know two other guys with android devices that didn't have an issue. one is a droid eris running 2.1 and the other is a nexus one running 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App
designgears said:
This sounds more like your network not being allowing your device rather then the device having an issue.
Click to expand...
Click to collapse
Worked closely with my highly experienced network admin in my dept. for an afternoon (we had some time to kill). He checked the firewall and dhcp servers, ran packet traces, etc.
With what I'm experiencing, its the device. These wifi networks we use with Cisco APs are completely wide-open. All other phones and mobile devices have always worked great for years. We rely on this network for many custom applications and mobile tools.
Once the dhcp server leases an address, it seems like the radio stack hangs, and the device ceases communication. Here's an older thread on the exact issue over at androidfouroms: http://androidforums.com/samsung-captivate/130403-wifi-terrible.html
I have tested multiple new unmodified captivates and the issue is identical accross the board.
Now that I am at work, and have coffee in me and not beer, I will go through the problem I had with miCap and works wireless. Due to my skeptical ways, I will be semi vague for security purposes. On with it.
When I originally got miCap (pet name for it) I was able to access our public wifi. It allowed me into the public portal to agree to terms. I played a little bit on it, but wanted to see if I could access our private wifi. I got in the private no problem. But after that I never was able to get back on to our public. It did the same thing as I've read. It got an ip no problem (via dhcp) and acted like all was well. No browser, or ap could get a connection. The phone would not switch over to 3g to get info.
Armed with ip and mac address, my co-worker and I started to did through our monowall. ( He also has a cap that had no issues on public or private). We try tried reserving the ip for miCap, didn't work. We tried static ip, didn't work. I spent the morning completely wiping miCap to get it back to return worthy.
This was when I decided on last ditch effort.
Our ap's are cisco's that connect into monowall. I got into monowall and dug around. I found that with in the captive portal (how fitting) that the ip/mac associated with my phone hadn't checked in for 8 days. Even though I tried everyday. I deleted the entry to the phone there and suddenly my phone was getting access again.
Now I understand that this may not help everyone, because setups vary from place to place. But digging deeper into configurations at the access points may be what is needed. Do I think the phone had nothing to do with it? No, I think it helped aggravate the problem.
We have had problems with the Intel 3945abg chipsets with the same exact setup. That problem was fixed with driver updates on the laptops.
sorry for the long winded reply.
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Pmac25 said:
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Click to expand...
Click to collapse
Essentially yes. But it is not listed like that in the portal. Hmmm. I wonder about the combo of dhcp/dns being the culprit.
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
I sent a help ticket into samsung; maybe if enough folks do we can get it on their radar.
jhannaman82 said:
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
Click to expand...
Click to collapse
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
phlunkie said:
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
Click to expand...
Click to collapse
Thanks for that, i figured the menu was built in somewhere just never found it.
:thumbsup:
UPDATE
So I flashed the i9000 Eclair rom last night, and when I got into work today I can connect and use the wifi here. So looks like something AT&T buggered up, big surprise there, when they "customized" the captivate.
As much as I normally love blaming AT&T for problems, that can't be done here. My Captivate (running Stock Firmware) connects just fine to my work network. We use 802.1x with PEAP/MSCHAPv2 for authentication.
Anyone been able to connect at over 802.11b speeds while connected to an 802.1x network? I show connections at G and N speeds on my WPA2 network but nothing over 11Mbps on 802.1x.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi,
I am also having problems with my work wifi network.
It is 802.1x, on TTLS/PAP it also requires a thawte premium server ca certificate insalled.
Is there any way to connect this kind of networks?
With my previous iphone 3g it was taking only 4-5 seconds.
My WiFi was working fine on my Xoom, and now it gets stuck while "obtaining IP address." It says for a split second "remembered" as if it was connected and starts the ongoing circular process of "obtaining IP address" all over again. I saw that galaxy tab users had this same problem and found a resolution by connecting "static" instead of "DHCP." I didn't try that as I honestly don't know how. What I do know is that there are a few devices like my OG droid, my laptop, my mothers' laptop, my xbox 360 that are connected to the same WiFi network. This randomly happened, when I decided to disconnect from WiFi to run a speed test on 3G and I was unable to connect to WiFi ever since. I tried unplugging/plugging the routers, turning the Xoom off and on, and even went so far as to doing a factory reset on the Xoom and I still can't connect. 3G works fine, but I have a 1GB cap and I would rather only use that while I'm on the go, and obviously WiFi is definitely faster. If I can't resolve this, I still have enough time to return this thing. Call me a newb, but I need a little help!
I know you said you did a factory reset, but google stores wifi passwords in the cloud now. Try making the xoom forget the network you're trying to connect to.
My only other thought is that you need to go into your router's configuration and remove the xoom as a remembered device.
Bauxite said:
I know you said you did a factory reset, but google stores wifi passwords in the cloud now. Try making the xoom forget the network you're trying to connect to.
My only other thought is that you need to go into your router's configuration and remove the xoom as a remembered device.
Click to expand...
Click to collapse
How do I get the xoom to forget the network? How do I remove the xoom as a remembered device? Sorry but I really don't know how to do that..
EDIT: I went into settings>privacy>backup and restore> and unchecked "back up application data, Wi-Fi passwords, and other settings to googles servers and was still unable to connect.
I think if you long press on the wifi network it will give you the option to forget it.
As for the router, do you remember setting it up? The settings pages where you set the wifi name and password and such.. it should have a section where it tells you which devices are connected.
I have pressed "forget network" on the xoom several times when trying to connect. As for the router, do I remember setting it up? No, as a matter of fact I didn't set it up. Could I configure this thing from my laptop?
droiduser1988 said:
I have pressed "forget network" on the xoom several times when trying to connect. As for the router, do I remember setting it up? No, as a matter of fact I didn't set it up. Could I configure this thing from my laptop?
Click to expand...
Click to collapse
Of course, anything that's connected to the router should let you configure it. It's too complex to explain here, but you need to enter the router through it's IP address and find the configuration.
Find the manual for the router you have and go from there.
I'll try to look into that, any idea as to wtf happened? This is beyond an inconvenience..
I'm having much the same problem. After entering the passphrase it says 'obtaining ip address from....' and thats all. It never connects??? I have tried 'forget' several times and no luck.
I have been able to connect to unsecured wifi with no problems.
Use the free app "wifi static". Config to assign you a static IP on that network only and dhcp on others. Its something within android as I have the same issue in my phone with a few networks but not most.
Sent from my Xoom using XDA App
jcampbell037 said:
Use the free app "wifi static". Config to assign you a static IP on that network only and dhcp on others. Its something within android as I have the same issue in my phone with a few networks but not most.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
OK, tried it. NO GO! After entering the passphrase it STILL says 'obtaining ip address from....' I may be doing something wrong with the app since it comes with absolutely NO directions. If this is going to be an issue average folks will take it back!
Have any of you with this issue verified that the DHCP scope on the wireless network is not full or that DHCP is even allowed? The fact it works one place but not another tells me the issue may be with the network and not the device.
Dave
Sent from my Xoom using XDA App
I was having the same issues as you originally at first until I reset my router and my Xoom.
Sent from my Xoom using XDA App
je2345 said:
I was having the same issues as you originally at first until I reset my router and my Xoom.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
I also had this issue, I ended up fixing it by upgrading my router BIOS. the version that was on there was dated 2004 (yikes), and though the most current update was only 2006, it seems to have fixed the problem.
That or the reboot after the update as previous poster said and the update didn't really have anything to do with it, but either way it got fixed.
Hello everyone, I really need a help here.
I was on a MIUI GB ROM and bought a wifi router Tplink WR74ON. After a few days I could not access google.com, bing.com, ask.com... and YT behaved strangely. But I could access czech domains and "anything.google.com", which leads to google.com/anything, so no help. Oh and the Play store had no connection. Google.cz works until I perform a search... then No connection !instantly again.Yahoo and a lot of smaller sites work. I tried stock browser and Opera mobile.
So I flashed MIUI Scotland 4.0.4 and after a few hours the problem is here again. Restart of anything does not help, on notebook there is no problem and the router is set out of the box, no special settings of any kind. It pings google.com with no problem.
If anyone has any idea.... thank you.
And it seems that I can connect to google via IP address...
Huh solved... apparently there was a DNS problem, I had to bypass the router and set public DNS.
Nice of you to give us the solution .
Sent from my GT-I9000 using xda premium
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).
There appears to be a problem with new versions of Android and old routers. Many people have reported the "obtaining IP address" loop problem.
Let me explain. I use the leisure facilities in a local hotel. It has a public (open) wifi network. I believe it uses an old router. My Galaxy S2 (Gingerbread) and AsusTransformer (ICS) both connected to this network without problems. I recently replaced the S2 with an S3 (ICS) and my Transformer with a Nexus 7 (Jellybean). Neither of my new devices connect to this network. I have had the same problem in a local cafe.
I have researched this problem. It is not uncommon. It appears to be caused by an odd mix of hardware (router and wifi chipset) and software (later versions of Android). If you are unlucky (like me and some others) you will be unable to connect to some networks.
The solution is to use static IP addressing (since your device is unable to obtain a dynamic IP address). This will allow your device to connect to the network -- but you need to know the correct settings (for static IP addressing) before you can actually use the network.
This problem has been reported by many people. Does anyone know if there is a fix or a workaround?
The only one I can think of it to get hold of a device that does connect to this network and copy the (static IP) settings. But this would only solve it for one location meaning that I will run into it again the next time I try to connect to a network with old hardware.
Sometimes when I get that problem it's due to IP address conflicts on the Windows 7 computers.
I go to the computer and:
http://helpdeskgeek.com/networking/release-and-renew-an-ip-address/
Otherwise I just pull the router out and refresh it, should work for another few weeks or so.
Asovse1 said:
Sometimes when I get that problem it's due to IP address conflicts on the Windows 7 computers.
I go to the computer and:
http://helpdeskgeek.com/networking/release-and-renew-an-ip-address/
Otherwise I just pull the router out and refresh it, should work for another few weeks or so.
Click to expand...
Click to collapse
I don't have access to the PC. It is owned by the hotel. I need a solution that I can apply client (Nexus) side.
Solution
I found a solution. I asked the guy to reset the router and both my Nexus and S3 immediately connected. Someone advised me to do this. I have no idea why it worked. Not really a solution since i cant go round cafes asking people to reset their routers for me.
Is there a way to find out IP, DNS, gateway etc values on Nexus when they are dynamically assigned?
I sometimes have this Problem when starting my accesspoint after enabeling wifi on my N7.
I have to reboot my N7 in that case to get an IP.
Happened to me quite a few times when I went out with it to a restaurant or something. It just loops and loops.
My Nexus (and S3) now connect to the hotel network every time now. So it looks like you only need to ask the owned to reset his router once.
Embraced with this problem
bobbyelliott said:
My Nexus (and S3) now connect to the hotel network every time now. So it looks like you only need to ask the owned to reset his router once.
Click to expand...
Click to collapse
Resetting the modem solves the problem if you don't make any change to the router settings. I don't understand why the hell google is not solving the problem yet...
many users are found to face the same problem..
eve I can connect with my Nokia E72 but not with my N7...
I can get the IP from my cell phone. But come on, what's the point of doing so?? Are you gonna assign the IP for each and every WiFi you connect?? Or if the IP changes everyday??
Static ip won't help, yes you can connect to wifi, but cannot get connection to internet. This is a bug of android, and ITs in Princeton univ. had some investigation. 412 should have fixed it
Sent from my HTC Z710e using xda premium
gcd0318 said:
Static ip won't help, yes you can connect to wifi, but cannot get connection to internet. This is a bug of android, and ITs in Princeton univ. had some investigation. 412 should have fixed it
Sent from my HTC Z710e using xda premium
Click to expand...
Click to collapse
no. The same problem with 4.2.1 on my N7. God,this is really pissing me off !
EDIT: Finally found a solution . Thank god!!
TheDarkDefender said:
no. The same problem with 4.2.1 on my N7. God,this is really pissing me off !
EDIT: Finally found a solution . Thank god!!
Click to expand...
Click to collapse
What was the solution?
bobbyelliott said:
Is there a way to find out IP, DNS, gateway etc values on Nexus when they are dynamically assigned?
Click to expand...
Click to collapse
For a simple display of the values look at something like Network Signal Info of Wifi Analyser (both free)
jet1000 said:
What was the solution?
Click to expand...
Click to collapse
Use a static IP .
Sent from my Nexus 7 using xda app-developers app
You can only get internet access when you'll be using the correct IP, DNS etc. So try to find out what is the working IP setting...
Sent from my Nexus 7 using xda app-developers app
Deleted
I just started having a similar problem. I have a samsung galaxy tab with Sprint. I've had it for a year and this is the first time I've had this trouble.
The only difference is, I cannot connect to any wifi network at all. It keeps hanging on "obtaining IP address" and then disconnects. It doesn't matter if it's my home wifi or school or free wifi in a restaurant.
The only possible connection I can make is that I downloaded Lookout to check it out as a possible security app, I have since uninstalled it but that did not fix my problem.
Continuing to research this but any ideas on how to fix this would be fantastic.
I'm having this problem on my HTC One S. It happened yesterday without warning and it's really annoying. I went to a nearby cafe and the wifi worked perfectly, so it's something wrong here.
Static IP solution connects to me to the network but I can't actually use the internet, so I'm stumped.
i'm getting the same error with AOKP 4.2.2, and also know people with stock 4.2.2 with it.
the only way i found to fix it is to reboot the phone..... and wait for it to happen again and reboot it again
i cannot use static IP since in my university (and some other public places) it is not possible to connect it like that :S
TheDarkDefender said:
no. The same problem with 4.2.1 on my N7. God,this is really pissing me off !
EDIT: Finally found a solution . Thank god!!
Click to expand...
Click to collapse
How did you solve this? I Need help with my tf 300
bobbyelliott said:
There appears to be a problem with new versions of Android and old routers. Many people have reported the "obtaining IP address" loop problem.
Let me explain. I use the leisure facilities in a local hotel. It has a public (open) wifi network. I believe it uses an old router. My Galaxy S2 (Gingerbread) and AsusTransformer (ICS) both connected to this network without problems. I recently replaced the S2 with an S3 (ICS) and my Transformer with a Nexus 7 (Jellybean). Neither of my new devices connect to this network. I have had the same problem in a local cafe.
I have researched this problem. It is not uncommon. It appears to be caused by an odd mix of hardware (router and wifi chipset) and software (later versions of Android). If you are unlucky (like me and some others) you will be unable to connect to some networks.
The solution is to use static IP addressing (since your device is unable to obtain a dynamic IP address). This will allow your device to connect to the network -- but you need to know the correct settings (for static IP addressing) before you can actually use the network.
This problem has been reported by many people. Does anyone know if there is a fix or a workaround?
The only one I can think of it to get hold of a device that does connect to this network and copy the (static IP) settings. But this would only solve it for one location meaning that I will run into it again the next time I try to connect to a network with old hardware.
Click to expand...
Click to collapse
Note: You Must have root.
Go to
/data/misc/dhcp/
and delete all 3 / 4 files there.
And voila it should work.