Wifi Problem. Good Connection & ip, but no data after a few minutes.

NLynch

New Member
Joined
Nov 8, 2009
Messages
3
Reaction score
0
I'm currently running a Trendnet TEW-633GR router with WPA2 Personal only with AES.

I have no trouble connecting to the network and my droid shows that I am connected and have obtained an IP. I can use applications, the browser, etc for a few minutes but then suddenly I can't use any internet requiring functions.

If i restart the droid. The wifi works again for a while but once again fails after a few minutes.

Any suggestions?
 
Last edited:

jsaggie

New Member
Joined
Nov 8, 2009
Messages
4
Reaction score
0
I have the same issue. I can connect to the 3G network and run internet apps without any problems, but when I turn on the WiFi, I can obtain an IP and connect (using a Linksys router), but I cannot run any internet apps.
 

dezymond

Tech Support Mod
Staff member
Premium Member
Joined
Nov 11, 2009
Messages
12,049
Reaction score
1,479
Location
Bay Area, California
Current Phone Model
Google Pixel
No problems here. You guys should check your routers. I would recommend resetting your wi-fi and having the Droid reconnect. If not, factory reset. Save yourself at the Verizon store, they'll factory reset anyway, so try it and if it doesn't work tell them you did and they'll replace the phone.
 
OP
N

NLynch

New Member
Joined
Nov 8, 2009
Messages
3
Reaction score
0
UPDATE:

So I think the WiFi is cutting out after the droid goes into sleep.
To fix this problem I set the WiFi sleep policy to "Never":
Settings>wireless & networks>wi-fi settings>advanced(use menu softkey)>wi-fi sleep policy>Never

However, the WiFi still cuts out(although it says excellent connection/signal strength) after a seemingly random amount of time. To fix this i have to reconnect the wifi.

Anyone know how to fix this problem?
 

MaynardLanthorn

New Member
Joined
Dec 30, 2010
Messages
1
Reaction score
0
I have the exact same router (TEW-633GR with firmware 1.0.4.3) -- also using WPA2, etc... This problem happens all of the time with all of my Android devices. I have a Motorola Droid, my wife has the Motorola Droid 2, and we both each have the new NookColor from Barnes & Noble. All four of those devices have the connection problem. They connect, and the Nook reports the status as, "Connected, but no internet". I can see the devices on the network from the router, and they all have active DHCP leases, but the route to the internet seems to get lost somehow.

I looked at the TrendNet log and found this:
[INFO] Fri Sep 25 09:20:49 2009 Wireless system with MAC address 58671A030AAE associated
[INFO] Fri Sep 25 09:20:49 2009 Wireless system with MAC address 58671A030AAE disconnected for reason: Received Deauthentication.
[WARN] Fri Sep 25 09:18:37 2009 A network computer (58671A030AAE) was assigned the IP address of 192.168.1.100.
[INFO] Fri Sep 25 09:18:36 2009 Wireless system with MAC address 58671A030AAE associated
[INFO] Fri Sep 25 09:16:46 2009 Wireless system with MAC address 58671A030AAE disconnected for reason: Received Deauthentication.
[INFO] Fri Sep 25 09:16:45 2009 Above message repeated 2 times
[WARN] Fri Sep 25 09:15:40 2009 A network computer (58671A030AAE) was assigned the IP address of 192.168.1.100.
[INFO] Fri Sep 25 09:15:39 2009 Wireless system with MAC address 58671A030AAE associated
[INFO] Fri Sep 25 09:15:38 2009 Wireless system with MAC address 58671A030AAE disconnected for reason: Received Deauthentication.
[INFO] Fri Sep 25 09:15:28 2009 Wireless system with MAC address 58671A030AAE associated

The date is wrong in the log file (I fixed that on the router and got the same results with the correct date).

I am now trying to figure out why all of the Droid devices connect and then send a "Deauthentication" -- or, at least, why the Trendnet believes they send a "Deauthentication"....

Does anyone have any ideas?

Also worth noting: I have an old linksys wireless router that I put back into operation. I created a secondary wireless network with WPA2 on it with a route to the internet. This connection works fine. The problem seems to be isolated to the TrendNet device... I am going to open an issue with them, as well as hope soemone here has any ideas.

Thanks!
 
Top