What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

home Wifi not working

I have a droid 3 taht is having wireless connectivity issues. this is not working at our office is not working or office who is an, I called motorola and they helped me reset the router last week, it worked for 1 day and not again.
also, the wireless connection is FAIR TO POOR at my house with this phone and was never that way with my droid LG ally.
please advise,
my email is [email protected]
please text me your name and #

Please PM any private information.
 
Last edited by a moderator:
So here's the deal. I have a new Bionic and I'm able to connect to my work WiFi but when I come home I'm able to connect to my home WiFi but no joy for passing traffic. I rebooted my router, verified that I was pulling the correct IP and I have no restrictions for mac's on my home router. I'm passing traffic on all other wireless devices in my home (to include the PC I'm currently typing this message). I've rebooted the phone, reset the wireless WEP and still no joy. Before I spend the time to WireShark my wireless traffic I wanted to know if this is a bug with the Bionic? I'm running my Apple AirPort in Bridge mode and I have a commercial grade router (DHCP server). Any suggestions?
 
So here's the deal. I have a new Bionic and I'm able to connect to my work WiFi but when I come home I'm able to connect to my home WiFi but no joy for passing traffic. I rebooted my router, verified that I was pulling the correct IP and I have no restrictions for mac's on my home router. I'm passing traffic on all other wireless devices in my home (to include the PC I'm currently typing this message). I've rebooted the phone, reset the wireless WEP and still no joy. Before I spend the time to WireShark my wireless traffic I wanted to know if this is a bug with the Bionic? I'm running my Apple AirPort in Bridge mode and I have a commercial grade router (DHCP server). Any suggestions?

I had this with the D3 and found the issue seemed to be with using a wireless-n router (802.11n). I found that regardless of security (WEP, WPA, WPA2 or none) I still had issues. Changing the router settings to wireless-g (802.11g) was the solution I found. After rooting and installing CM7 and later CM9, I was able to use wireless-n protocol again. To me, this is a clear indication that there was/is something wrong with Motorola's software that caused the issue. If you are running stock software and wireless-n on your router, your two possible solutions include changing your phone's rom to an AOSP ROM or using wireless-g only on your router. I could be wrong, but test this out for yourself and post your findings.
 
I had this with the D3 and found the issue seemed to be with using a wireless-n router (802.11n). I found that regardless of security (WEP, WPA, WPA2 or none) I still had issues. Changing the router settings to wireless-g (802.11g) was the solution I found. After rooting and installing CM7 and later CM9, I was able to use wireless-n protocol again. To me, this is a clear indication that there was/is something wrong with Motorola's software that caused the issue. If you are running stock software and wireless-n on your router, your two possible solutions include changing your phone's rom to an AOSP ROM or using wireless-g only on your router. I could be wrong, but test this out for yourself and post your findings.


The problem I have is that my AirPort is 802.11n with back compatibility to b/g. I'm not able to choose only 802.11b, sadly this is a work phone and I wasn't thinking about rooting the phone until now. I agree that it appears to be an issue with the software (how did they not find this in there testing).
 
The problem I have is that my AirPort is 802.11n with back compatibility to b/g. I'm not able to choose only 802.11b, sadly this is a work phone and I wasn't thinking about rooting the phone until now. I agree that it appears to be an issue with the software (how did they not find this in there testing).

Not 802.11b, 802.11g. If you are unable to select that, you might need to look into a ROM.

Sent from my XT862 using Tapatalk
 
The problem I have is that my AirPort is 802.11n with back compatibility to b/g. I'm not able to choose only 802.11b, sadly this is a work phone and I wasn't thinking about rooting the phone until now. I agree that it appears to be an issue with the software (how did they not find this in there testing).

I have a D3 with Airport routers in the house (three of them, one on each floor, all set to the same SSID and running 802.11 n with b/g compatible* with WPA2) and the D3 connects just fine to all of them. I had a Bionic for a couple of weeks and that worked fine here as well.


* Actually, the newest Airport Extreme at the border - so, the connection to the internet that all the other routers are bridged to - is set to "Automatic", though it says underneath "802.11 a/n - 802.11 b/g/n".
 
