I have had a Netgear Powerline Adapter system set up in my Bedroom (XAVNB2001) for the past year and a half, because the signal from my Cisco E4200 doesn't effectively reach up there. It has its own SSID, on the 2.4GHz band. It has been completely solid and reliable, and I use it all the time with my Verizon Samasung Galaxy Nexus (stock ROM 4.2.2), and Asus Infinity Tablet (stock ROM 4.2.1). My wife also used it without problem with her prior Motorola Droid 3.
But for reasons I can't identify, my wife's new Galaxy S4 won't connect to it. Also Stock ROM 4.2.2. Her phone sees the Adapter/SSID, and shows a strong signal when we're up there. I enter the passcode with the same encryption (WPA/WPA2 PSK) as I have on the other working devices, and it quickly goes to "Acquiring IP" but this never completes. It tries a couple of times, and usually ends up saying: "Network Disabled Because Internet Connection Is Slow." But it is not slow - works as fast with the other devices as when I'm connected to the Cisco downstairs near the Router. I have carefully entered the passcode (checking the box to show the characters to make sure I'm not putting in a typo) a dozen times.
There is no problem connecting her S4 to any other WiFi network we've encountered (to the Cisco downstairs directly, at my kids' houses, hotels, etc.).
I can't see any trouble-shooting steps to even identify the problem. Usually this is a no-brainer: you see the SSID, enter the passcode, and you're in. What could possibly be the problem here??
DLCPhoto said:
I have had a Netgear Powerline Adapter system set up in my Bedroom (XAVNB2001) for the past year and a half, because the signal from my Cisco E4200 doesn't effectively reach up there. It has its own SSID, on the 2.4GHz band. It has been completely solid and reliable, and I use it all the time with my Verizon Samasung Galaxy Nexus (stock ROM 4.2.2), and Asus Infinity Tablet (stock ROM 4.2.1). My wife also used it without problem with her prior Motorola Droid 3.
But for reasons I can't identify, my wife's new Galaxy S4 won't connect to it. Also Stock ROM 4.2.2. Her phone sees the Adapter/SSID, and shows a strong signal when we're up there. I enter the passcode with the same encryption (WPA/WPA2 PSK) as I have on the other working devices, and it quickly goes to "Acquiring IP" but this never completes. It tries a couple of times, and usually ends up saying: "Network Disabled Because Internet Connection Is Slow." But it is not slow - works as fast with the other devices as when I'm connected to the Cisco downstairs near the Router. I have carefully entered the passcode (checking the box to show the characters to make sure I'm not putting in a typo) a dozen times.
There is no problem connecting her S4 to any other WiFi network we've encountered (to the Cisco downstairs directly, at my kids' houses, hotels, etc.).
I can't see any trouble-shooting steps to even identify the problem. Usually this is a no-brainer: you see the SSID, enter the passcode, and you're in. What could possibly be the problem here??
Click to expand...
Click to collapse
You could try creating a static IP address using the MAC of the GS4 on your Cisco router. It sounds like it's authenticating, but unable to assign an IP for whatever reason.
Disable WiFi Multimedia (WMM) or the equivalent... BOOM! should work fine.
Also, if it's a MAC filter issue turn your MAC filtering off. If that is the issue your GS4 will connect instantly once MAC filtering is off.
Thanks for the replies.
I assigned a Static IP to the GS4 through the Router without difficulty. I then went to the GS4's settings for this SSID, changed it to Static IP, entered the assigned IP, kept the Gateway as 192.168.1.1, and changed the DNS settings to what is shown through IPCONFIG when I check my Desktop.
It now connected, but shows a DNS error when trying to go to a given website. So something funky is going on there. The phone shows a setting for "Network prefix length" and has a value of 24 - I've not encountered this before - should there be a different setting here?
There is no MAC filtering enabled, so that's ok.
"Disable WiFi Multimedia (WMM) or the equivalent" - where is this setting located? I don't see anything along those lines on the Phone, or in the Router's program??
DLCPhoto said:
Thanks for the replies.
I assigned a Static IP to the GS4 through the Router without difficulty. I then went to the GS4's settings for this SSID, changed it to Static IP, entered the assigned IP, kept the Gateway as 192.168.1.1, and changed the DNS settings to what is shown through IPCONFIG when I check my Desktop.
It now connected, but shows a DNS error when trying to go to a given website. So something funky is going on there. The phone shows a setting for "Network prefix length" and has a value of 24 - I've not encountered this before - should there be a different setting here?
There is no MAC filtering enabled, so that's ok.
"Disable WiFi Multimedia (WMM) or the equivalent" - where is this setting located? I don't see anything along those lines on the Phone, or in the Router's program??
Click to expand...
Click to collapse
I'm not sure about Eric214's suggestion, but it sounds like it could help. Regarding the static IP, if you set it on the router, the phone should pick it up automatically without you needing to enter it manually. After you set the static IP on the router, does the phone still hang on Acquiring IP? If you HAD to manually enter, you could plug in the DNS address coming straight from your router, or Google's open-dns of 8.8.4.4 and 8.8.8.8 (I think that still works.)
ttupa said:
I'm not sure about Eric214's suggestion, but it sounds like it could help. Regarding the static IP, if you set it on the router, the phone should pick it up automatically without you needing to enter it manually. After you set the static IP on the router, does the phone still hang on Acquiring IP? If you HAD to manually enter, you could plug in the DNS address coming straight from your router, or Google's open-dns of 8.8.4.4 and 8.8.8.8 (I think that still works.)
Click to expand...
Click to collapse
I tried it before, but tried it again - with the Static IP set up on the Router (using the "DHCP Reservation" option in the Router's program), and the Connection Settings on the GS4 for this SSID set to DHCP, all advanced settings at their default, it behaves the same way: Shows Acquiring IP, tries it twice, then shows the message I quoted above.
The Router remains set at Automatic Configuration/DHCP overall, with DHCP Reservation used to create a Static IP for this phone's MAC address. If this isn't the proper way to do this, let me know.
And with the Phone Settings for this SSID's WiFi set to Static IP, and the info entered as above, it quickly connects, but doesn't gain internet access.
It shouldn't be this hard. This is usually a no-brainer, as I first indicated. What is so different with this phone's WiFi setup??
I appreciate your input!
DLCPhoto said:
I tried it before, but tried it again - with the Static IP set up on the Router (using the "DHCP Reservation" option in the Router's program), and the Connection Settings on the GS4 for this SSID set to DHCP, all advanced settings at their default, it behaves the same way: Shows Acquiring IP, tries it twice, then shows the message I quoted above.
The Router remains set at Automatic Configuration/DHCP overall, with DHCP Reservation used to create a Static IP for this phone's MAC address. If this isn't the proper way to do this, let me know.
And with the Phone Settings for this SSID's WiFi set to Static IP, and the info entered as above, it quickly connects, but doesn't gain internet access.
It shouldn't be this hard. This is usually a no-brainer, as I first indicated. What is so different with this phone's WiFi setup??
I appreciate your input!
Click to expand...
Click to collapse
That sounds exactly right to me, and you're right that it shouldn't be that difficult. I've heard others report of miscellaneous routers that don't play nice with our phone. In this case, it's an AP, but that might still be the issue. I haven't personally experienced the problem, so hopefully someone else can chime in who has.
ttupa said:
That sounds exactly right to me, and you're right that it shouldn't be that difficult. I've heard others report of miscellaneous routers that don't play nice with our phone. In this case, it's an AP, but that might still be the issue. I haven't personally experienced the problem, so hopefully someone else can chime in who has.
Click to expand...
Click to collapse
Does anybody else have any ideas here?
I have also posted on Netgear and Verizon's forums, but am not expecting too much from either of these. I'm putting my money on the expertise here at XDA!
WMM is listed under the advanced settings of your router, it's not phone based but in your router. Disable it and return your other settings to normal and it should fix your problem.
Eric214 said:
WMM is listed under the advanced settings of your router, it's not phone based but in your router. Disable it and return your other settings to normal and it should fix your problem.
Click to expand...
Click to collapse
I'll have another look in the morning but earlier today I looked through every page of settings and didn't see anything that looked or sounded like this.
What section or function might you expect it to be found? What else might it be called?
Thanks.
Advanced settings in your router.
Basically, the 802.11n spec requires devices to support 802.11e (Quality of Service [QoS] enhancements for wireless LAN) in order to use HT (High Throughput) link rates, i.e. higher than 54 Mbps. (WMM is a subset of 802.11e that was created by the Wi-Fi Alliance as a stop-gap measure while 802.11e made its way slowly through the IEEE review process.)
The point is this is an issue for the GS4 as it's either firmware related or a Samsung issue they didn't realize they caused. Point being, if you have constant disconnects to your router, disabling WMM should make your connection "stick". At this point its what you may have to do until a firmware update for the router is released or Samsung releases an OTA update fix. Unless you're rolling 3+ devices at the same time streaming content you shouldn't have an issue running 54mbps. I stream full HD content to 2 devices at the same time with no lags or decompression issues at 54mbps.
As long as your phone has a static IP from the router there is no reason to set the DNS on the S4...the router does all the DNS routing for your devices. Hopefully that'll fix your DNS error issue.
Sent from my SCH-I545 using Tapatalk 2
OK - had another look at the Router settings, and found the WMM option in the QoS section. I somehow overlooked that yesterday. I'll try this out later today when I'm at home.
Eric214 - with respect to this WMM setting, I have a Panasonic SmartTV, and stream Netflix, Amazon Video, Vudu, etc. and can get the highest quality (1080p) through these. Is changing this setting going to impair throughput for this purpose?
chrishoyt2012 - after changing to Static IP, if I did nothing on the phone (that is, kept it at DHCP), it didn't fix the problem. I then selected Static IP on the phone, which necessitated inputting DNS. There were DNS server entries there by default, and these didn't work, so I manually changed them to my ISP's DNS that are used on my Desktop.
What should I be doing in this regard, other than what I have tried above?
Thanks!
Well, I disabled WMM Support, but nothing changed. It still failed to get an IP Address, same as I described in my original post.
No replies in the other forums either.
I'd really like to get this going - I'm also considering getting the S4, but this may cause some second thoughts...
I went into the Netgear Adapter's setup program, but couldn't fix the problem there either.
I tried different Channels, and a few other settings changes, but no joy.
There was a WMM setting there, but it was checked, and greyed out, so I couldn't try unchecking it even if I wanted to. I disabled WMM on the Router again, but this option remained unavailable on the Adapter's setup program.
I went into my Router, and deleted the IP address for the S4, to try and 'reset' it, but still no change. The S4 shows 'failed to acquire IP' every time.
Any other ideas?? I also tried my daughter's Razr HD, and it connected fine, just like the others. What is so different about the S4's WiFi connectivity??
Related
If you see this on Modaco, apols.
Hi folks, just picked one of these up for the £149 in Orange, but have a problem with wi-fi that I have had with a few WM devices over time, think its the AR6000 wlan chipset myself, seems very fussy about what and when it connects.
I would appreciate any help, but not please along the lines of "change your router", that ain't happening, it works fine with loads of other devices, so if this issue is non solveable, its the TG01 that goes!
OK, first connection to the Router (its a Billion ADSL) was fine, got connection, worked OK. From there in, as soon as it woke up, no dice, just unable to connect, always shows up in both WM and Tosh wireless util as available, just never connects.
Now, what I have noticed with this and at other times when I have had this issue with past devices is that it puts some odd stuff in the IP address field in the Configure Networks Adaptors screen.
I have it set for Use Server Assigned IP Address, but in the field below, I get this odd stuff fe80:221:e8ff:fe88 instead of 192.xxx.xxx.xxx that should be in there. I am sure this is somehow related to my connection issues, but searching the web, seems like noone else ever had this?
Kev
can u turn ur wifi off ?
and can u turn it back on ?
Yep, turns on and off no problem, even done hard reset to see if I can get that fresh connection, but no way.
That is your IP. You need to configure it with get automatic IP or put you the IP but is more complicated.
This problem have origin be tween router and mobile or pc. Some time routers didn't assign an IP address.
Some time have other origin is a key try to put the key in different form AES or TKIP nbest one TKIP.
Check to security type.
kevwright said:
I have it set for Use Server Assigned IP Address, but in the field below, I get this odd stuff fe80:221:e8ff:fe88 instead of 192.xxx.xxx.xxx that should be in there.
Click to expand...
Click to collapse
That looks like an IPv6 address as opposed to an IPv4 address, so I guess your router must be using IPv6. Does it not do this for your other devices? Maybe your router's DHCP serves up an IPv6 address because it detects that the TG01 can handle it. What happens when you try to do something meaningful on the network?
try and change your router security from wep (i assume it is due to a problem i have) and that seems to solve it,did for me neway and you are probably right about the chipset,
bojan6 said:
That is your IP. You need to configure it with get automatic IP or put you the IP but is more complicated.
This problem have origin be tween router and mobile or pc. Some time routers didn't assign an IP address.
Some time have other origin is a key try to put the key in different form AES or TKIP nbest one TKIP.
Check to security type.
Click to expand...
Click to collapse
Is it an IP address, all my other devices show 192.168.xxx.xxx, not seen that format before.
Checked the AES/TKIP thing, and tried both to no effect.
Also tried to set a static IP, but no dice.
Kev
paroariax said:
That looks like an IPv6 address as opposed to an IPv4 address, so I guess your router must be using IPv6. Does it not do this for your other devices? Maybe your router's DHCP serves up an IPv6 address because it detects that the TG01 can handle it. What happens when you try to do something meaningful on the network?
Click to expand...
Click to collapse
Hrmm, IPv6 address looks like
2001:0db8:3c4d:0015:0000:0000:abcd:ef12
Which is not really what I have, and nothing else uses it, in fact can not see any reference to IPv6 on the router.
Kev
useyourfist said:
try and change your router security from wep (i assume it is due to a problem i have) and that seems to solve it,did for me neway and you are probably right about the chipset,
Click to expand...
Click to collapse
Security is WPA2-PSK, which to be fair works on lots of other devices, and I don't really wanna mess with them
Kev
Put your configuration here and lets check if we have the same.
I have a similar issue using a Siemens Gigaset SE587 ADSL router at home with the wireless security set to WPA/WPA2 - it will happily connect me once, but subsequent attempts fail unless I reset the router. Other access points are fine. For example, there is a BTOpenZone router not far outside that I can connect to at will, with no problem. Also, the router we use at work happily embraces the TG01's desire to connect.
The SE587 has been a bit temperamental with certain other devices so I wonder if the issue is the slightly fussy router rather than the phone?
Oh well .. I'm picking up a second hand Belkin 54g router soon, so hopefully this will solve it.
Ok guys this problem how I said his origin is to not assign one IP address correctly. This problem is because of WPA2 crypt key.
Turn of your security in your router and try to connect and lets start talk then.
that address (the numbered one) looks like a mac address, if you log on to your router, set up a rule with that mac address and/or ip addres (try 192.168.0.4, its usually free unless you have more than 4 connected devices, if you have then up the 4 to a 6) and restart the connection
it may help or it may do nothing or i might be wrong
Following on from my investigations on why the SGS2 takes *so" long to re-establish a WiFi connection, it now seems part of the problem is a major delay in obtaining an IP address.
In another thread (I forget which one) it was suggested that slow WiFi could be caused by a router not being able to cope with 802.11b, g & n traffic at the same time, which got me thinking - what if I disable the n part of the WiFi on the phone to revert it to 802.11g - would this make acquisition time on an older router faster?
So - does anyone know which file / script etc. could be altered to keep WiFi enabled, but ONLY at 802.11g; not utilising 802.11n?
stuclark said:
Following on from my investigations on why the SGS2 takes *so" long to re-establish a WiFi connection, it now seems part of the problem is a major delay in obtaining an IP address.
In another thread (I forget which one) it was suggested that slow WiFi could be caused by a router not being able to cope with 802.11b, g & n traffic at the same time, which got me thinking - what if I disable the n part of the WiFi on the phone to revert it to 802.11g - would this make acquisition time on an older router faster?
So - does anyone know which file / script etc. could be altered to keep WiFi enabled, but ONLY at 802.11g; not utilising 802.11n?
Click to expand...
Click to collapse
Just a guess, but is likely a build.prop tweak
Is this a frequent problem ? Has never happend here
Sent from my GT-I9100 using XDA App
As I've said in my post on the general forum, I get a horrible delay every time I ask the phone to connect WiFi.
I've got the WiFi sleep policy set to "when screen turns off" to save battery power; and using the same router as on my SGS (hell, i can sit the phones next to each other to try this) I get the following:
Waking the SGS up from a sleep results in a delay of 1 or 2 seconds before WiFi connects.
Doing the same with the SGS2 results in a delay of up to 1 minute before WiFi will connect. (sometimes it can be seen to give up trying to acquire an IP address, then try again)
...so yes, may be a router issue, but clearly there's something different between the 2.3.3. on the SGS versus the 2.3.3 on the SGS2 as well.
You could just disable n mode on your router if you think mixed mode is slowing it down. Most new routers will let you choose which wifi modes to broadcast via their web interface. The best option would be to only use n if all your devices support n.
Sent from my GT-I9100
Router only supports g. I'm suspecting the phone looks to n first, hence my interest in disabling it.
stuclark said:
As I've said in my post on the general forum, I get a horrible delay every time I ask the phone to connect WiFi.
I've got the WiFi sleep policy set to "when screen turns off" to save battery power; and using the same router as on my SGS (hell, i can sit the phones next to each other to try this) I get the following:
Waking the SGS up from a sleep results in a delay of 1 or 2 seconds before WiFi connects.
Doing the same with the SGS2 results in a delay of up to 1 minute before WiFi will connect. (sometimes it can be seen to give up trying to acquire an IP address, then try again)
...so yes, may be a router issue, but clearly there's something different between the 2.3.3. on the SGS versus the 2.3.3 on the SGS2 as well.
Click to expand...
Click to collapse
quick side note, wifi sleep policy set to NEVER saves you much more battery power because when it switches over to 3g, 3g uses way more power than just leaving it on wifi. counter intuitive but true.
Have you tried hard coding an IP address on the S2?
And by Hard coding, he means manually setting a Static IP address and now allowing the DHCP to provide you an IP address each time. Although the IP will most likely be the same while using DHCP, it has to request and authenticate each time. Setting a Static IP address eliminates the process of "Asking" for a IP address each time.
when the phone scans and finds the ssid, as part of that scan it checks if the router supports b/g/n then will try to connect at the highest speed. If the router isnt n compatible it wont even try.
I don't want to give the phone a static IP as I regularly visit three or four different wireless networks and they don't all use the same IP range.
I do know how DHCP works, this isn't a newbie question.
It seems definite now, watching the phone, that it tries to connect once (presumably on n), fails, then re-connects (quickly) on g.
Of course, I'll be changing the router eventually; I'm just interested in what's going on first
stuclark said:
I don't want to give the phone a static IP as I regularly visit three or four different wireless networks and they don't all use the same IP range.
I do know how DHCP works, this isn't a newbie question.
It seems definite now, watching the phone, that it tries to connect once (presumably on n), fails, then re-connects (quickly) on g.
Of course, I'll be changing the router eventually; I'm just interested in what's going on first
Click to expand...
Click to collapse
Understand about leaving it set for DHCP. Trying a fixed IP as a test may tell you if DHCP is part of the delay. If the b/g/n search is that slow it would be useful if it could be configured more precisely.
Have you tried it using another router using only g? If n is available it connects quickly? Seems like others would have mentioned this if it is something with the phone as g-only networks are still common.
I too am interested in disabling 802.11n. wpa_supplicant keeps hanging on some wifi networks and I suspect it may be because of n.
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?
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.
All,
I just recently got my S3 (T-Mobile) on opening day 21Jun12 however could not get my wifi to work properly at home. It would say "connected" on my S3 but no internet and wifi calling. In addition, when I tried to "enable" my wifi calling, I would get a REG99 error. Tech support narrowed this error to an address update on my profile (911 address info) which was updated but the problem still existed. I troubleshooted with my router and saw no problems on that end due to the fact that 8 other devices connected fine. After looking carefully at IP addresses, I noticed my S3 persistently tried to connect with an IP of 192.168.100.16 where all my other devices had an IP that started with 192.168.1.(xxx). Check to see if your S3 defaults to a conflicting IP or IP that your Router does not accept (My router accepted standard IPs from 192.168.1.1 to 192.168.1.254). Before you do the steps below, reference your Router Configuration and check your starting and ending IP addresses, Gateway IP, DNS and Alternate DNS.
Now for the fix:
If you're S3 is connected to your home wifi but no internet, wifi calling, etc.
1) Simply goto Settings
2) Click on Wifi to get to the your wi-fi networks list
3) Press AND HOLD on the connected network (The one that says connected) and a window will pop up
4) Select modify network config.
5) highlight advanced options
6) Change IP settings (dropdown) to static
7) Enter a new IP address that your router accepts (ex. 192.168.1.10). Like mentioned above, my router takes 1-256 for the last number set. Be careful to not select an IP address that's already being used. You can easily see what IPs are used in your router configuration setup (something like attached devices).
8) Make sure your gateway is similar to your router config (usually 192.168.1.1)
9) Network prefix length - I left this alone at 24
10) DNS 1 and DNS 2 can be also found in your Router Config setup. (DNS 2 is usually your alternate DNS).
11) Click save and voila (You may want to turn wifi on and off on your S3 to recycle)
After 3 tech support calls with no resolution and researching this for the last 2 weeks, I found the answer to my problems. I can understand how annoying this problem could be for some people out there so I decided to register with XDA and post this for you all.
Hope this works for some of you. Enjoy!
~Jay
Sounds like an issue with the phone's DHCP client.
However afaik T-Mobile sells the US Galaxy S3, not thn international i9300 what this forum is about.
Sent from my GT-I9300 using xda premium
Yeeeehhhhaaaaa
JAY! you are amazing... thanks soooooo much - i've been trying to sort this for ages - really appreciate your time and expertise.
Cheers Anna
Jccovert said:
All,
I just recently got my S3 (T-Mobile) on opening day 21Jun12 however could not get my wifi to work properly at home. It would say "connected" on my S3 but no internet and wifi calling. In addition, when I tried to "enable" my wifi calling, I would get a REG99 error. Tech support narrowed this error to an address update on my profile (911 address info) which was updated but the problem still existed. I troubleshooted with my router and saw no problems on that end due to the fact that 8 other devices connected fine. After looking carefully at IP addresses, I noticed my S3 persistently tried to connect with an IP of 192.168.100.16 where all my other devices had an IP that started with 192.168.1.(xxx). Check to see if your S3 defaults to a conflicting IP or IP that your Router does not accept (My router accepted standard IPs from 192.168.1.1 to 192.168.1.254). Before you do the steps below, reference your Router Configuration and check your starting and ending IP addresses, Gateway IP, DNS and Alternate DNS.
Now for the fix:
If you're S3 is connected to your home wifi but no internet, wifi calling, etc.
1) Simply goto Settings
2) Click on Wifi to get to the your wi-fi networks list
3) Press AND HOLD on the connected network (The one that says connected) and a window will pop up
4) Select modify network config.
5) highlight advanced options
6) Change IP settings (dropdown) to static
7) Enter a new IP address that your router accepts (ex. 192.168.1.10). Like mentioned above, my router takes 1-256 for the last number set. Be careful to not select an IP address that's already being used. You can easily see what IPs are used in your router configuration setup (something like attached devices).
8) Make sure your gateway is similar to your router config (usually 192.168.1.1)
9) Network prefix length - I left this alone at 24
10) DNS 1 and DNS 2 can be also found in your Router Config setup. (DNS 2 is usually your alternate DNS).
11) Click save and voila (You may want to turn wifi on and off on your S3 to recycle)
After 3 tech support calls with no resolution and researching this for the last 2 weeks, I found the answer to my problems. I can understand how annoying this problem could be for some people out there so I decided to register with XDA and post this for you all.
Hope this works for some of you. Enjoy!
~Jay
Click to expand...
Click to collapse