Has anyone else had problems with name resolution on Wifi networks?
On 3G I can browse to any site and it works fine. As soon as I connect to my Wifi network I am unable to connect to anything (websites, Play, email etc.) The only way I can connect is if I connect directly to the IP address of the site (not the DNS name). I'm getting an IP address on the Wifi network via DHCP, but have tried manually specifying IP, gateway and DNS with no luck. (I've actually tried manually specifying my own DNS, and Google's DNS server) Looking at the DNS server logs it doesn't appear that the S3 is even querying the DNS server.
Other devices on the same network (multiple iDevices, Macbook, XBox 360 etc.) all work fine.
It has worked for the past 6 or 8 weeks (as long as I've had the phone) but stopped working a few days ago. I was running stock firmware, unrooted. Since the problem appeared I have updated to the recent JB leak and XXLH1 modem but it has made no difference.
Any ideas?
Please ignore. I managed to resolve it but I have no idea what the original problem was or why the fix worked.
I manually changed the IP address to a different valid address within the subnet and it fixed it. The original IP address is not in use anywhere else on the network. I've now created a DHCP reservation using the new address and it's working fine.
Related
As a newbie with basic tech knowledge I will try to explain the problem as best I can.
Our office wi-fi has an internal DNS address that is not assessible externally. When exchange email is set up using our external DNS, email service works perfectly on 3G service. When the phone connects in the office to wi-fi we can't figure out how to set the internal DNS setting.
If we set the email server to the internal DNS setting, it works great on wi-fi in the office but does not connect via 3G. On a computer we can adjust using a host file to search for both options.
This is a stock phone. Is there somethig we are missing in set-up?
Thanks in advance.
Is your access point configured to issue addresses via DHCP ? If so then push the internal dns address out via that and resolve the server name to its inside address.
sdunne said:
Is your access point configured to issue addresses via DHCP ? If so then push the internal dns address out via that and resolve the server name to its inside address.
Click to expand...
Click to collapse
I'll pass this on to my IT admin to see how our server is set up. Thanks for the tip, especially given it is your first post. Much appreciated.
I'll keep you updated.
Our address is static.
If I turn off wi-fi, email comes in fine over 3G with the external IP address. If I turn wi-fi on, it doesn't.
If I use the internal IP address, email comes in fine on wi-fi but not on 3G.
Anyone else heard of this issue?
Strange - tested with two iphones and they work okay both on 3G and wi-fi. They pick up the internal wi-fi DNS address. The SGS2 doesn't.
So when I was using 2.2.2 my WIFI connection was working flawlessly with DHCP setting my wireless settings.
I flashed 2.3.4 using NFHimself's Gobstopper without any errors, did a factory reset afterwards and I get an internet connection over mobile with no problems, however on my home WIFI network w/ DHCP (on which 2.2.2 worked fine), it cannot resolve addresses past my router (can browse to the router config fine). Now if I set a static IP and the DNS servers manually, it works over WIFI, however when the WIFI radio turns back on from sleeping it gets stuck at obtaining an IP address.
So I tried leaving it with DHCP giving me an IP address, and then using Set DNS to use google's DNS servers instead of my router's IP, and it seems to work in all situations, however it leaves me unable to browse my LAN (even when one dns domain is left as my local domain server).
I installed Network Monitor II to watch my wireless settings for the three setups:
For just using DHCP, the DNS servers are both set to my router's IP
For static settings, the DNS servers are whatever i set them however i cannot browse my LAN when one is left as my router's IP
For DHCP w/ a custom DNS, it is the same as using static settings
Not sure whether to think this is a problem with the update, or a problem with my router (however no settings were changed before or after the update on it). Anyone have any ideas?
Router: Linksys WRT54GL running DD-WRT
I read somewhere that having the "Filter WAN NAT Redirection" setting enabled in DD-WRT causes this sort of behavior on some mobiles, it is not enabled.
Only thing I could find that I thought it might be is Android Bug Issue 10315 (to which I cannot post a link as I lack sufficient posts... so far), but am still unsure
I should also note that I have two routers (both identical), but only one deals with the DHCP and DNS, the other is more just a wireless AP. Thus, all of my lan is on 192.168.1.*, including both routers ( x.x.x.1 and x.x.x.2 ). uDHCPd is my DNS server on my router, but I might try dnsmasq in the next couple days.
Jiraffe said:
So when I was using 2.2.2 my WIFI connection was working flawlessly with DHCP setting my wireless settings.
I flashed 2.3.4 using NFHimself's Gobstopper without any errors, did a factory reset afterwards and I get an internet connection over mobile with no problems, however on my home WIFI network w/ DHCP (on which 2.2.2 worked fine), it cannot resolve addresses past my router (can browse to the router config fine). Now if I set a static IP and the DNS servers manually, it works over WIFI, however when the WIFI radio turns back on from sleeping it gets stuck at obtaining an IP address.
So I tried leaving it with DHCP giving me an IP address, and then using Set DNS to use google's DNS servers instead of my router's IP, and it seems to work in all situations, however it leaves me unable to browse my LAN (even when one dns domain is left as my local domain server).
I installed Network Monitor II to watch my wireless settings for the three setups:
For just using DHCP, the DNS servers are both set to my router's IP
For static settings, the DNS servers are whatever i set them however i cannot browse my LAN when one is left as my router's IP
For DHCP w/ a custom DNS, it is the same as using static settings
Not sure whether to think this is a problem with the update, or a problem with my router (however no settings were changed before or after the update on it). Anyone have any ideas?
Router: Linksys WRT54GL running DD-WRT
I read somewhere that having the "Filter WAN NAT Redirection" setting enabled in DD-WRT causes this sort of behavior on some mobiles, it is not enabled.
Only thing I could find that I thought it might be is Android Bug Issue 10315 (to which I cannot post a link as I lack sufficient posts... so far), but am still unsure
I should also note that I have two routers (both identical), but only one deals with the DHCP and DNS, the other is more just a wireless AP. Thus, all of my lan is on 192.168.1.*, including both routers ( x.x.x.1 and x.x.x.2 ). uDHCPd is my DNS server on my router, but I might try dnsmasq in the next couple days.
Click to expand...
Click to collapse
I did flash NFHimself's ROM without any issues. My wireless LAN was working fine. Did not noticed any issue on my side. Try with another Wireless router without all the setup you've done. Pretty sure the issue is with your routers.
I don't understand why you are not able to reach you LAN with google's DNS configured...? Do you have some sort of DNS entry specific to your LAN configured into your router?
the problem seemed to solve itself when i switched my router's DNS server daemon from UDHCPD to dnsmasq.
And I couldn't reach my lan when i had both dns servers forced to google's servers as google's servers don't know how to route to addresses inside my lan. But that's not a bug, that is how it is supposed to work.
Good !
Sent from my MB860 using xda premium
This has been plaguing me for a few days now and I just want to share the solution I found for you guys. Have you ever had this issue? Your selected wireless network has been working great for days and suddenly one day it refuses to connect anymore. I would hit connect and the phone would be stuck in a "Obtaining IP address from WIFINETWORK" "Disconnected" "Scanning" cycle and so forth. You can wait forever and the phone will never connect to wifi.
The first time this happened to me I did a hard reset. Worked like a charm, I was able to use the network again for a few days until it began happening again. I decided a reset was not the solution so I looked for an answer. I happened upon sites like this:
http://anxiousnut.wordpress.com/201...d-obtaining-ip-address-wifi-issue-workaround/
Where certain solutions were posted but none seemed to work for me. I decided that it definitely wasn't my router (although some said resetting your wireless router may also work sometimes).
I finally stumbled upon the answer. The solution is to use a static ip by going into to Settings>Wireless & Networks>Wi-Fi settings>Menu Click to Advanced and then check Use static IP. You must figure out these values: IP Address, Gateway, Netmask, DNS 1, DNS 2.... Luckily, it is pretty easy.
IP ADDRESS
To find this, go back and select your wifi network. Hit "Modify" and see the IP address listed. Copy that down, this is your IP Address.
GATEWAY
This is your router's IP address. You will need a computer that is connected to the network already. For Windows, run a command prompt and type ipconfig to show you the default gateway address. For Mac, go to the network preference pane in system preferences. Click advanced and go to TCP/IP tab.
NETMASK
You will find this in the previous step. Often it is 255.255.255.0.
DNS 1
Put in the same IP you found for the gateway box.
DNS 2
Same as above.
In the end it will look something like this:
IP Address: 192.168.1.107
Gateway: 192.168.1.1
Netmask: 255.255.255.0
DNS 1: 192.168.1.1
DNS 2: 192.168.1.1
Connect again and it works. No need to factory reset. Enjoy!
Update: After a few days, something in the phone's wifi settings seem to "correct" itself and your wifi will not work with this method anymore. Simply go back and disable static IP and your phone will be back to its old self again. If the symptoms appear again, you can follow these steps again.
I wonder if this will help with eclipse 2.0.3 disconnecting issues
Sent from X2 Eclipsed using xda app
I was having this problem with CM7 and this fixed it. Thanks!
thanks solved my problem i m so very grateful
Careful, this "fix" could be very temporary... If you set a static IP and do not configure your router to use static IPs you will at some point run into conflicting IPs if you have other devices on the network. The router is dynamically allocating IP addresses if you use a standard DHCP setup and can give your chosen IP for your phone to any device on the network, creating a situation when you cannot connect or you can connect but it does not work. If you want to use static ips on your phone with the router, you have to configure the router to understand this by disabling DHCP and setting up static IPs for all devices or by allocating fixed IP for certain MAC addresses. SO either setup both your phone and router to use a static IP or change the DHCP lease time to something other than "infinity" .
Most routers strart DHCP allocation at .100. Check with your particular routers manual. If you assign the IP less than .100 you should be fine as long as you don't assign another device with the same IP.
Sent from my MB870 using Tapatalk 2
A workaround != A fix.
DigitalMD said:
Careful, this "fix" could be very temporary... If you set a static IP and do not configure your router to use static IPs you will at some point run into conflicting IPs if you have other devices on the network.
Click to expand...
Click to collapse
I'm with DigitalMD - this is a very kludgy "fix" that will lead to trouble in the future. I am coming to believe there is a consistent interoperability issue between Android and some other systems (OS X and some routers??) that leads to issues - both my GN with 4.0.4 and my JetStream with 3.1 will routinely fail to connect both to my Mac (10.7) and the routers, primarily in a couple of particular offices - maybe it's just a high-noise area (one is an older building). The devices both connect fine to my home wifi (WRT54G) and most internet cafes.
Not a good fix
This isn't really a fix for the problem. I connect to multiple wireless networks, between work and home and friend's houses, and they all have different routers. Setting a static IP is impractical, because I have to turn it on with certain networks and off with other networks, or change the static IP from one router to another.
Why does this happen? It works fine for a while, then one day it just doesn't want to take an IP address from the router. For me, it works fine at home and at my parents, but at work, it doesn't want to connect anymore. It's been connecting fine for months, then yesterday it got stuck with obtaining IP.
Setting a static IP isn't a solution; it's a cop-out. Does anybody know why this happens? Does anybody know how to fix it?
I was experiencing this from past couple of days than I just put static IP works really great for me :laugh: it was a biggest headache, now past.
Hello everybody.
Since last saturday i'm testing a Galaxy S3.
I want to test if everything works properly before buying it.
I have some problems deling with the WIFI stuff.
I gave him a static IP (192.168.1.15), configured the gateway as the ip of my router (192.168.1.1),
the network class is 255.255.255.0 (network prefix = 24), the DNS points to the IP of the Router (192.168.1.1)
It connects without problems. form the S3 i can ping any device in my network and from other devices i can ping the S3.
I can connect to the configuration site of the router and from the page of connected devices i can see that the S3 is connected
with the correct ip and also the MAC adress is correct.
And for now everything is fine.
Problems raise up when i try to surf internet. The answer is always "Page not found"
If i open the browser and try to navigate to google] the answer is "Page not found". Same for any other site i try to connect with.
I cannot ping external adresses from the S3. Only the ones inside my LAN.
On the same LAN there are 3 laptops, 1 IPhone, 1 TV, NAS NETGEAR , home automation screen, all connected in WIFI.
All of them configured in the same way. (static ip, gateway=ip router, dns = ip router, network class 255.255.255.0),
And they all access internet without any problem.
The network is protected with WPA2/PSKey, encryption AES.
I tried to configure channel with WPA, WEP, without protection, but no changes.
The S3 connects to router but does not connect to internet,
I also tried to make it point to a public DNS 8.8.8.8. No WAY!
Works for other devices.
I tried to reset S3 to factory parameters, same thing i did for the router.
I reconfigured everything from scratch but no result.
I do not have any filtering based on IP or MAC adress on my Router.
I tried with DHCP, with reservation of IP adresses or without reservation. No change.
Other devices can access internet. S3 does not.
I have to say i'm quite desperate.
If you guys have some good ideas to solve or diagnostic the problem i would be grateful.
Cheers,
Fabio
I get that around my office as I walk around, I find that when I change AP in range my internet connection drops. I have to constantly disable/re-enable WiFi.
Even around my house, I have the handset to WiFi always on, yet when I wake up in the morning the internet connection is not working yet there is an IP. I couldn't be bothered to telnet to port 80 etc., but I hear that the Jellybean update will resolve this issue.
Same problem
nickzap said:
Hello everybody.
Since last saturday i'm testing a Galaxy S3.
I want to test if everything works properly before buying it.
I have some problems deling with the WIFI stuff.
I gave him a static IP (192.168.1.15), configured the gateway as the ip of my router (192.168.1.1),
the network class is 255.255.255.0 (network prefix = 24), the DNS points to the IP of the Router (192.168.1.1)
It connects without problems. form the S3 i can ping any device in my network and from other devices i can ping the S3.
I can connect to the configuration site of the router and from the page of connected devices i can see that the S3 is connected
with the correct ip and also the MAC adress is correct.
And for now everything is fine.
Problems raise up when i try to surf internet. The answer is always "Page not found"
If i open the browser and try to navigate to google] the answer is "Page not found". Same for any other site i try to connect with.
I cannot ping external adresses from the S3. Only the ones inside my LAN.
On the same LAN there are 3 laptops, 1 IPhone, 1 TV, NAS NETGEAR , home automation screen, all connected in WIFI.
All of them configured in the same way. (static ip, gateway=ip router, dns = ip router, network class 255.255.255.0),
And they all access internet without any problem.
The network is protected with WPA2/PSKey, encryption AES.
I tried to configure channel with WPA, WEP, without protection, but no changes.
The S3 connects to router but does not connect to internet,
I also tried to make it point to a public DNS 8.8.8.8. No WAY!
Works for other devices.
I tried to reset S3 to factory parameters, same thing i did for the router.
I reconfigured everything from scratch but no result.
I do not have any filtering based on IP or MAC adress on my Router.
I tried with DHCP, with reservation of IP adresses or without reservation. No change.
Other devices can access internet. S3 does not.
I have to say i'm quite desperate.
If you guys have some good ideas to solve or diagnostic the problem i would be grateful.
Cheers,
Fabio
Click to expand...
Click to collapse
I'm having the exact same problem, I'd really like to know if you were able to solve the problem.
Phoenix_Dean said:
I'm having the exact same problem, I'd really like to know if you were able to solve the problem.
Click to expand...
Click to collapse
Me too... Is anybody has solution for this issue?
Oh poor fellows ....try to add DNS manually according to your ISP...not add public DNS
Try forgetting the network and connecting again and make sure all the other devices are using different ip address
Sent from my GT-I9300 using xda app-developers app
I am in university halls of residence. I have setup a Wi-Fi hotspot in my room using a generic router by connecting from the ethernet out port in the wall to a ethernet LAN port and disabling DHCP on the router.
This works perfectly for my Windows 7 laptop. It connects to the router and then to the uni internet without issues. However, although my Samsung Galaxy S3 (International i9300) can detect the network, if I just try to connect to the network as I would any other it gets stuck when obtaining an IP address. After messing around with it for a bit i found that I could get the phone to connect by going into the advanced settings and choosing "static" instead of "DCHP". I don't know what I was really meant to enter for IP Address, gateway, subnet, DNS 1 and DNS 2.
The router has the IP of 192.168.1.1 when i connect it directly to my laptop via ethernet so I tried that as the gateway, I set the IP address to something like 192.168.1.14 (So that it was similar but different), I set the subnet to 255.255.255.0 and the DNS servers I used google's (8.8.8.8 and 8.8.4.4). This got me connected to the router but there doesn't appear to be any internet connection.
I therefore thought that I had entered wrong information for the network (I was only guessing after all). Therefore I went into ipconfig in Windows and copied the default gateway and DNS servers and used a similar IP address (Last number different). I had the same issue.
Does anyone have any suggestions?
I only want Wi-Fi in my room for mobile.