I did a deep dive into my router and wireshark my Bionic traffic and it appears that my router is causing the issue. I can see the Droid sending a SNY packet but my router is reporting " Blocked NAT- out fail, First packet in connection is not a SYN packet: TCP 192.168.20.3:49180->17.149.36.158:5223 on ixp1". I then removed my router from my network and hung my AirPort off my cable modem directly allowing my Droid to pull a public IP. The Droid worked like a champ! I apologize to Motorola for blaming there software. As for my "Carrier Access Adit 3500" home router that is no longer supported by Turin or provides a software update or new release since 2008.....well my 11 year old son gets to take it apart now. A death reserved only for equipment that fails epically!
 
I did a deep dive into my router and wireshark my Bionic traffic and it appears that my router is causing the issue. I can see the Droid sending a SNY packet but my router is reporting " Blocked NAT- out fail, First packet in connection is not a SYN packet: TCP 192.168.20.3:49180->17.149.36.158:5223 on ixp1". I then removed my router from my network and hung my AirPort off my cable modem directly allowing my Droid to pull a public IP. The Droid worked like a champ! I apologize to Motorola for blaming there software. As for my "Carrier Access Adit 3500" home router that is no longer supported by Turin or provides a software update or new release since 2008.....well my 11 year old son gets to take it apart now. A death reserved only for equipment that fails epically!

So the Droid will not work if NAT is enabled on the router? I would like a better understanding g of this issue since I have had many people ask about it. I never really dug that deep since I have my primary router (802.11n) and a wireless bridge (802.11g) in my house and stopped investigating when I could connect with the bridge and not the primary.
 
So the Droid will not work if NAT is enabled on the router? I would like a better understanding g of this issue since I have had many people ask about it. I never really dug that deep since I have my primary router (802.11n) and a wireless bridge (802.11g) in my house and stopped investigating when I could connect with the bridge and not the primary.

It's not a NAT issue it's more of a failure in the TCP/IP handshake between the Droid and my modem. My router some how is losing the intitial SYN packet from the Droid so when the second packet from the Droid comes in the router views that as a fraud request and then fails the request as a "Blocked NAT-out fail".
 
It's not a NAT issue it's more of a failure in the TCP/IP handshake between the Droid and my modem. My router some how is losing the intitial SYN packet from the Droid so when the second packet from the Droid comes in the router views that as a fraud request and then fails the request as a "Blocked NAT-out fail".

Ok, I see. My next question is how did you come to the conclusion that is the routers fault? When the Droid tries to send traffic, the router denies it because of an incorrect/missing first packet. From what your saying, every other device you have works with this router except the Droid. What makes you sure that the Droid is sending the packet correctly instead of the router losing it?

Sent from my XT862 using Tapatalk
 
I then removed my router from my network and hung my AirPort off my cable modem directly allowing my Droid to pull a public IP. The Droid came up on the 802.11n and was able to pass traffic. Also I'm not having this issue on my work WiFi so I don't believe it's a Droid issue. I added my router back into my home network and again it failed. I'm in the process of replacing my router with a Juniper SRX210, I'll let you know if that fails.
 
I then removed my router from my network and hung my AirPort off my cable modem directly allowing my Droid to pull a public IP. The Droid came up on the 802.11n and was able to pass traffic. Also I'm not having this issue on my work WiFi so I don't believe it's a Droid issue. I added my router back into my home network and again it failed. I'm in the process of replacing my router with a Juniper SRX210, I'll let you know if that fails.

I understand about having the Droid pull a public IP, however my point is that if it cannot communicate from within a private domain, that isn't necessarily because of the router. I am very interested in your results with the new router, please post your findings, thanks. By the way, I hope you are not taking this conversation the wrong way, it is not my intention to be argumentative, I'm just very interested in finding the REAL cause of this issue.
 
I understand about having the Droid pull a public IP, however my point is that if it cannot communicate from within a private domain, that isn't necessarily because of the router. I am very interested in your results with the new router, please post your findings, thanks. By the way, I hope you are not taking this conversation the wrong way, it is not my intention to be argumentative, I'm just very interested in finding the REAL cause of this issue.

In my Wireshark capture I can see the Droid sending the SYN request and then in my router log I can see the failure. As far as the NAT issue when I'm at work the work WIFI is NAT so I'm not thinking it's a NAT issue. I'm going to cut in my new router either tonight or tomorrow and I'll let you know my findings. As far as being "argumentative" no worries.
 
Back
Top