Related
Anyone else having trouble with att tilt vpn over edge? I've had several smartphones in the past, the last being tmobile wing, and have never had any problems creating a vpn connection with url exceptions. With this new tilt it seems like I can connect the vpn only over wifi, it does not attempt to connect to the vpn when just using edge. I've reset the device several times both with and without the att customization.
Any ideas for this problem would be appreciated.
Thanks,
-J
TILT VPN Connection problems
I have been trying to make VPN connections over EDGE and 3G also. I find that the connection does get made if I connect manually, but as soon as I try to access something through IE, RD or Opera, it drops the connection. I have seen the connection maintained for up to a minute, but I cannot access anything.
I called ATT yesterday early afternoon. At that point the CSR was a proxy for the tech dept and told me to call HTC. I contacted HTC tech support and they were convinced it was an att softwae problem since the url exceptions worked correctly over wifi.
I called back ATT last night, got a csr who xfer me to a tech rep. He walked through the steps and provisioned isp.cingular apn to see if that would work. It did not. He then sent me to advanced network services where I got someone who definately was either not having a good night or had no intention of actually working that night. After his xfer to a bad extension, I called back to a csr, who then semi-understood the situation ( she was actually excellent help at the time for not being a tech person ) She put me with another advanced network services tech ( the first time she called advanced tech services she was hungup on by the same "Steve" I had encounted a few minutes earlier. Nice work Steve) who walked through the settings a few times, and then suggested I try another tilt at an att store.
Unfortunately it seems as though noone I've talked to yet has a grasp on url exceptions or what a vpn is? Noone from ATT or HTC seems to understand that its the software that's not trying to even attempt to connect to the vpn. I would be fine if it was my problem, vpn wise. I'm sure they're just doing their jobs but it's a little frustrating to pay $550 for a phone to have it no do something your other htc phone was doing last week. Anyways thats where I'm at now. I will try to go to an att store tonight and see if it works on another phone. I'm curious to know if anyone with the regular kaiser ( with the front camera ) is having a similar problem.
-J
Round 1
I called ATT yesterday early afternoon. At that point the CSR was a proxy for the tech dept and told me to call HTC. I contacted HTC tech support and they were convinced it was an att softwae problem since the url exceptions worked correctly over wifi.
I called back ATT last night, got a csr who xfer me to a tech rep. He walked through the steps and provisioned isp.cingular apn to see if that would work. It did not. He then sent me to advanced network services where I got someone who definately was either not having a good night or had no intention of actually working that night. After his xfer to a bad extension, I called back to a csr, who then semi-understood the situation ( she was actually excellent help at the time for not being a tech person ) She put me with another advanced network services tech ( the first time she called advanced tech services she was hungup on by the same "Steve" I had encounted a few minutes earlier. Nice work Steve) who walked through the settings a few times, and then suggested I try another tilt at an att store.
Unfortunately it seems as though noone I've talked to yet has a grasp on url exceptions or what a vpn is? Noone from ATT or HTC seems to understand that its the software that's not trying to even attempt to connect to the vpn. I would be fine if it was my problem, vpn wise. I'm sure they're just doing their jobs but it's a little frustrating to pay $550 for a phone to have it no do something your other htc phone was doing last week. Anyways thats where I'm at now. I will try to go to an att store tonight and see if it works on another phone. I'm curious to know if anyone with the regular kaiser ( with the front camera ) is having a similar problem.
-J
Sorry for that last double post. I did go back to the att kiosk again today and tried another tilt, which had the same results. I decided to return the one I had purchased and think i may try the regular htc kaiser with the front camera.
If anyone can verify that that version of phone works with pptp, that would be great.
From your last message I tried a few other things and I too was able to manually connect ( even get a prompt for login credentials to the vpn ) however the IE still will not try to connet with the url exception or keep the vpn connection open after IE is opened.
It's sad to think the att tilt is not working in thie regard. It takes away quite a bit of functionality for those who do use the vpn feature.
-J
PIE will "ignore" exceptions for work connection using EDGE
I see similar problem with 8525 at&t WM 5.0 device (HTC Hermes) exact version Microsoft ® Windows Mobile™ Version 5.0 with the Messaging and Security Feature Pack. 5.0 OS 5.1.478 (Build 15706.3.5.2)
PIE will "ignore" exceptions for work connection using EDGE. However other applications like “ActiveSync” and “Terminal Service Client” work properly.
If Wi-Fi connection used for Internet, PIE as well works properly.
FYI on previous device 8525 Cingular
Microsoft ® Windows Mobile™ Version 5.0 OS 5.1.195 (Build 14955.2.3.0)
work exceptions works with PIE
it continues...
I ordered htc kaiser, had it shipped opened it, configured, and the results were.....
it would use work exceptions as it should, dialing the vpn when using PIE and calling trying to access a host in the exceptions list.
It did not however want to connect to the host even after establishing a connection with the vpn server.
I dont know why, but I thought of checking the ip address with PocketLan on the gprs interface. The ip address was a 10.x.x.x but the kicker was the subnet mask using 255.0.0.0. That may cause a problem with routing as my vpn tunnel is not a full 10/8 but still a 10/16. Anyway I decided to try the online tech chat and spoke with "Marcus"
I asked if there had been any changes in the last month or so on as far as ip address scopes using wap.cingular He said yes. I'm still not sure if that was actually the case or not . I went ahead and upgraded to the pda connect unlimited to use the isp.cingular, as the "pda personal max" just uses wap.cingular.
I had to connect several times with the isp.cingular to have the connection get a public ip address rather than a nat'd 10.x.x.x. It DOES now work properly with url exceptions, connecting the vpn, the whole ball of wax with isp.cingular
Unfortunately I had already returned the ATT Tilt so I dont have any way to test if it was the att software causing it or not. If anyone would like to let me borrow one for a few days we can do that
I am going to test with another vpn connection using a 192.168 or 172.16 etc. ip scope and see if it works with wap.cingular getting a 10.x.x.x address.
Anyways, thats it for now. I'll post again after the vpn test with the different scope.
Thanks,
-J
Today I setup a vpn server with a 192.168.x.x scope. Using wap.cingular i was able to connect to the vpn and hosts within the vpn.
I tried again to connect to the 10.x.x.x vpn and try to edit the routing table using the PocketLan but each time I try to edit something it returns an error.
I'll have to try to find another utility or see if there a way to edit the routing table.
I'm hoping theres a way to change the default route for the 10.x network.
Here's some of the info when connecting over a wap.cingular connection
ip: 10.67.x.x
gateway: 10.67.x.x ( same as ip address )
subnet mask: 255.0.0.0/8
DNS: 66.209.10.201, 66.102.163.231
WINS: 10.11.12.13, 10.11.12.14 ( kind of hard to imagine any reason for wins entries? 10-11-12-13 seems like they may just be fake address. I dont know how window mobile does it's resolution, but that doesnt seem like it would be in the customers interest to be pointed to non-existant wins, if thats what they are. This may just be place holder entries for the PocketLAN software?)
Here's some of the info when connecting over a isp.cingular connection
ip: 166.128.x.x
gateway: 166.128.x.x ( same as ip address )
subnet mask: 255.255.0.0/16
DNS: 209.183.48.11, 208.183.48.10
WINS: 10.11.12.13, 10.11.12.14 ( same comments as before )
See Arin Whois for this netblock
OrgName: Service Provider Corporation
OrgID: SPC-10
Address: 442 Route 202-206 North
Address: # 485
City: Bedminster
StateProv: NJ
PostalCode: 07921-0523
Country: US
NetRange: 166.128.0.0 - 166.255.255.255
CIDR: 166.128.0.0/9
NetName: NETBLK-CDPD-B
NetHandle: NET-166-128-0-0-1
Parent: NET-166-0-0-0-0
NetType: Direct Assignment
NameServer: NS1.WIRELESSDATASPCO.ORG
NameServer: NS.CDPDSPCO.ORG
Comment:
RegDate: 1993-07-09
Updated: 2005-01-07
RTechHandle: WDSPC-ARIN
RTechName: WDSPCo Helpdesk
RTechPhone: +1-215-489-7599
RTechEmail: [email protected]
OrgTechHandle: WDSPC-ARIN
OrgTechName: WDSPCo Helpdesk
OrgTechPhone: +1-215-489-7599
OrgTechEmail: [email protected]
# ARIN WHOIS database, last updated 2007-11-02 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.
I just thought of testing tracreroutes form both isp and wap.cingular. It does then show the problem with the ip information when trying to route.
When using the tilt though at first, none of this seemed possible at the time ( as I thought I was going a little nuts ) since the url exceptions never seem to attempt to connect to the vpn at all. As if the exceptions were ignored when using anything except WIFI.
Thats it for now. Post something new later.
-J
jakedahs,
Very informative. Looks like its' been a few weeks. New insights?
Best,
Things are still working good with the kaiser and the isp.cingular. I haven't come across another ATT Tilt again to test it out again. Any other things you can think to test to put on this forum?
Thanks,
-J
LOL! I'm so far behind, I don't have a clue.
Tilt and VPN PPTP
jakedahs said:
I called ATT yesterday early afternoon. At that point the CSR was a proxy for the tech dept and told me to call HTC. I contacted HTC tech support and they were convinced it was an att softwae problem since the url exceptions worked correctly over wifi.
I called back ATT last night, got a csr who xfer me to a tech rep. He walked through the steps and provisioned isp.cingular apn to see if that would work. It did not. He then sent me to advanced network services where I got someone who definately was either not having a good night or had no intention of actually working that night. After his xfer to a bad extension, I called back to a csr, who then semi-understood the situation ( she was actually excellent help at the time for not being a tech person ) She put me with another advanced network services tech ( the first time she called advanced tech services she was hungup on by the same "Steve" I had encounted a few minutes earlier. Nice work Steve) who walked through the settings a few times, and then suggested I try another tilt at an att store.
Unfortunately it seems as though noone I've talked to yet has a grasp on url exceptions or what a vpn is? Noone from ATT or HTC seems to understand that its the software that's not trying to even attempt to connect to the vpn. I would be fine if it was my problem, vpn wise. I'm sure they're just doing their jobs but it's a little frustrating to pay $550 for a phone to have it no do something your other htc phone was doing last week. Anyways thats where I'm at now. I will try to go to an att store tonight and see if it works on another phone. I'm curious to know if anyone with the regular kaiser ( with the front camera ) is having a similar problem.
-J
Click to expand...
Click to collapse
I too am having issues with my Tilt and VPN. So when I got the Tilt 10 days ago, I had a blackberry 8300 (Curve), when i left the store they had me on the same BlackBerry Data plan. The VPN worked fine - Perfectly in fact. A few days later when I questioned why I was still using a blackberry plan the CSR at AT&T said I should be on a PDA data plan and changed my service. After that the VPN stopped working. I contacted AT&T chat support and also called their complex data device support department and after changing a bunch of settings on the phone they finally gave up and said they could not support the VPN option. Nice Huh?
When I get home I am going to try connecting over WiFi and trying the VPN. This should tell me if the routing / VPN issue is related to traffic over AT&T or if there is something wrong with the phone.
Additionally, when the VPN worked it used to show a " balloon status " telling me VPN was connecting. Now it no longer does that. Even if I do force the VPN to connect and then try to use the connection is disconnects immediately.
I'm guessing you're going to have the same result. If you'd like we can run through some tests using different scopes of vpn's. I'd be interested in trying the tilt again since I know the kaiser I have works ok and I'm not crazy
VPN
jakedahs said:
I'm guessing you're going to have the same result. If you'd like we can run through some tests using different scopes of vpn's. I'd be interested in trying the tilt again since I know the kaiser I have works ok and I'm not crazy
Click to expand...
Click to collapse
What kind of tests were you thinking?
wap.cingular - isp.cingular / netowrk settings
jakedahs said:
I ordered htc kaiser, had it shipped opened it, configured, and the results were.....
it would use work exceptions as it should, dialing the vpn when using PIE and calling trying to access a host in the exceptions list.
It did not however want to connect to the host even after establishing a connection with the vpn server.
I dont know why, but I thought of checking the ip address with PocketLan on the gprs interface. The ip address was a 10.x.x.x but the kicker was the subnet mask using 255.0.0.0. That may cause a problem with routing as my vpn tunnel is not a full 10/8 but still a 10/16. Anyway I decided to try the online tech chat and spoke with "Marcus"
I asked if there had been any changes in the last month or so on as far as ip address scopes using wap.cingular He said yes. I'm still not sure if that was actually the case or not . I went ahead and upgraded to the pda connect unlimited to use the isp.cingular, as the "pda personal max" just uses wap.cingular.
I had to connect several times with the isp.cingular to have the connection get a public ip address rather than a nat'd 10.x.x.x. It DOES now work properly with url exceptions, connecting the vpn, the whole ball of wax with isp.cingular
Unfortunately I had already returned the ATT Tilt so I dont have any way to test if it was the att software causing it or not. If anyone would like to let me borrow one for a few days we can do that
I am going to test with another vpn connection using a 192.168 or 172.16 etc. ip scope and see if it works with wap.cingular getting a 10.x.x.x address.
Anyways, thats it for now. I'll post again after the vpn test with the different scope.
Thanks,
-J
Click to expand...
Click to collapse
Since they had me change my plan and settings around I called and confirmed that I now have the PDA Connect Unlimited plan. However, in the phone's connection settings what should the two network and subsequent individual network setting be? Mine was set to Media Net and Media Net.
I tried setting it to ATT ISP but it still did not work.
I just use isp.cingular all the time. Have you created work url exceptions for your vpn connection? The problem I was having when I had the tilt is even though I had the exceptions it would never attempt to dial the vpn when going to a web site on the vpn network. I'm thinking it may have been ATT that cripled the phone somewhat. The regular HTC Kaiser I have now works fine.
VPN - TILT
So I confirmed that if I use my WiFi connection the VPN works perfectly.
There is some issue with routing over AT&T data network. I tried chatting with their online chat support and they could not give me the settings I needed. It was clearly beyond their scope of knowledge. I will try calling their complex data support department to see if I can get the right settings.
How can a company offer data services and not understand their own network?
Vpn - Tilt - Settings
I found this posting at the cingular.com forum.
Since I need to call tomorrow to confirm my provisioning and my data plan subscription I cannot tell if they will work but I thought I would make the info public.
Here's what I've done to VPN using L2TP successfully... (someone else)
- Have PDA Unlimited Plan
- Call to have your account "provisioned" to use isp.cingular
- Create a new connection using the isp.cingular settings
- Configure device to always use that connection
- Create a new VPN connection
- Import appropriate certificates (if necessary)
- Disable (preferably remove) Proxy settings in Registry
- Create an Exception list for Intranet addresses
- Configure device networks to use isp.cingular for Internet access and vpn for 'Your Work/Intranet' network
One thing I have noticed is that if I let the device connect automagically to VPN, it will disconnect after a short period of inactivity. If I manually/force connect to VPN, it stays that way until I disconnect session.
I can connect either via 3G or Edge with no issues/problems.
VPN Access over anything on the tilt would be nice
I am unable to either one of my 2 vpn's using any connection configuration. I It seems like it wants to connect but then gives me an error msg telling me to check username and password.
Can anyone shed anylite what I'm doing wrong?
Tilt Vpn over Edge
With a little patience i figured it out! if you connect to your VPN first and then go to IE it will disconnect you. But if you go to IE, Opera, whatever first and then go to the address that you have in your exception list the tilt will connect to MediaNet and then connect to your VPN server and work!
Love my N1.
But when i have connected to my Wi-Fi, YouTube won't load any videos.
It wont access Facebook properly at times. For instance thumbnails does never show. It is worse on FB via Browser.
However when i connect to 3G, everything is peachy.
Is there something wrong with my router?
Is a netgear Rangemax with latest FW.
Running Stock 2.1 at the moment.
EDIT:Now it works fine. But it was like that since this morning. What can cause this?
Did you have problems using your Wi-Fi at the time on a different machine, i.e your PC? It might your ISP and not your phone. Since using 3G is technically a different ISP provider so your home ISP might had a temporary problem.
Another common Wi-fi problem that might occur all of a sudden is when your neighbour decides to buy a brand new wi-fi router and uses the same channel as your router, thus getting interference.
Hello people,
Two days ago I bought a Legend only to discover that it has some issues with Wi-Fi. Here's what I mean:
I did the initial setup fully, set up a Google account, Wi-Fi connection only. Weather and Mail (Imap, not Gmail) work perfectly with my home WLAN, but Market does not. What's even strange - I can only open .bg websites (I'm from Bulgaria) in the browser, but nothing else, not even google.com. Those two work just fine on a 3G connection, though.
I tried all sorts of tricks with my router (D-Link N in mixed-mode if it matters), but it was no good. Even set the phone to be in the Demilitarized zone so as to have no problems communicating on port 5228 as I read Market needs to use... still nothing.
Please, can anyone think of a way to solve this annoying problem?
May thanks in advance!
Did you try switching the router to only b/only g/only n mode?
My router is a D-Link DSDL 2740R N and I haven't problem.
Also the coverage is satisfactory.
Try changing your DNS settings, and check router's MTU. Although just guessing here...
Sent from my HTC Legend using the XDA mobile application powered by Tapatalk
Yes, switching the mode was the first thing I did - going to g/b did no good.
Like I said, I don't have troubles connecting now - just a very limitted access to websites and services.
And what DNS Settings? The ones on the router? But they are working perfectly with my two computers, it's the HTC Legend that has issues.
---
So, I just talked to the support desk of my ISP and they told me they had never heard of such a problem. According to the guy, everything should be working normally because they were not blocking any kind of traffic/ports.
Any ideas?
I finally tossed my old wifi router and got a shiny "new" Linksys E2000 and have it set up pretty much as stock. B/G/N, a few ports open, WPA2 Personal security, etc. Nothing special except that, of course, the Focus won't connect to it. I had to ask a neighbor if I could use his wifi so it would stop whining about email. How many more months until this "phone" can do something useful? Tell you what, how about if I mail a piece of it to Microsoft every month they don't have an update for it and attached to each mangled piece I attach a note that reads "You"? Think they'd get the point then instead of combing their hair around it? I'd just sell it on ebay except what do you get for a Focus these days? $30 if you throw in the sim card? Still might be worth not having to look at the thing every day, tho. Never again, Microsoft. WP7 is as dead a WM....well, no, I can connect my Fuze to the damn wifi.
Linksys routers, especially the new E series, are notoriously buggy. My Focus connects to two of my 11n routers just fine (one TrendNet, one NetGear). So, it looks like it is the problem with your shiny new router.
I concur. I've connected my Focus to dozens of hotspots without issue.
On the other hand, I've had problems and complaints about 100% of Linksys routers that are owned by clients (granted, they call me when they have problems) and two Linksys routers that I managed myself.
I would never recommend Linksys, and will never own another. I have and will recommend the Samsung Focus, however, and will own another Windows Phone.
(For the record, I own a Buffalo router running http://www.dd-wrt.com)
Ever since Cisco takes over Linksys, its Linksys brand getting worse and worse. Not only the initial release firmwares are always buggy, Cisco also deliberately remove features that are common on other brands of consumer routers so that it does not eat into its Cisco commerical grade router business. Most common compliants I read is that WOL packets do not work on Linksys routers and switches after a device entering sleep for a while.
I have a Linksys E2000 and mine works great. I was loyal to the D-Link brand, but their recent routers have had too much trouble. I was resetting my router at least once a week.
I will admit, it seems to be hit or miss with any brand of router. Just go to Newegg.com and you'll see hundreds of reviews both positive and negative for any brand router. Why can't they just make something that works?
foxbat121 said:
Linksys routers, especially the new E series, are notoriously buggy. My Focus connects to two of my 11n routers just fine (one TrendNet, one NetGear). So, it looks like it is the problem with your shiny new router.
Click to expand...
Click to collapse
I kind of doubt that. Every other device I own works just fine. Bridges, iPhone, iPad, Galaxy Tab, 3 laptops, 2 netbooks, other people's equipment....everything that anyone has tried to connect does so and very quickly. Just like at work where there are literally dozens and dozens of devices connected and what won't connect? Why the Focus, of course! Actually, the E2000 is an excellent router and it gets very good reviews nor have I ever had a problem with a Linksys in a whole lot of years of using them. No, I tend to think the Focus is the junk here.
I am sorry my friend but it is not the Focus phone in "general" You must have a faulty device and should take it back to the store to return it or get fixed. There are so few complaints about Focus devices connecting to routers. I have never had a single problem and I have connected to dozens of routers all of different brands and models.
I would definitely take the focus back to the store, if you bought it from an ATT store, at least I hope you did and didnt get it from some other source as you are probably screwed.
I have been so pleased with my Focus, granted all of the setbacks with updates and short comings.
OP:
I have found people with issues connecting their Android & iOS devices to this router as well. The Android post I read suggested using WPA2 (AES) on the router. A iOS person suggested taking wireless settings off auto and actually selecting a channel such as 11 as well as selecting B & G or G & N instead of auto to fix connection issues.
My personal experience with Cisco Linksys routers in the past has been mixed mode can be flaky. When I set the router to G only or N only (use only if all your devices support N) everything runs smoothly.
yup it must be the router, back home my Focus failed to lock onto my Linksys WAG200 gateway if my Laptop was already connected to it. So I had to turn off the wifi on my laptop and let Focus connect to it first and then let my Laptop also connect. Strange
Set your router to g only
Sent from my SGH-i917 using Board Express
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)