Related
I've had the captivate about 24 hours now and dig it. I've rooted it and remove the att bloatware (per titanium backup), I've also performed a backup using Rom Manager.
I'm having trouble getting it up and running on an enterprise wireless what uses 802.1x PEAP authentication. I can get through all the auth. steps, and the device is assigned an IP, but I am unable to do anything that requires an internet connection; browser, market, etc.
Has anyone else ran into this issue?
*****EDIT*****
sigh i just realized that this is in the wrong area, it should have been over in development...i'm an idiot
I had a similar problem on a WEP-encrypted network, which I fixed by setting a static IP on the phone and then setting it back to DHCP (the correct setting). However, your problem could be entirely different than mine (not that I even am sure what my problem was, just that I fixed it!)
Best of luck!
Having the same problem on enterprise access points regardless of encryption. Home wifi netwroks work great (open and WPA2). Enterprise APs (open and WEP) connect and give me an IP, but will not transfer data. Think its a driver issue with the Wifi, it happens on every captivate ive tested, and seems to be more widespread than the GPS issue.
I have had the same issue with my work at work. I can get it to connect and get a ip but can not pass any data.
Sent from my SAMSUNG-SGH-I897 using XDA App
Had the same problem at work. Luckily I'm an admin and figured mine out. Our monowall portal was the issue. I can give a detailed answer for my problem tomorrow when I get to work.
I actually had the cap wiped to go back, then I literally figured out the problem. Thanks go out to my team mate for helping me talk through this.
Sent from my SAMSUNG-SGH-I897 using XDA App
can't wait to hear what your fix was!
Sent from my SAMSUNG-SGH-I897 using XDA App
This sounds more like your network not being allowing your device rather then the device having an issue.
it's been frustrating as I know two other guys with android devices that didn't have an issue. one is a droid eris running 2.1 and the other is a nexus one running 2.2.
Sent from my SAMSUNG-SGH-I897 using XDA App
designgears said:
This sounds more like your network not being allowing your device rather then the device having an issue.
Click to expand...
Click to collapse
Worked closely with my highly experienced network admin in my dept. for an afternoon (we had some time to kill). He checked the firewall and dhcp servers, ran packet traces, etc.
With what I'm experiencing, its the device. These wifi networks we use with Cisco APs are completely wide-open. All other phones and mobile devices have always worked great for years. We rely on this network for many custom applications and mobile tools.
Once the dhcp server leases an address, it seems like the radio stack hangs, and the device ceases communication. Here's an older thread on the exact issue over at androidfouroms: http://androidforums.com/samsung-captivate/130403-wifi-terrible.html
I have tested multiple new unmodified captivates and the issue is identical accross the board.
Now that I am at work, and have coffee in me and not beer, I will go through the problem I had with miCap and works wireless. Due to my skeptical ways, I will be semi vague for security purposes. On with it.
When I originally got miCap (pet name for it) I was able to access our public wifi. It allowed me into the public portal to agree to terms. I played a little bit on it, but wanted to see if I could access our private wifi. I got in the private no problem. But after that I never was able to get back on to our public. It did the same thing as I've read. It got an ip no problem (via dhcp) and acted like all was well. No browser, or ap could get a connection. The phone would not switch over to 3g to get info.
Armed with ip and mac address, my co-worker and I started to did through our monowall. ( He also has a cap that had no issues on public or private). We try tried reserving the ip for miCap, didn't work. We tried static ip, didn't work. I spent the morning completely wiping miCap to get it back to return worthy.
This was when I decided on last ditch effort.
Our ap's are cisco's that connect into monowall. I got into monowall and dug around. I found that with in the captive portal (how fitting) that the ip/mac associated with my phone hadn't checked in for 8 days. Even though I tried everyday. I deleted the entry to the phone there and suddenly my phone was getting access again.
Now I understand that this may not help everyone, because setups vary from place to place. But digging deeper into configurations at the access points may be what is needed. Do I think the phone had nothing to do with it? No, I think it helped aggravate the problem.
We have had problems with the Intel 3945abg chipsets with the same exact setup. That problem was fixed with driver updates on the laptops.
sorry for the long winded reply.
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Pmac25 said:
So in a nut shell you deleted the DNS entry for that ip/mac in the firewall and you are working.
Click to expand...
Click to collapse
Essentially yes. But it is not listed like that in the portal. Hmmm. I wonder about the combo of dhcp/dns being the culprit.
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
I sent a help ticket into samsung; maybe if enough folks do we can get it on their radar.
jhannaman82 said:
I was able to resolve this issue by changing my connection settings from DHCP to static for the Cisco APs.
Installing WiFi Buddy from the market allowed me to access these connection settings.
I just used an address from our static IP pool.
Manually set IP, subnet, gateway, and DNS, and now im finally rolling on our enterprise wifi network
Click to expand...
Click to collapse
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
phlunkie said:
you can set the ip manually with out an app. When on the wifi screen, hit menu-advanced. This is a good time to set the wi-fi sleep policy also.
Click to expand...
Click to collapse
Thanks for that, i figured the menu was built in somewhere just never found it.
:thumbsup:
UPDATE
So I flashed the i9000 Eclair rom last night, and when I got into work today I can connect and use the wifi here. So looks like something AT&T buggered up, big surprise there, when they "customized" the captivate.
As much as I normally love blaming AT&T for problems, that can't be done here. My Captivate (running Stock Firmware) connects just fine to my work network. We use 802.1x with PEAP/MSCHAPv2 for authentication.
Anyone been able to connect at over 802.11b speeds while connected to an 802.1x network? I show connections at G and N speeds on my WPA2 network but nothing over 11Mbps on 802.1x.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi,
I am also having problems with my work wifi network.
It is 802.1x, on TTLS/PAP it also requires a thawte premium server ca certificate insalled.
Is there any way to connect this kind of networks?
With my previous iphone 3g it was taking only 4-5 seconds.
I am trying to use PPTP VPN with MPPE encryption enabled to connect to a network with a WRT54GL running dd-wrt-vpn running the vpn server. I know I have the server setup right, and I have added scripts to the server pptpd options file to require encryption "MPPE required" and disable compression "nodeflate". Using a rooted EVO 4G with stock 2.2 Froyo, I am able to connect successfully over 3G or 4G, however traffic only works for about 20 seconds, after that, no web pages will load, no ping, nothing, but the vpn stays connected and never disconnects. I know this has been an issue with Android since 1.6, and you can see the post on code.google, issue 4067, it's been there since november 2009, and has still not been fixed. I'm not asking a question about "what's causing the issue", so please don't tell me to use search just yet , what is strange to me is that if I use my Samsung Galaxy Tab 10.1 running Android 3.1 to tether to my Evo with wireless tether, then I can use the PPTP VPN client in 3.1, and it connects and creates a stable pptp tunnel, and I was able to have stable traffic for hours without anything going wrong (except for the Evo battery temp reaching 100F after some time ). They had reported on that issue 4067 that even the later versions of android don't have a working pptp and ppp0 client, so that's obviously not correct.
Anyway, I read a post here (in the Samsung Epic 4G forum) by member "drunix" from september of last year that said he was going to try to recompile the client with MPPE encryption enabled (assuming that is the issue in 2.2) if no one else has done it yet or tried to fix this yet. I don't think it's just the encryption that is the issue, because even with encryption disabled both on the server and client, traffic dies again after about 20 seconds.
So judging from what that member wrote, even though SO many android phone owners have complained so far about the pptp vpn client not working properly in Android versions 1.x and 2.x, no one has so far successfully fixed this issue yet, no one has even acknowledged or attempted to look at this issue yet so far other than that one member, not even the OS manufacturer. I have a hard time believing that the independent developers here and everywhere else make all these custom roms and kernels and other very impressive things from scratch, but no one has even touched this issue when functional pptp and ppp0 already exists almost on all other computer OS's and other platforms, and iPhone, WinMo and linux ALL have functional clients. All apple users say that they can successfully use the phone to connect to a pptp vpn. I guess this must not be important enough to catch the attention of any devs not only from google, but not even here. Is there any way some of the very knowledgable devs here, who can so easily root any new android version that comes out, take a look at this to see if they can fix it so android can be fully functional in all its included features like apple? I think this is the only major issue where android does not function as well as iOS, otherwise it is ahead of the iphone in every other aspect, so why not try to fix this for those who have the knowledge and fix things that are way more complicated than this?
Thanks
Are you referring specifically to 2.2 versions? If so I cannot answer since I am running 2.3.4 modified stock sense 3.0
Also I have successfully used at least three of the available VPN clients to support a IP/Sec connection to both secured servers and routers (mostly routers) with no drops, lock ups or related.
For me, the VPN clients work and have worked but maybe you are referring to something specifically different.
Hope that helps
Hey, I was hoping I could get some help with this. I must be doing something wrong because I've spent a ridiculous amount of time on this project and have nothing to show for it.
I want to run a mobile hotspot on my phone, but not nearly enough to justify paying Verizon an extra $30/month for tethering. I'd only use it a few times a month and wouldn't push a lot of data thru, plus I'm paying them for an "unlimited" data plan - I won't get into that, you know where I'm coming from. I know they probably won't do anything about it since I'm using it so little, but I want to add an extra layer of security via an SSH tunnel or a VPN. I'm sure they just have to run a very basic report on their system to catch somebody who's tethering, and who knows when some manager will tell them to run it on every user vs just the high bandwidth ones? They could force me onto a more expensive plan, disable my account, throttle my connection, or just block any port an Android phone doesn't normally use, and they could do all that automatically pretty easily. If all my tethering data is encrypted they'd have to do some actual work to prove I'm tethering and probably won't think it's worth their time.
I installed OpenSSH on my home PC, forwarded some ports, and put the SSHTunnel app on my phone and it works great. It seamlessly moves all traffic over my SSH tunnel, except for the mobile hotspot. Which was kind of the point of the whole exercise! I looked all over the place but could not find a way to resolve this.
Next I looked at setting up a VPN so I loaded TomatoVPN on my router. The default VPN (OpenVPN) option for that firmware is IPSec with a CA certificate, so I went about setting that up. Apparently the default Android VPN client doesn't work well with IPSec because I can't get it to work - it keeps prompting me for a username and password, but it won't accept my router's admin credentials. None of the tutorials mention that prompt and I can't get around it. I messed around with an IPSec PSK VPN but couldn't get Android to connect to that either.
I looked into PPTP a bit but they say it's not supported by Linksys or OpenWRT, and from my experience Tomato doesn't appear to work with it either. I was going to put a PPTP server on my PC but saw somewhere that many routers can't forward PPTP requests from a WAN into the LAN.
So I went back to the IPSec approach, figuring the problem is with the Android client. I tried putting OpenVPN on my phone, but got stuck where I have to register a tun.ko file using the terminal. I don't even know if I found the right tun.ko. Then I realized I was trying to install an app to configure an app that installs another app and maybe I wasn't going about this the right way.
Does anybody have any advice? How should I approach this?
Here's what I'm using
Phone: Rooted HTC Thunderbolt
Carrier: Verizon
Ugh, looks like Verizon is 1 step ahead of me:
jbenisek.wordpress.com/2010/10/05/android-2-1-and-2-2-vpn-pptp-over-verizon/
Well, that sucks.
OK so device is a - LG D80210B - 16GB - UK - EE - UNLOCKED - ROOTED - StockMOD rom with update package. 4.5gb storage space left.
2nd device is a - HTC ONE 16gb - STOCK - NO ROOT
3rd device is a - SAMSUNG RV510 Laptop.
Im on EE uk network on both phones with EE ADSL Broadband at both mine and my partners house.
Now.... One would assume everything from the same company would be simple... If only that was the case! haha.:silly:
Now which ever property I visit within 15 - 20 minutes of being on the Wi-Fi the LG G2 kicks everybody out of the router, all at the same time. No one can access the network until one of 2 things happens... either I disconnect for 15mins plus or the router gets restarted nothing else will bring back the internet. Note - This does NOT happen when I am not present and surfing can be achieved all day on any device.
So ive spoken to the useless turds at EE technical support on the phone about 30 x they have absolutely no idea what the issue is but its definitely only related to my device. There suggestion is to cancel and go back to sky (which worked flawlessly previously to EE being installed). this is an option but it means another month with no internet at all and I also get an additional 10GB of 4GEE data on my phone allowance if I have there broadband so it would be beneficial to keep it.
Things ive tried;
Every different setting under the sun.
Different encryption.
Static IP addresses.
DCHP settings.
the brightbox will only broadcast internet on 2.4ghz as well if it helps anyone diagnose.
Using a known router as an access point to see if that solves the issue - again perfect until I log on.
Tech support.
Search the net and forums on here.
Spoken to a networking wizard mate of mine.
The problem seems to lie in the LG G2 and/or Jellybean firmware currently installed and installed as stock as the fault is not present when I log off the Wi-Fi...
So..... I decided to try a different rom, the Slim Kat rom
The Wi-Fi works flawlessly for me and everyone else however the rom is just too unstable at the moment to be a daily driver. It doesn't have the complete knock on knock off features and I don't really like the look I much prefer the stock rom as well as some of the games I play just will not work.
Now ive had and been flashing smartphones for about 8 yrs with the help of you lot on here leedroid especially was one of my faves so im not a novice or anything im just lost for what else to do or try????
Has anyone else experienced anything similar?! I would send it away to see if its a hardware fault but as it works perfectly on kitkat I assume its got to be some kind of bug in jellybean.
OR ive changed something that's ****** it up.
I would really appreciate any imput at all because I have a phone I cant use at my partners house or at home ...
Cheers brett
Just to add it also does it when Im on my own i.e. just the phone.
bump for today.... this is really breaking me now as no one can use the wifi for longer then 15 minutes lol
So theres not one single person that has even the faintest idea of what my issue may be?
Someone had this issue before, read about it. A router update fixed their issue. If setting device static, the router also needs to be configured to hold it, try this with all devices and lock local IP's. Next, leave a device off and see if it gets kicked. The G2 seems a bit picky with routers... On the Comcast Technicolor, it won't push past 3.5 dl, but max up. Some old drt firmware has problems as well.
Steamer86 said:
Someone had this issue before, read about it. A router update fixed their issue. If setting device static, the router also needs to be configured to hold it, try this with all devices and lock local IP's. Next, leave a device off and see if it gets kicked. The G2 seems a bit picky with routers... On the Comcast Technicolor, it won't push past 3.5 dl, but max up. Some old drt firmware has problems as well.
Click to expand...
Click to collapse
Thanks for the reply dude...
Yeah tried to update it but its telling me its on the most recent software even though its date is 2010. Called tech support they say it up to date.
I can set the IP in the DHCP section of the router but I cannot for one second find out how to do it on the phone... do you know?
I used DHCP to assign a static IP to both phones, the Nintendo wii, the sky box and the laptop, so they always pick up that IP from the router without fail. I also set the DHCP settings so that it does not conflict with any of the locked IP's just incase - so DHCP is from 192.168.1.2 - 192.168.1.99
Its not a router problem as much as id like to blame it on that because I used my old known working sky router as an access point to connect to as well and that make absolutely no difference apart from slow it down because it doesn't support "N" mode.
Its an EE brightbox router - piece of *****
I can leave the other 4 devices connected to the router 24/7 with no issue until I connect the LG G2. Then all devices are booted at the same time usually 15-20 mins sometimes less. never more. it also only occurs when just the LG is connected. Like now my phone is stuck at recovery ATM (another problem im trying to solve) and the internet hasn't dropped once my partner is on it and so is the sky box so its DEFO my phone that's doing the bad.
That's ODD that isn't it my up and downstream in the router are both above 10meg although the attenuation and line noise keep changing.
cheers for the input
In wifi menu of phone, hold on connection and select modify. Check show advanced options, chose static, input data(along with password again). Reboot phone. After you fix it of course.
Steamer86 said:
In wifi menu of phone, hold on connection and select modify. Check show advanced options, chose static, input data(along with password again). Reboot phone. After you fix it of course.
Click to expand...
Click to collapse
I ended up getting a new router that seems to be ok so far... what does that actually do? Thank you so much for it suggestions
Sent from my LG-D802 using xda app-developers app
Sets static for phone. Has to be set on both router and phone. I just found out the G2 has some issue with AES on certain routers. Try TKP only. I had to do this with my other Technicolor. Odd thing is AES works fine on the SB 6141. Lost on that one.
Had exactly the same issue with my shiny new G2. Using a Netgear modem/Router. I upgraded the firmware and that seems to have fixed it. It was killing the Router within about a minute of use. Now running 25 minutes without any drops. Fingers crossed it's permanent.
Sent from my LG-D802 using Tapatalk
I have had my new Galaxy Note 3 for about 3 weeks now, and have had an issue with certain apps not connecting to the internet over wifi. All of the google apps (youtube, play store, hangouts, gmail, etc) are not able to connect to the internet over any wifi hotspot, or if they do, they're painfully slow.
I have changed MTU settings on my home router, DNS settings, wifi auto switch is off on the phone.
Here's the kicker. If I enable airplane mode first, then turn wifi on, everything works great. I suspect this to somehow be related to the SIM card? Really should have nothing to do with wifi, but who knows...
I should add that I've owned a couple other android phones that have had this issue, but it seemed to have just "worked itself out" after a day or so. (Droid 4, Stratosphere II)
Have you tried a 30/30/30 hard reset on the router yet?
Does a laptop connected via Wi-Fi also have similar issues?
Sent from my SM-N900V using XDA Premium 4 mobile app
I have hard reset and factory reset the router a few times, even went so far as to buy a brand new router and use it. No difference.
I get 26/8 speeds on two different laptops, and one desktop, all with ping times down to about 18ms (as shown on speedtest.net)
spoke with a helpful rep at verizon today, who supposedly called samsung regarding this fix while I was on hold. My replacement should be here tomorrow. This issue is exactly the same as when older android phones would not connect to google (signal indicators would be white instead of blue). It seems like something to do with ssl traffic.
Anyhow, will post back after i've played with the replacement for a bit.
syntheticexctasy said:
I have hard reset and factory reset the router a few times, even went so far as to buy a brand new router and use it. No difference.
I get 26/8 speeds on two different laptops, and one desktop, all with ping times down to about 18ms (as shown on speedtest.net)
Click to expand...
Click to collapse
syntheticexctasy said:
spoke with a helpful rep at verizon today, who supposedly called samsung regarding this fix while I was on hold. My replacement should be here tomorrow. This issue is exactly the same as when older android phones would not connect to google (signal indicators would be white instead of blue). It seems like something to do with ssl traffic.
Anyhow, will post back after i've played with the replacement for a bit.
Click to expand...
Click to collapse
The next most common thing that it would be is the channel that your router is set to. You want to use a frequency that has little interference and there is an app called WiFi Analyzer to help figure it out for your surroundings.
The reason that the laptops might work ok is because the channel can be set within Windows and are most likely set to a different random number between 1-11 than your phone is.
I have found open channels and used those, which made no difference. I believe this may be a google issue as evidenced here (granted these guys are talking about the nexus 5, the issue is very much the same)
https://productforums.google.com/forum/#!topic/nexus/SN03aclu7B8[1-25-false]
I received my replacement today, no dice. I also bought a new router today, no dice. I've tried every channel 1-12, no dice.
The only thing that works is to enable airplane mode, then turn wifi on. I then see full speeds on play store, youtube, gmail, and hangouts. Interestingly enough, the facebook app is affected by this, as well as all push notifications.
It should be noted that the replacement note 3 exhibits the exact same behavior. This leads me to believe there is a modem issue causing the phone to switch back and forth between LTE and wifi, or something along those lines (if the cell radio is off, wifi works great)
syntheticexctasy said:
I received my replacement today, no dice. I also bought a new router today, no dice. I've tried every channel 1-12, no dice.
Click to expand...
Click to collapse
syntheticexctasy said:
The only thing that works is to enable airplane mode, then turn wifi on. I then see full speeds on play store, youtube, gmail, and hangouts. Interestingly enough, the facebook app is affected by this, as well as all push notifications.
It should be noted that the replacement note 3 exhibits the exact same behavior. This leads me to believe there is a modem issue causing the phone to switch back and forth between LTE and wifi, or something along those lines (if the cell radio is off, wifi works great)
Click to expand...
Click to collapse
That is truly odd. I suppose it could be believable that an ISP throttled traffic to specific blocks (net neutrality anyone?), but I don't know why that would cause an interface change on the handset.
There are some apps which are network interface aware - e.g. as an example carriers will use split DNS and inbound IP firewalling so only people on their own network can resolve the IPs of MMS (APN) servers or *send* data to them. That prevents them from being DDOS'ed and I suppose other attacks from anything but their own network - which they have well instrumented. But that means that the MMS apps can not use whatever IP interface happens to be up - either for DNS service or for IP routing - so they need to be able to bring up a specific IP interface, use DNS that is bound through that interface, and route through that interface as well.
I was going through the apps on my phone the other night with a package browser (Package Explorer (Ribo), btw) and I was stunned at how many apps have "CHANGE_NETWORK_STATE" privileges.
What I'm wondering is if you have an app installed that has gone nuts and is toggling on/off your cell I/F. Something like that would be consistent with your observations.
Is there anything relevant happening in your device logcat when this is going on?
.
bftb0 said:
That is truly odd. I suppose it could be believable that an ISP throttled traffic to specific blocks (net neutrality anyone?), but I don't know why that would cause an interface change on the handset.
There are some apps which are network interface aware - e.g. as an example carriers will use split DNS and inbound IP firewalling so only people on their own network can resolve the IPs of MMS (APN) servers or *send* data to them. That prevents them from being DDOS'ed and I suppose other attacks from anything but their own network - which they have well instrumented. But that means that the MMS apps can not use whatever IP interface happens to be up - either for DNS service or for IP routing - so they need to be able to bring up a specific IP interface, use DNS that is bound through that interface, and route through that interface as well.
I was going through the apps on my phone the other night with a package browser (Package Explorer (Ribo), btw) and I was stunned at how many apps have "CHANGE_NETWORK_STATE" privileges.
What I'm wondering is if you have an app installed that has gone nuts and is toggling on/off your cell I/F. Something like that would be consistent with your observations.
Is there anything relevant happening in your device logcat when this is going on?
.
Click to expand...
Click to collapse
There are no apps installed other than the stock verizon/samsung apps. I have reset to factory in preparation for sending this unit back to vz, however it appears i'll be keeping it since the replacement didn't work any better.
Nothing interesting from logcat. Just a lot of IRListener messages, and DalvikVM occasionally clearing ram.
I can see why you would be pulling your hair out.
And the fact that you observe the same behavior with two different units (completely different hardware) and two different routers means one of two things:
- the problem is the handset/software
- the problem is not the handset/software.
Not trying to be funny there. What I mean by the above is that for you to pull two devices out of Samsung's production line at random (unless you happened to get two devices from a single batch of defective units), then the problem couldn't possibly be a low-probability defect thing: either it happens on a very large fraction of all N3 handsets, or the problem actually has nothing to do with the handset at all.
e.g. suppose Sammy shipped handsets where 1 out of 100 had the problem you observe. For you to end up with two of them in a row, the odds of that happening would be 1 in 10,000. If affected half of all handsets, then your odds would be more reasonable - 1 out of 4.
But it sure seems like if it affected half of all owners... or even 10% of all owners, people would be piling in in droves to complain.
I haven't noticed it on my N3, but I have other devices so I'm not sure how much I have used it for e.g. Youtube streaming. I do leave both WiFi and the cell on, and haven't noticed what is happening to you, but I am on MJ7 instead of MJE, and my WiFi is older (802.11g), so maybe if it is a bug it that wouldn't even show up with my setup even if it were the N3's fault.
(BTW, that offers a suggestion - because the N3 is so new it has 802.11ac capabilities - and I suppose your new router does too - if you turn off some capabilities, does the problem disappear? For instance turn off 802.11ac or 802.11n or 5Ghz band usage on the router, does that change anything?)
The other alternatives? Some kind of burst RF noise in your local environment? You earlier said
are not able to connect to the internet over any wifi hotspot, or if they do, they're painfully slow.
Click to expand...
Click to collapse
were the "any wifi hotspot" APs that were all relatively close to a single location, or were they widely dispersed (miles apart)? If they were miles apart, then the problem isn't ISM-band interference. Even if it were, interference from non 802.11 devices (bluetooth devices, baby monitors, microwaves, some wireless cameras, etc) isn't going to show up using a scanning app. Relatively sophisticated equipment would be needed to make that determination. Or a search and destroy mission.
I will say that I had a similar problem a few weeks back (using completely different gear) - I was tethering to a different Android phone (USB tether), and Web browsing on the client device (N7 tab) was fine except the Google Play store app - data would only come dribbling out of it. I couldn't even complete a single app listing, much less begin an app download. At the time I just chalked it up to a temporary problem with Google's Play store. But now it makes me wonder if it isn't something more subtle - as you noted, Google servers seem to be a commonality you are observing. Maybe some ridiculous bug involving Google's single credential efforts?
Well, now I'm rambling and I really haven't given you a suggestion. Maybe something I said will jog you in a different direction and you'll figure it out. If it really is something generic to the current Note 3, it seems like Google would want to know about it. I wonder if it is even possible to get telephone support from Google - they don't really have a reputation as being a consumer-oriented business.
good luck
.
Thank you for all of your help. I am sort of an amateur RF "enthusiast" myself. This happens in more than one location, literally every wifi location i've connected to.
I do believe on past handsets a new sim card sorted this out for some reason, however the vz rep that I spoke with activated a new one that I had gotten with the note 3, but not activated at the time, since my droid 4's sim card was "current enough".
I am lead to believe that this is a modem firmware issue, due to the fact that when the cell radio is off (doesn't matter if mobile data is on or off) the wifi works great. I am running MJE, and would be willing to try and downgrade to the previous radio to see if it makes a difference, but I don't know if that's even possible without causing some damage.
edit: I just realized that the replacement phone is running MJ7...so not sure it would matter.
Resolved
Ok guys, I figured this out, sort of.
I went into an angry router swapping/resetting frenzy when I figured out that the replacement acted the same.
My original setup consisted of: (I have a lot of wired devices in my house)
Comcast Gateway (set up as a normal cable modem, wifi/firewall/dhcp disabled) ----> Linksys WRT54G w/ DD-WRT (wifi off, using for firewall/routing) -----> Zonet N router (no dhcp, using as a switch, wifi off) --------> Linksys BEFW11S4 (used as a switch) ------> Netgear WNR1000V2 (used as a switch and second wifi access point occasionally)
During this frenzy, I eliminated the Zonet unit, and the BEFW11s4. My network now looks like this:
Comcast Gateway ----> Netgear WNR1000V2 (router/firewall/dhcp/wifi access point) -----> WRT54G (as a switch)
This seems to have solved my problem. I noticed while troubleshooting that if I disconnected the segment between the Zonet and the BEFW11S4, my phone would work perfectly fine. I believe that taking the BEFW11S4 out of the picture solved my problem, even though my data was not riding on that segment of the network.
Still, I am perplexed as to why the airplane mode trick fixed the issue.
LOL. I have a pile of Cisco routers if you want to buy them - and I'll throw in some token ring gear and another BEFW11S4 for free.
But seriously - you did the right thing by (experimentally) simplifying; the more complex an environment is, the more opportunities there are for bug expression.
Glad everything worked out - and I await your PM inquiring about my Cisco pile
I never wanted to upgrade from my WRT54G V1! What an awesome, rock solid router! However, need faster wireless speeds nowadays.
I was trying to keep that as my firewall, since the dd-wrt firewall is so much more robust than that of the netgear, also the netgear does not support nat loopback (something I really would like to have)