Related
First of all may I say I have searched for this problem on google, as well as xda forum. I did find several threads about this problem, but none of the solutions presented appear to be my case.
So, basically the problem is: I cannot connect to my home router, a Linksys WRT300N N-router. I could not connect with a N1, HTC Desire, nor with my actual NS. My previous Galaxy S was connecting fine though. I'm talking here about stock ROM, no rooting, no custom kernel etc. Also, using static IP address works like a charm, but then WiFi cannot be used on other outside routers, since Static Ip setting is not setup PER router, but rather per WiFi connection, meaning the phone will try to use the static IP defined for any WiFi I run into.
From My experience, it seems it could be related to wireless N router as opposed to b/g. This happened since I replaced my router with the actual one. Ever since this happened, my phone would not connect to my router. Also, this problem seems to be presentfor any N-router, since I cannot connect to WiFi in other locations as well (which might have N-routers as well).
Assuming that it is a problem with N-routers, I don't understand why the Galaxy S would connect, but NS not, since they are almost the same hw.
Does anyone have a clue on this? But please skip solutions like reset router, reset phone, reset modem, use different ROM etc. I am talking stock ROM for all the examples above.
Thanks.
I use my NS with three 802.11N routers without issue (D-Link, Belkin and Netgear).
Have you checked if MAC filtering on the router is active? What security mode are you using? Who makes yr router and does it have latest fw?
Sent from my Nexus S using XDA App
Just seen you use Linksys, I have a wag160n and I find it unsusable on terms of wifi, dreadful hardware, despite the parent company being Cisco
Check Linksys forums for problems.
Try another router for whether it's that or phone at fault.
Sent from my Nexus S using XDA App
MikhailCompo said:
I use my NS with three 802.11N routers without issue (D-Link, Belkin and Netgear).
Have you checked if MAC filtering on the router is active? What security mode are you using? Who makes yr router and does it have latest fw?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
MAC filtering is disabled, I've checked it. Security is, on the router, PSK-Personal with TKIP encryption. Key renewal: 7200 sec. Not sure if this can influence anything.
I've checked on linksys page for fw upgrade, they only have pdf manuals.
ionutz6 said:
First of all may I say I have searched for this problem on google, as well as xda forum. I did find several threads about this problem, but none of the solutions presented appear to be my case.
So, basically the problem is: I cannot connect to my home router, a Linksys WRT300N N-router. I could not connect with a N1, HTC Desire, nor with my actual NS. My previous Galaxy S was connecting fine though. I'm talking here about stock ROM, no rooting, no custom kernel etc. Also, using static IP address works like a charm, but then WiFi cannot be used on other outside routers, since Static Ip setting is not setup PER router, but rather per WiFi connection, meaning the phone will try to use the static IP defined for any WiFi I run into.
From My experience, it seems it could be related to wireless N router as opposed to b/g. This happened since I replaced my router with the actual one. Ever since this happened, my phone would not connect to my router. Also, this problem seems to be presentfor any N-router, since I cannot connect to WiFi in other locations as well (which might have N-routers as well).
Assuming that it is a problem with N-routers, I don't understand why the Galaxy S would connect, but NS not, since they are almost the same hw.
Does anyone have a clue on this? But please skip solutions like reset router, reset phone, reset modem, use different ROM etc. I am talking stock ROM for all the examples above.
Thanks.
Click to expand...
Click to collapse
Have you checked that you set up the router with b/g/n protocols? not only N..
Try to change the password encrypting method, to WPA or WPA2 or WEP, try also to change the default password.
Have you tried to disable the firewall (DMZ)?
I have exactly the same issue on my stock Desire.....
I have recently upgraded my router from a Belkin G+ to a Belkin N+ and using the b/g/n setting the desire WILL see the connection but will NOT connect to it, NO MATTER WHAT settings you try. Changing it to b/g and it will connect without any issues.
It is my understanding that the Desire/Nexus et al doesnt have the access to the N ability enabled (it has the correct chipset but for some reason it is not active).
Maybe when broadcasting the tri-band the chipset only sees the stronger N connection, therefore tries to connect but gets conflicted (due to lack of N firmware) and instead of switching to b/g it just loops to the stronger signal. IF that makes any sense
Riki1kenobi said:
I have exactly the same issue on my stock Desire.....
I have recently upgraded my router from a Belkin G+ to a Belkin N+ and using the b/g/n setting the desire WILL see the connection but will NOT connect to it, NO MATTER WHAT settings you try. Changing it to b/g and it will connect without any issues.
It is my understanding that the Desire/Nexus et al doesnt have the access to the N ability enabled (it has the correct chipset but for some reason it is not active).
Maybe when broadcasting the tri-band the chipset only sees the stronger N connection, therefore tries to connect but gets conflicted (due to lack of N firmware) and instead of switching to b/g it just loops to the stronger signal. IF that makes any sense
Click to expand...
Click to collapse
Well, the funny part is that I don't even know how to disable the N range to my Linksys 300N.
Anyway, it is weird that the Samsung Galaxy S had no issues with this, while Nexus S (still Samsung made, brother-in-law to SGS) has this issue. For HTC, all have had this problem, including Desire, Desire HD, Wildfire.
Still no explanation or resolution to this matter.
I may have fixed this issue (well I have for me anyway, so yay).
After posting this I decided to apply some weird logic to it. So I reset the router back to b/g, to do this you need to log into the router IP settings, for Belkin it is 192.168.2.1. On linksys routers I think it is 192.168.1.1 but check to be sure.
Once you are logged in there you can change the broadcast settings from N, b/g/n or b/g etc.
Okay, so here is what I did. I reset the router to broadcast b/g only, my Desire would connect. So I decided to try resetting the router to broadcast b/g/n (because I use N on other devices) and then switched the wifi on the desire off and back on again. Low and behold it connects.......Tried it loads of times now and connects everytime!
Might be worth a try?
You guys should just check the logs on the router and see what they say. Should give you a much better idea of what the issue is. You can then Google the error line.
Mine is fixed now, been connecting to various N routers with NO probs since I did the workaround.
My guess would be a protocol conflict (wireless handshake if you prefer) when N routers are broadcasting (based on the fact that the Desire/Nexus etc dont have N protocol enabled in the chipset firmware).
To get around the conflict connect to an N router using the b/g only setting in the routers IP settings and then check you can connect okay and switch the b/g/n back on in the router. I've done this twice today (different N routers, a Linksys and a D-Link) and it works on both where it wouldnt before, so it wasnt just my router.
hum... i am having the exact same problem as described only my router is already using
802.11g&802.11b
i have no idea why it keeps trying to obtain ip address
then it scans agains because it can't connect and tries to obtain the ip again
after trying for a minute or 2, the home ssid becomes:
"disabled, secured with..."
(device = motorola atrix)
I have tried everything and still not working... do routers block Mac addresses if it doesn't connect right away?
Sent from my MB860 using XDA App
Did you reboot your router? Mine does that sometimes but a reboot always fixes it.
Sent from my Nexus S using XDA App
Hum. Tried restarting the router... no go
Sent from my MB860 using XDA App
Hello all!
Not sure if this has been posted but I figured I would put up a new post. I am showing that I am connected to my home WiFi but I am not able to actually use it. For instance, I cannot open links or watch YouTube videos. I believe it is the router because I just had a Droid RAZR and my connections to the Internet were not dependable. Currently, I am using AT&T's 2Wire 2701HG-B Gateway router.
Are there any settings that should be adjusted within the router? Encryption type is WPA-PSK. Wireless mode is 802.11g/b.
I just got my S3 yesterday and so far WiFi works in other places. Also, I tried the #*0011# thing and that did not work for me. I've rebooted and factory reset my device. Nothing helps. Anything I can change?
Thanks in advance!
Does your router Administration panel (perhaps accessed via a web browser?) show your phone as connected with an assigned IP address?
- ooofest
ooofest said:
Does your router Administration panel (perhaps accessed via a web browser?) show your phone as connected with an assigned IP address?
- ooofest
Click to expand...
Click to collapse
Now that I'm looking, no it doesn't have it listed there. My phone says its connoted though. I forgot the connection, rebooted the phone and did the #*0011# and reconnected the network. Still the same result. Any ideas?
I've seen some routers being a bit buggy about showing all wireless-connected devices (my dual-band Netgear comes to mind), so I can only think of a few things to check:
This assumes your router is configured for DHCP and that you have addresses available in its configured range, etc.
1. Does anything else use this router successfully to access the Internet?
2. On your phone, Settings -> Wi-Fi->(click on the wireless network you are "Connected" to)->View, does it show an expected speed and a valid IP address from your router?
3. If (2.) revealed a valid IP address on the phone, can you ping that address from another system attached to the same router?
4. Did you connect the phone using a typed-in passphrase on both router and phone or by using the Wi-Fi Protected Setup (WPS) push-button method on the router? I found that, no matter how carefully I typed the passphrase, it often would not connect to my desired network because something was somehow amiss. However, this phone is compatible with using WPS, so I used the router's push-button method and it connected easily + worked fine.
Just some things to check and ensure nothing critical is amiss.
- ooofest
ooofest said:
I've seen some routers being a bit buggy about showing all wireless-connected devices (my dual-band Netgear comes to mind), so I can only think of a few things to check:
This assumes your router is configured for DHCP and that you have addresses available in its configured range, etc.
1. Does anything else use this router successfully to access the Internet?
2. On your phone, Settings -> Wi-Fi->(click on the wireless network you are "Connected" to)->View, does it show an expected speed and a valid IP address from your router?
3. If (2.) revealed a valid IP address on the phone, can you ping that address from another system attached to the same router?
4. Did you connect the phone using a typed-in passphrase on both router and phone or by using the Wi-Fi Protected Setup (WPS) push-button method on the router? I found that, no matter how carefully I typed the passphrase, it often would not connect to my desired network because something was somehow amiss. However, this phone is compatible with using WPS, so I used the router's push-button method and it connected easily + worked fine.
Just some things to check and ensure nothing critical is amiss.
- ooofest
Click to expand...
Click to collapse
1. Yes, my iPad and two laptops.
2. There is a link speed and an IP address but the third number of the IP address on my phone is different than the third number of the IP addresses of the devices listed that connect to the router. I hope I made some type of sense saying that lol! There are about 6 devices listed that connect to the router and the first, second and third numbers are the same. My phone only have the first & second numbers in common.
3. didn't try that because I'm assuming something isn't right from the previous answer.
4. I typed in the pass phrase from my phone. I do not know of any other way to connect the device. I am not familiar with doing it from the admin panel especially since I'm not even seeing the device there.
Thanks again!
Yeah, not getting the proper address range would be indicative of a problem authenticating with the router, I'd suspect. If you are using the default router configuration, it should have an IP address of 192.168.1.x, where x = {some number}
You might try temporarily setting the router to "WEP-Open" and no passphrase on the phone (i.e., connect to the open network) to determine if the phone can obtain a valid IP address from this router before doing more debugging. This might weed out the possibility that this new phone has an inherent problem connecting with your specific router - even though other devices don't have such issues, maybe the Galaxy S III is sensitive in this regard.
Consider ensuring that the "Power setting" in your wireless configuration is at its maximum value (10?).
Aside, I don't know if the latest firmware enables WPA2-PSK, but that utilizes AES and is often more efficient than WPA-PSK, from my understanding. If using WEP-Open works for your new phone in the above test, then consider setting the router to "WPA-PSK and WPA2-PSK" (if it has that value) and try reconnecting using the passphrase (either 10 or 26 letters/numbers) - that setting should be compatible with your other devices and not require them to be reconfigured, I believe.
This topic seems to indicate people have problems with your model of router in making and keeping wireless connections at times, sometimes needing to hardcode the router down to only use "b" protocol (i.e., slower) for maintaining stable connections. I don't think that's the case here, though.
This User Guide (.pdf) for your router model does not seem to show that it offers WPS as an alternative for establishing device connectivity. From my recollection, my phone would only connect reliably to the router using encryption when I used the WPS button on the router. That's why I asked you to set your router to be Open for a test.
- ooofest
I had the same issue as you. I would be connected to my router and nothing at all. I am using a att modem/router along with my netgear wndr3800. But wifi was dropping a lot of the time. I never had this problem before when I had my Rezound. 3 days before I got my S3 I upgraded the firmware on my netgear router. I am guessing my S3 didn't like the firmware update or something. I tried everything in the router settings to doing a factory reset on both the att modem and my netgear router. Nothing... So I honestly thought it was my phone. Called Verizon and asked them to ship me a refurbished. So, I thought I would try one more thing. Revert back to my old firmware on the netgear router. Well it worked. Since Friday night I haven't had the issue you are having. Connected to my home wifi with no drops at all. It could be the firmware. Wonder if you could revert back. On a att modem/router I am not sure.
Sent from my Samsung Galaxy S3
ooofest said:
Yeah, not getting the proper address range would be indicative of a problem authenticating with the router, I'd suspect. If you are using the default router configuration, it should have an IP address of 192.168.1.x, where x = {some number}
You might try temporarily setting the router to "WEP-Open" and no passphrase on the phone (i.e., connect to the open network) to determine if the phone can obtain a valid IP address from this router before doing more debugging. This might weed out the possibility that this new phone has an inherent problem connecting with your specific router - even though other devices don't have such issues, maybe the Galaxy S III is sensitive in this regard.
Consider ensuring that the "Power setting" in your wireless configuration is at its maximum value (10?).
Aside, I don't know if the latest firmware enables WPA2-PSK, but that utilizes AES and is often more efficient than WPA-PSK, from my understanding. If using WEP-Open works for your new phone in the above test, then consider setting the router to "WPA-PSK and WPA2-PSK" (if it has that value) and try reconnecting using the passphrase (either 10 or 26 letters/numbers) - that setting should be compatible with your other devices and not require them to be reconfigured, I believe.
This topic seems to indicate people have problems with your model of router in making and keeping wireless connections at times, sometimes needing to hardcode the router down to only use "b" protocol (i.e., slower) for maintaining stable connections. I don't think that's the case here, though.
This User Guide (.pdf) for your router model does not seem to show that it offers WPS as an alternative for establishing device connectivity. From my recollection, my phone would only connect reliably to the router using encryption when I used the WPS button on the router. That's why I asked you to set your router to be Open for a test.
- ooofest
Click to expand...
Click to collapse
I tried WEEP-Open and that did not allow me to connect either. I did set up WPA2 but I still was not able to connect. The power setting was set to 10. Not sure how to manually add the device which I was going to try. I've forgot it several times and added it again but it does not work. I did connect at a different location. Not sure what else to try. Even tried changing the channel.
iLogikk said:
I tried WEEP-Open and that did not allow me to connect either. I did set up WPA2 but I still was not able to connect. The power setting was set to 10. Not sure how to manually add the device which I was going to try. I've forgot it several times and added it again but it does not work. I did connect at a different location. Not sure what else to try. Even tried changing the channel.
Click to expand...
Click to collapse
If it's not connecting to your router with WEP-Open, then something different is going on. I looked in the manual for MAC Address access lists, but that doesn't appear to be a feature of this router (unless it was added in a firmware update which came after the manual was published - if this was the case, your laptops and iDevice would have had their MAC addresses added to the router as another layer of access control to the WiFi network).
Sorry, I'm out of ideas on this one. You seemed to say that the Samsung connects to other WiFi points, so perhaps there is an inherent incompatibility between this router model and your phone which can be reported to Samsung and/or Verizon Tech Support - for all we know, this is a known issue.
- ooofest
ooofest said:
If it's not connecting to your router with WEP-Open, then something different is going on. I looked in the manual for MAC Address access lists, but that doesn't appear to be a feature of this router (unless it was added in a firmware update which came after the manual was published - if this was the case, your laptops and iDevice would have had their MAC addresses added to the router as another layer of access control to the WiFi network).
Sorry, I'm out of ideas on this one. You seemed to say that the Samsung connects to other WiFi points, so perhaps there is an inherent incompatibility between this router model and your phone which can be reported to Samsung and/or Verizon Tech Support - for all we know, this is a known issue.
- ooofest
Click to expand...
Click to collapse
Thank you for all of your help!
Rams99 said:
I had the same issue as you. I would be connected to my router and nothing at all. I am using a att modem/router along with my netgear wndr3800. But wifi was dropping a lot of the time. I never had this problem before when I had my Rezound. 3 days before I got my S3 I upgraded the firmware on my netgear router. I am guessing my S3 didn't like the firmware update or something. I tried everything in the router settings to doing a factory reset on both the att modem and my netgear router. Nothing... So I honestly thought it was my phone. Called Verizon and asked them to ship me a refurbished. So, I thought I would try one more thing. Revert back to my old firmware on the netgear router. Well it worked. Since Friday night I haven't had the issue you are having. Connected to my home wifi with no drops at all. It could be the firmware. Wonder if you could revert back. On a att modem/router I am not sure.
Sent from my Samsung Galaxy S3
Click to expand...
Click to collapse
I've tried every way possible to find a way to revert back but it does not work. No success. I've noticed that this S3, my old razr, & another android phone does not actually connect. The comet (3rd phone) actually appears on the the panel but the ip address on the phone is different than what is showing on the admin page for my router. The phone does show whereas the razr and s3 never even appear in the list though they say they are connected.
I'm at a dead end
iLogikk said:
I've tried every way possible to find a way to revert back but it does not work. No success. I've noticed that this S3, my old razr, & another android phone does not actually connect. The comet (3rd phone) actually appears on the the panel but the ip address on the phone is different than what is showing on the admin page for my router. The phone does show whereas the razr and s3 never even appear in the list though they say they are connected.
I'm at a dead end
Click to expand...
Click to collapse
To be honest. It's not your phone. I think you said you already did a factory reset on the modem/router correct? If not, do it and revert back to factory settings. If that doesn't work I would call att and tell them to send you another att modem/router. Tell them your wifi is down. Hopefully you'll get everything back to where it was. Good luck.
Sent from my Samsung Galaxy S3
Fix
This is what finally worked after two weeks of researching! Found this here for the toshiba thrive but it worked for mr! http://www.thriveforums.org/forum/t...1-thrive-will-not-connect-t-2wire-router.html
I tried this part but all of my settings were already set to match this....including it because it was part of the process.
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Originally Posted by shakefry
My little sister received a cool Toshiba Thrive for Christmas but the thing will not connect to the proprietary router we have. The router isn't the problem because I've been able to connect a Macbook, 2 PCs, a 3DS and a smartphone to it and they all work as needed. When we put in the password for the connection it saying it is 'scanning' and 'connecting' then disconnects and starts going into a scanning loop saying is scanning then stopping then starting again.
I found a similar topic about this but the thread did not answer my question. I followed all of the steps of given solutions to no avail. And the constant suggestion to set the beacon or preamble differently is highly frustrating because the model router I have does not have such settings (I have gone through all the menus about ten times, literally).
I have also heard that the connection security could be a factor but I am not willing to downgrade my WPA 2 (TKIP & AES) to a WPA 1 or WEP, unless its absolutely necessary. I've been googling for hours so I need a solution or unfortunately we will have to return it for a more compatible device, which would suck because we got this for a good price (new).
Our router is a 2WIRE 3800 hgv-b (we have AT&T Uverse, idk if I should specify anything else)
Any help would be greatly appreciated.
Hi shakefry - Nice to meet you. You are 100 percent right you should not lower your security - WPA2 is the strongest and it does work fine with Thrive. That is what I use.
For some reason the ATT 2-wire routers are the most frustrating, but that is not a problem. We just might have to try a few different things, instead of getting it to connect the first time, so stay with me, OK? big brothers always have to help their little sisters...
----
1. You do not have MAC Filtering enabled,do you? If you do add the Thrive's MAC to the Router's list of permitted devices. Then try connecting.....
2. Not using MAC Filtering, or you added the thrive and still can not connect ......
OK, First ... Lets get the info your Windows Laptop has about your router when it connects
successfully to the 3800HG-B Router via wifi:
On your (Win7?) PC that is successfully connected by wifi to the same network, lets get some wifi settings. Vista - pretty much the same screens, XP a little different looking.
Click on the wifi signal lower right taskbar, open network and sharing center.
click on right side in blue, your network name
Pop up window - click on Details
the detail window opens ...
IPv4 Subnet Mask should be 255.255.255.0, if not we need to change it in the router settings.
This would prevent you from getting to the internet, but with all devices not just thrive.
Copy down IPv4 Default Gateway, and both IPv4 Servers
(Most routers will not need the actual IPv4 addresses in the devices DNS1 and DNS2, but yours might)
Now (no picture) close the DETAILS window and click on WIRELESS PROPERTIES. click on SECURITY tab, then click on SHOW PASSWORD. DO NOT CHANGE THIS FIELD, YOUR PC WILL DISCONNECT. WHAT YOU SEE IN THIS FIELD IS THE CORRECT PASSWORD TO YOUR NETWORK.
(I just want to be 100 percent sure - this is the password you need to log the thrive on. You are pretty sharp with all this stuff, so you know it is case sensitive, don't mistake a "zero" for the cap letter O, etc.
We will try using these when we set Thrive's wifi settings for your network.
(Go to link to find the screenshot)
Now please check the following router summary page by logging on to your router.
Make sure, on the right side it, shows enough DHCP Available, and on that the router
address is still 192.168.1.254
And on the left, the page is exactly the same as below, none of the blank fields are filled in, right?
And the top button is still selected ..... 192.168.1.0/255.255.255.0 (default)
--------------------------------------------------------------------------------------------------------------------------------------------------------------
THIS IS WHERE THE ACTUAL FIX CAME IN
Originally Posted by shakefry
"Would it possibly help if i DID enable filtering? then I could just put in all the device's MAC addresses and maybe it'll be more focused or something?"
No filtering wont "pull in" the devices, through the front door of the router. Filtering will just turn them around and kick them out again if they are not on the "invited to the party" List.
"edit: I just found a similar page, the design is slightly different. The router/gateway address is one number above my DHCP range and it says I have 178 available and there are 12 allocated (weird because we only have 10 devices connected to this thing that I know of)
OK so you have plenty of available IP addresses (DHCP). It is normal to see a couple more than the number of devices you have."
So now you have the info you need to connect the thrive (maybe):
1-Hold the Thrive in portrait mode so the keyboard does not hide the settings
...
2- Go to Settings >> Wireless and Networks >> Wi-Fi settings >> tap your network name, Tap FORGET
Now when your network name shows up again under wifi settings ....
select WPA2
Enter password, it is case sensitive.
3- tap the triangle where it says DHCP, select "static"
enter 192.168.1.173. (a nice odd numbered unused ip, away from the auto assigned ones).
(You are making it an odd number (173) because if you buy, in the future, something like a network drive, or AppleTV, it will probably come with a nice "multiple of five" static number like 150 or 155 or 35
the "CONNECT" is greyed out .... right?
4- enter routers gateway 192.168.1.254
enter prefix 24
enter dns1 192.168.1.254
5- the"CONNECT" brightened up again? Tap CONNECT.
....... OR ..........
CONNECT is still greyed out? Enter DNS2 192.168.1.254, tap CONNECT
ARE YOU CONNECTED???
If NO
1- update the router's firmware - try connecting again
2- We will give up on the 3800 and add your second router, with different sets of DHCP ranges, and broadcasting on a non-conflicting channels to the 3800's channel ( channels 1, 6, and 11 do not conflict with each other - assign one router to channel one and the other to channel 11, and keep them a couple of feet away from each other.
shakefry, Please Let us know how it goes, which solution worked ... so other forum readers can help their little sisters too ....
we are standing by (actually in my comfy recliner waiting ..)
Thanks, bobj
aka Bojo, or Obi-Wan, or RouterRooter
I was able to connect to wifi consistently and access the Internet and YouTube app successfully. Hope this helps someone else!!!
Source: http://www.thriveforums.org/forum/t...1-thrive-will-not-connect-t-2wire-router.html
Glad to hear you got it going. I actually fixed mine about 3 days ago. I read somewhere changing your ssid inside the router helps. Well, I did and it actually worked. I haven't had a problem with my wifi signal yet. On mine what was happening also was whenever my phone would go into sleep for say 5min and I went to use the Internet immediately. It would take the wifi about 20-30secs for the wifi to wake up. So far, since changing my ssid I haven't had that problem at all.
Sent from my Samsung Galaxy S3
iLogikk said:
This is what finally worked after two weeks of researching! Found this here for the toshiba thrive but it worked for mr!
. . .
2- Go to Settings >> Wireless and Networks >> Wi-Fi settings >> tap your network name, Tap FORGET
Now when your network name shows up again under wifi settings ....
select WPA2
Enter password, it is case sensitive.
3- tap the triangle where it says DHCP, select "static"
. . .
4- enter routers gateway 192.168.1.254
enter prefix 24
enter dns1 192.168.1.254
5- the"CONNECT" brightened up again? Tap CONNECT.
....... OR ..........
CONNECT is still greyed out? Enter DNS2 192.168.1.254, tap CONNECT
. . .
Source: http://www.thriveforums.org/forum/t...1-thrive-will-not-connect-t-2wire-router.html
Click to expand...
Click to collapse
Thanks for posting a followup.
Did you delete and re-add the WiFi network on your phone, configuring it for a static route and IP address that was in the range on the router, essentially?
- ooofest
Hi there, I've had a lot of help through this forum in using my Android tablet without registering, so I thought this could be the best place to ask a question that's beginning to wreck my head.
I have a Versus 7 Touchpad, and while I know it's just a rebranded something or other made in China, it's actually a decent tablet for the price of €100. Anyway, recently I installed the TPlink TL-WA730RE wireless repeater at home and just have had no luck in getting the tablet to connect to the repeater whatsoever. My android phone (Xperia T), my wife's Nokia E5 and my Compaq PC all connect to the repeater fine and can browse the web/network no problem. However, the tablet just says 'connecting' (to the network) but then reverts back to 'saved, secured with WPA' etc. I know it's trying to connect because if I log onto the repeater through my PC every few minutes the MAC address of the tablet appears along with the status of 'STA -ASSOC', which I think means that the unit is trying to associate with the repeater, but then it just disappears. It may be worth noting at this point that the tablet connects to my TPlink TL-WR841N wireless router running DD-WRT no problem.
I've tried almost everything I can think of, like 'forgetting' the network and reconnecting, ensuring MAC address filtering is disabled, trying static instead of DHCP, resetting my router and repeater etc etc. I even tried apps such as 'wifi strongest signal' from the app store which connects you to the strongest access point in your house if you're using a repeater and walking around. The latest thing I did was to install CM10 on the rooted tablet and everything works apart from the wifi with the repeater, so it wasn't a fault with the original image. Also, the tablet was running ICS 4.0.4 I think, which was the same version of Android as my Xperia T, which connects perfectly.
The last thing I can think of trying is updating the repeater firmware, or installing DD-WRT on it also, but I'm loathe to do that seeing as all of my other equipment is working fine. Other than that maybe there is some sort of updated wifi driver I could try for the tablet itself??
Any ideas would be greatly appreciated!
Just incase anyone else has similar problems with this or any other android tablet, I managed to solve the problem after weeks of headaches.
The problem was that my TPLink wifi repeater's channel width was set to 'auto', where I had other options of 20mhz and 40mhz. Once I paired these with my router -i.e- both the router and the repeater were both set to a wireless channel of 20mhz, my tablet worked perfectly fine. Obviously some equipment can handle the difference in channel width, just not the Versus 7 Touchpad wifi.
Hope this helps someone in the future.
Hello,
I have a galaxy nexus running stock android 4.2.1 with a very peculiar problem. From time to time i have trouble accessing a certain website if i try from wifi or from mobile connection it doesn't matter. If i restart the device the website works without a problem. It was a very odd problem and kept bugging me so i tried to focus on finding the real cause. After a lot of try and error i managed to arrive at this situation:
I have at my disposal 3 different wifi networks (lets call the wifi-1,wifi-2,wifi-3) and mobile broadband connections.
after a reboot of the phone (just to have a clear state) if i connect to wifi-1,2 or mobile conn the website works OK. if i connecto to wifi-3 the site also works OK but then after i disconnect from wifi-3 and connect to any of the other wifi-1,wifi-2 or mobile conn it doesn't work anymore. If i connect to wifi-3 again it works fine on that network.
I've connected to the phone using connectbot and checked the ip address and different params. and i simply can't get a ping to that website. a similar website located in the same subnet but on a different IP still works.
So what could happen on the network layer on the phone to stop working the connection to a certain IP?
Where could i find some info about how to debug IP networking issues on android 4.2.x
PS: I control both the phone and the servers that i'm trying to reach and can't see any traffic coming from the phone on the server.
PS1: I couldn't reproduce the issue with android 4.2.2 only with 4.2.1 (i've also tested android 4.4.4 and couldn't reproduce) i've tested 2 different phones with 4.2.1 and the problem reproduces.
This seems like an issue of handshake and IP Negotiation on the phone. Please see what options you have in terms of DHCP and IPV6 Settings. Please also take a close look at the DHCP Lease time of WiFi-3.
Also Please post in Galaxy Nexus Q&A, Help & Troubleshooting so that the right experts for your device may be of help.
Thank you
Moved here http://forum.xda-developers.com/galaxy-nexus/help/networking-issue-android-4-2-1-galaxy-t2886208
IPv6 is disabled
DHCP is similarly configured on all networks. different IP classes. IP addresses change correctly every time. As i'm able to connect to everything i try except that certain website i don't think it's something related with dhcp.
Hi. Yesterday I got my new Z3, and since then, I've had nothing but WiFi trouble.
My basic home setup:
Linksys EA4500
1 Mediapc with Plex installed
1 Sonos speaker
1 Chromecast connected to my TV
3 pads (samsung, sony tablet z)
Several android phones
Until yesterday (and exept with my Tablet Z - more on that later) my network works as supposed. All units can talk to each other, and most important, my phones and tablet can ALWAYS find and use my Sonos, Chromcast and Plex server. I have a Nexus 5, SGS3, SGS4 and more, and all are connected. Always. Without hickups.
Not so with the Z3. Althoug it says I'm connected - and I can indeed reach outside websites like cnn.com etc.. more often than not the in-house resources are unavailable. Early on I remembered that my Tablet Z had a similar issue, but turning off the Stamina modus on that one always solved the issue. Again, not so with my new Z3. No matter how many functions I turn off - starting with Stamina mode - I'm unable to reach my Plex server, find the Sonos or Chromecast devices. Also, restarting the device or the router don't seem to help either. Even more frustrating, suddenly the phone will find the resources, only to have them drop out again two minutes later... even if the screen was on all the time (did not go into stand-by).
I've turned off all the functions that was part of the reason I bought the phone...
I've changed the router setup to have mixed modes and all other tips I've found on the forums...
I've tried setting a static IP-adress for the phone on the router, and although it lists the phone, still no luck...
(beside the fact that all other devices still connect and work as expected)
I'm extremely frustrated. This is a premium device with a premium pricetag, and I cannot trust it to even connect and use my own WiFi setup.
So in short - please advice.
Schildkamp said:
Hi. Yesterday I got my new Z3, and since then, I've had nothing but WiFi trouble.
My basic home setup:
Linksys EA4500
1 Mediapc with Plex installed
1 Sonos speaker
1 Chromecast connected to my TV
3 pads (samsung, sony tablet z)
Several android phones
Until yesterday (and exept with my Tablet Z - more on that later) my network works as supposed. All units can talk to each other, and most important, my phones and tablet can ALWAYS find and use my Sonos, Chromcast and Plex server. I have a Nexus 5, SGS3, SGS4 and more, and all are connected. Always. Without hickups.
Not so with the Z3. Althoug it says I'm connected - and I can indeed reach outside websites like cnn.com etc.. more often than not the in-house resources are unavailable. Early on I remembered that my Tablet Z had a similar issue, but turning off the Stamina modus on that one always solved the issue. Again, not so with my new Z3. No matter how many functions I turn off - starting with Stamina mode - I'm unable to reach my Plex server, find the Sonos or Chromecast devices. Also, restarting the device or the router don't seem to help either. Even more frustrating, suddenly the phone will find the resources, only to have them drop out again two minutes later... even if the screen was on all the time (did not go into stand-by).
I've turned off all the functions that was part of the reason I bought the phone...
I've changed the router setup to have mixed modes and all other tips I've found on the forums...
I've tried setting a static IP-adress for the phone on the router, and although it lists the phone, still no luck...
(beside the fact that all other devices still connect and work as expected)
I'm extremely frustrated. This is a premium device with a premium pricetag, and I cannot trust it to even connect and use my own WiFi setup.
So in short - please advice.
Click to expand...
Click to collapse
maybe the no. of devices connected to your router is limited? try removing some devices from your server and try it..
Settings > WiFi > Menu > Advanced > Uncheck "WiFi Optimisation"
See if this makes a difference as it disables all power saving features related to the wifi chip.
Mine was useless. But swapped router and seems fine now.
Try a factory reset on the router, clears all data but leaves original passwords and stuff, if you've not messed with the router, then it's a simple fix.
If you have messed with the router then it might be a setting you tweaked. So a reset may help.
Either way, worth a shot