Am I the only one who, since updating to 4.2.1, has problems connecting to the net via WiFi? The antenna symbol shows it's connected, yet I don't get a Data IP address, so subsequently am not connected to the internet.
Am I the only one who, since updating to 4.2.1, has problems connecting to the net via WiFi? The antenna symbol shows it's connected, yet I don't get a Data IP address, so subsequently am not connected to the internet.
I have the same as this but I've had it to differing degreees ever since I got my iPad with 3.2. I've also tried all sorts of router config, static IP address, hard coding the Google or OpenDND DNS server, etc.I have issues with my WIFI since updating but they seem different to yours. In my situation, the internet will work fine bu periodically the ipad will be unable to reach aky websites unless i renew my DHCP lease in network settings. In my router config ive even set up a permanent lease or disabled DHCP and used a static IP but to no avail. I didnt have this issue prior to updating.
I have the same as this but I've had it to differing degreees ever since I got my iPad with 3.2. I've also tried all sorts of router config, static IP address, hard coding the Google or OpenDND DNS server, etc.
I also have Filebrowser from Stratospherix on my iPad (http://itunes.apple.com/gb/app/filebrowser-access-files-on/id364738545?mt=8) which I use to access files on my NAS and when access to stuff on the internet dies (just like you are describing) I have found that I can go straight to FileBrowser and mount my NAS and it connects immediately and at that point I can immediately switch back to my browser or the AppStore or whatever it was that just locked up on me and at that point I then have connectivity back (for a few minutes, before it dies on me again). The network stack seems to get "clogged up" in some way and just the process of doing the NAS mount in File Browser seems to unclog it for a while. It's very wierd.
This is why I played quite a lot with trying other DNS servers because the fact that File Browser always had network capability to do the mount made me wonder if it was something in the DNS resolution that was breaking since my NAS is defined to my iPad via an explicit IP address. Maybe I need to write down an IP address for a big site like www.google.com and the next time I get a lock up in the browser then I'll try to immediately access it via a direct IP address and see if that works which would also point the finger at the bit of the WiFi stack that is breaking being DNS.
- Julian
Very interesting. That does seem to support what I'm seeing. Basic IP transmission remains just fine, it seems to be something somewhere in the DNS lookup or DNS cache corruption that is hitting us here.When it happened I pointed safari to the router's admin screen (192.168.1.1) and immediately switched back to the offending website and it started responding again. Very strange issue, but I have loads of different gadgets here, and only the iPad has the problem so I think it's to blame here.
One other thought. If you bookmark 192.168.1.1 then maybe you've at least got a slightly faster way of recovering the connection when it locks up! I might do that myself....When it happened I pointed safari to the router's admin screen (192.168.1.1) and immediately switched back to the offending website and it started responding again.