hi,
I've linksys wi-fi router model WRT54GH in my home & it has a good amount of signal strength to cover entire area.
My recently bought galaxy S2 is able to identify linksys wi-fi access point & connects too with the IP assigned to it, also at wi-fi settings connected being displayed.
Now when I try to access Internet (any url google/FB), it doesn't connect at all.
I tried almost everything about router configuration, restart etc. but with no success
can someone plz help on this ?
shantanu_d said:
hi,
I've linksys wi-fi router model WRT54GH in my home & it has a good amount of signal strength to cover entire area.
My recently bought galaxy S2 is able to identify linksys wi-fi access point & connects too with the IP assigned to it, also at wi-fi settings connected being displayed.
Now when I try to access Internet (any url google/FB), it doesn't connect at all.
I tried almost everything about router configuration, restart etc. but with no success
can someone plz help on this ?
Click to expand...
Click to collapse
In my case the problem was with frozen "WiFi sharing" in combination with juicy defenders "Location" fearure. It seems such combination is dangerous. Solutin (in my case):
1. defroze
2. remove all wifi networks
3. reboot (for "clean" frozing)
4. make WiFi sharing frozen
5. reboot again just for fun
Try to check your router's MAC address restrictions. In my router, as security, I have to add MAC addresses of each device to share internet. They take IP's, connects etc. but does not have accesses to internet
as above, check that there is no MAC filtering set up.
one other thing it may be is the security settings, if you have a WEP Key to access the router it may need the Hex conversion of your key depending on what level of security you have (64bit or 128bit for example)
shantanu_d said:
hi,
I've linksys wi-fi router model WRT54GH in my home & it has a good amount of signal strength to cover entire area.
My recently bought galaxy S2 is able to identify linksys wi-fi access point & connects too with the IP assigned to it, also at wi-fi settings connected being displayed.
Now when I try to access Internet (any url google/FB), it doesn't connect at all.
I tried almost everything about router configuration, restart etc. but with no success
can someone plz help on this ?
Click to expand...
Click to collapse
Try setting up a static IP address for your phone, I presume your network is a 192.168.1.0, go into router settings and LAN setup, give your phone the address in a static DHCP assignment of 192.168.1.5, or any other address in the same subnet your in. Some SGSII's have problems with dynamic DHCP for some reason, some NS had the same problem too,
Sent from my Sammy Galactic S2 Beastly Device
I have a similar problem and I fix mine temporarily by turning my wifi off, then in wifi settings > advanced, I change wifi sleep policy from 'never' to 'only when the screen is off'. However I have to do this every time I want to use wifi so it can become quite annoying sometimes.
So I can get through however only for a short period of time as it seems as long my Galaxy S2 keeps turning off my wifi even though it's on :/
I had exactly the same issue on Linksys E4200 with my laptop, could connect to network, even to router's attached storage, but not to internet. Restart helped
On SGS2, I couldn't connect to the router at all at first, but fixed this by switching from WPA2/WPA mixed mode access protocol to WPA2 private. But I guess this is not exactly your issue.
SiSL said:
Try to check your router's MAC address restrictions. In my router, as security, I have to add MAC addresses of each device to share internet. They take IP's, connects etc. but does not have accesses to internet
Click to expand...
Click to collapse
Thanks for the suggestion but MAC restriction is already disabled at router
Robsso said:
I had exactly the same issue on Linksys E4200 with my laptop, could connect to network, even to router's attached storage, but not to internet. Restart helped
On SGS2, I couldn't connect to the router at all at first, but fixed this by switching from WPA2/WPA mixed mode access protocol to WPA2 private. But I guess this is not exactly your issue.
Click to expand...
Click to collapse
Yes, you are right this is not an issue for me.
In fact my SG2 being assigned with an IP address from 192.168.1.xx subnet.
Also at a same time my laptop connected with an IP from same subnet able to ping SG2.
OccasionalDroid said:
Try setting up a static IP address for your phone, I presume your network is a 192.168.1.0, go into router settings and LAN setup, give your phone the address in a static DHCP assignment of 192.168.1.5, or any other address in the same subnet your in. Some SGSII's have problems with dynamic DHCP for some reason, some NS had the same problem too,
Sent from my Sammy Galactic S2 Beastly Device
Click to expand...
Click to collapse
My SG2 being assigned with an IP address from 192.168.1.xx subnet.
So I think IP addressing may not be an issue.
Also another thing I tried was, at a same time my laptop connected with an IP from same subnet able to ping SG2.
So wi-fi router may not be an issue here, whats say ???
Even I am facing the same issue at my office network. I am able to connect to the wireless network but if I try to access any app I cannot browse. This is really frustrating looks like some issue with the modem drivers.
I was able to browse on another wifi created virtually by mobile tethering. This looks like a major bug with the current firmware. Another interesting thing to note is that the Wifi network has a hidden SSID and uses WPA2 auth scheme.
I have seen a Galaxy S able to connect to the same n/w without any issues.
Has anyone figured out a solution to this one ?
Hi, thanks for your reply.
I am yet to figure out a solution for this
Even I am also agree on the probable issue with modem driver.
I've D-link modem.
Are you aware of anything about this modem that can be reconfigured to get this worked ... ?? pl let me know
The wifi router at my office is Cisco Aironet 1200 Series, anyone else facing this issue ?
I'm having the same problem at work connecting my SGS2 with v2.3.3 Official Firmware (customized for Orange service provider) to a Cisco Aironet 1130 AP. I can see that the Galaxy authenticates with the AP correctly and gets IP from the DHCP server, but it cannot send or receive any traffic, although the phone stays connected and authenticated. At home, I use an Atheros based Fonera with DD-WRT without any problem.
As I'm the company's network administrator, I will try to further investigate this problem, but it seems like some kind of incompatibility between the devices or misconfiguration ....
Basuk said:
The wifi router at my office is Cisco Aironet 1200 Series, anyone else facing this issue ?
Click to expand...
Click to collapse
try turn off the wifi, turn off the mobile data and turn on the wifi again
It seems the SGS2 sometimes has problems with DNS.
Try a static IP and use 8.8.8.8 as second DNS server, which is a free Google DNS server.
This fixed MY problems
I rooted my SGS2 and voila wifi worked at my office finally I have been able to find a solution.. love my SGS2 the Beast...
I'm having this same problem..
I think I've tried all the solutions above, but one (Sorry - noob question):
Rooted?
is there a firmware patch or something that I should know about?
Anyone got any other ideas?
ETA:
I can connect to hotspots (DHCP) and at home (Have to set it to static tho)
No internet
AP works - Laptop and i8910 (had to set static and advanced settigs etc). I've rebooted it a few times, set DHCP on and off. DHCP seems to be running on the router
viqles said:
I'm having this same problem..
I think I've tried all the solutions above, but one (Sorry - noob question):
Rooted?
is there a firmware patch or something that I should know about?
Anyone got any other ideas?
Click to expand...
Click to collapse
This is an issue with SGS2 with wifi server using authentication protocol TPIK, if you use AES as encryption then it will work without any issues.
That should be a setting in my AP? I can't see it...
If I get a new non-crappy AP is that likely to solve my problem?
ETA:
Ah - that's a WPA thing? Mine only seems to do WEP - is that right?
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
Ok, so, I have a VPN setup at home, and I'm connected to it with my phone (AT&T Infuse 4G). Does every single packet go out through the VPN or only the ones destined for an IP on the private subnet? If it indeed passes every packet over the VPN (as with others I've used), why couldn't one just tether it after that? Would all data not then go over AT&Ts network and out to the internet via my home connection?
I've actually been musing about this for a while, but never bothered to actually connect my phone to my home VPN until now to even think about trying it.
Anybody have any unique insight on this?