Related
Apologies if this has already been asked/answered, but have spent the last two days looking for a solution..
When connected via USB I cannot establish an internet connection, unless I delete the T-Mobile proxy setting.
I've applied the regedit edit that's been mentioned as a solution, but this didn't work.
Is there anyway to use the pass through connection without having to delete the proxy everytime?
The main annoyance is that the phone won't sync with my exchange server whilst connected to the PC. I have mail set up to sync with exchange server and all other items syncing with my PC. My Hermes sync'ed with anything and everything.
Thanks
just leave the proxy out.
T-Mobile's proxy is a pain in the arse and causes all sorts of problems.
I deleted the proxy from my connection on t-mobile nearly three years ago and on every single device i have had since. never had a problem since.
If the proxy is there, it affects ALL internet connections, so when you plug it in to your PC, it is trying to go through a Proxy that you can only access over GPRS.
that's why proxies are a PITA and should be deleted permanently.
and no, it should not affect anyhting if you delete it. or not that i have noticed anyway.
Thanks will give it a go when I get home.
Seem to be able to access internet without the proxy, but forgot my usb cable so can't test pass though at work.. fingers crossed!
When I deleted the proxy I couldn't then send SMS texts...?
That's a completely random coincidence. The proxy has nothing to do with SMS whatsoever.
you can of course make sure that you are using GSM for SMS. start>settings>connections>advanced network>SMS
set it to GSM. if this is already set, then it has nothing to do with the proxy.
Says "Your text message cannot be sent" after I removed the proxy. SMS is set to GSM. Could it have altered any other relevant settings? Have put the proxy back now but it still refuses to send the message.
Any ideas?
no, wouldn't have changed anything else. The proxy has no bearing on SMS whatsoever.
Like i said, i reckon it is just a coincidence, otherwise turning the proxy back on would have fixed it.
If it is set to GSM already try the other three settings as well.
and a soft reset of course....
Have found a cable and tested - still no joy after deleting proxy.
Connecting to PC, and items syncing with host PC are fine. Mail syncing with Exchange server fails and can't access internet via pass through.
Browsing and syncing with the exchange server is fine when not connected to the PC.
Btw kempas - SMS works fine after deleting the proxy setting, as it should do.
Steve
on the handset:
start>settings>connections>wifi (NOT Wireless LAN)> network adapters
set the drop down box to Internet.
On the PC:
Open Activesync>File>Connection Settings
Set "This computer connects to" to the internet.
Dunno what it is in vista, i have avoided it like the plague....
I did a soft reset and tried again (a couple of time) with no luck, unable to send text message.
Went to settings, connections and run through the network provider setup wizard, let it reset the phone and tried again. Settings 'seemed' all the same but SMS now sent without issue.
Will try removing the proxy again later and testing with another SMS.
EDIT: removed the proxy and sent an SMS without issue this time... So was a "completely random coincidence" as rhedgehog said.
Still can't access You Tube via it's mobile client though, at least, it still says no videos...
All now appears to do what I expect after removing proxy and following rhedgehog's advice. Pass through now works Many thanks!
Also appeared that the t-mobile proxy blocks Windows live and messenger
stevecg said:
All now appears to do what I expect after removing proxy and following rhedgehog's advice. Pass through now works Many thanks!
Also appeared that the t-mobile proxy blocks Windows live and messenger
Click to expand...
Click to collapse
Are you on wnw+??
mrvanx said:
Are you on wnw+??
Click to expand...
Click to collapse
Just Web N Walk I believe, not plus, so I guess messenger is a no no. Will bypassing their proxy end up with me being charged for data??
stevecg said:
Just Web N Walk I believe, not plus. Will bypassing their proxy to use messenger end up with me being charged for data??
Click to expand...
Click to collapse
No, but it is against the t&cs to use IM software when on basic web n walk. Tmobile block the ports for IM software anyways, it seems for new customers since several old customers managed to get through.....i never could though, so the proxy would make no difference if it is on or off.
I personally am on wnw+ which is TOTALLY worth it for using the HSPA when out with my laptop on location.
Cheers for that. Won't really need messenger to be honest - but the proxy setting interfering with the pass through was annoying.
kempas said:
Still can't access You Tube via it's mobile client though, at least, it still says no videos...
Click to expand...
Click to collapse
Log into My T-Mobile or call customer services and get the adult content filter turned off.
I think they blocked it to prevent kids blowing mummy and daddy's credit on watching videos.
Of course, Streaming is also against the T&C's of wnw standard, so it could be that this is why. I'm on wnw+ and had to turn off the filter to get it working.
Yep, that was it. Cheers for the reply...
Okay, I'm here in Houston and as of yesterday, I have noticed that it takes FOREVER for certain web pages to load. Specifically, Google.com(along with google search), and Yahoo (m.yahoo.com)
When I switch to 3g and Wifi, they resolve normally. On 4g, it's as if the dns server is having a tough time getting there. The weird thing is when I ping the sites by domain, I'm getting responses on my phone so I'm not even sure if it's DNS. Since if it was DNS I'd get slow responses, or I would only be able to ping it by I.P address.
So, I got an app on the market called SETDNS, and it seems to change my DNS server (I have it set to OpenDNS) and it still doesn't load up these sites fast.
Anyone in Houston having an issues with slow sites?
I've verified that it's not my rom (CUBEDROM) as my Co-worker here is on BAMF and is currently experiencing the same thing. I thought it was just the tower we both happened to be on, but we went somewhere outside of work on the other side of town, and still the same thing
Any ideas?
Samsuck said:
Okay, I'm here in Houston and as of yesterday, I have noticed that it takes FOREVER for certain web pages to load. Specifically, Google.com(along with google search), and Yahoo (m.yahoo.com)
Click to expand...
Click to collapse
FWIW, I'm in Denver and experiencing the same issues on those sites. While on the LTE network, some sites are ridiculously slow to load compared to 3G. I don't believe it's strictly a DNS issue; you'd never get the page to load at all if you couldn't resolve the domain name, you'd just get a 404 or the like.
Same thing with me in Pittsburgh. Even happens when trying to load the XDA app. Just takes forever on 4G but then 3G works fine.
NickWarner said:
FWIW, I'm in Denver and experiencing the same issues on those sites. While on the LTE network, some sites are ridiculously slow to load compared to 3G. I don't believe it's strictly a DNS issue; you'd never get the page to load at all if you couldn't resolve the domain name, you'd just get a 404 or the like.
Click to expand...
Click to collapse
Yeah, you know what you're right. If it was strictly DNS then I would only be able to ping by I.P
So is 4g being routed through a proxy or something?
It's getting annoying because I use google search alot on my phone, and it will only load up properly on 3g.
Hrm, so apparently it's not just a Houston thing.
If anyone could continue to confirm this that would be great.
Purely just a theory, but with the big sites like google.com and yahoo.com, they are testing IPv6 (Global IPv6 test day, started yesterday at like 4pm West time i believe). Possible that your wifi and 3g can handle IPv6, but the 4g switches were struggling? Just a theory.
Same issues here in Detroit, was better 20 mins ago but back to the same problem again.
I agree that World IPv6 Day could be a cause, but that's only if you have trouble routing to the IPv6 address. I'm testing using purely IPv4 addresses for m.google.com (First response I get is 74.14.213.193).
On LTE, I'm averaging 300ms for the first hop (69.83.157.73), and ~75ms for the other hops.
On 3G, I average 130ms for the first hop (69.83.157.73), and ~115ms for the other hops.
If that's on each packet, I'm experiencing about double the load time for any traffic to m.google.com on LTE vs. 3G. Of course, that's not taking into account actual transfer speeds, so some of that might be recouped on larger packets, but still, it's significant.
Same in Columbus, Ohio except that 3g was doing the same thing. I was trying to stream Tunewiki on the way to work around 8am and nothing would load. I tried rebooting but it didn't help. At that point I chalked it up to network problems. I jumped on wifi when I got to work and have been waiting for the threads to pop up here to confirm.
Same thing in socal so its a national thing
good thing we have options to change to 3g
and not 1x
Hrm, that's interesting.
Yooooo, i think you're right
check this article out
http://www.metro.co.uk/tech/865705-google-facebook-and-bing-test-ipv6-as-net-runs-out-of-space
I can't resolve google,yahoo, facebook,and bing is occasional.
They all will failover to IPv4, and I was testing using the IPv4 addresses. I still think there's something wrong here, and the World IPv6 Day stuff is masking it.
I can resolve all of the major sites in DNS and get both an IPv6 and IPv4 address for them. I chose to test with only IPv4 to ensure that my results would be comparable to each other.
Nick, i agree that there is an error here. I'm just outside of my 4g at work, but can you check what your IP is if you are on 4G? I have a sneaky suspicion that there is a correlation here. If we are on v6 and pinging to v4, could possibly see higher load times if there is software glitches on verizons end. Awfully suspicious if they are not related! And i do know the t-bolt is v6 ready, as all LTE on verizon are required to be v6 ready.
Hrm. When on 4g my IP is 166.249.220.38, for 3g my IP is 166.249.197.80
Samsuck said:
Hrm. When on 4g my IP is 166.249.220.38, for 3g my IP is 166.249.197.80
Click to expand...
Click to collapse
Well there goes my theory. Thanks for checking Samsuck.
I too see addresses in the same IPv4 Class A (10.0.0.0) when on either LTE or 3G. I'm seeing non-routables, of course, which then get NAT'd through to a pool of external IPv4 addresses.
Running netcfg on the phone shows that I only get IPv4 addresses. I don't believe that these phones are receiving IPv6 addresses from Verizon, which makes sense if they're non-routable addresses, since they'll have to be NAT'd at some point.
Ok, so netcfg on Android only supports IPv4, which is my bad.
I may have spoke too soon. This guy says his VZ LTE always assigns him a IPv6
www(dot)anandtech(dot)com/show/4289/verizon-4g-lte-two-datacards-wifi-hotspot-massively-reviewed/3
I can't seem to find any sites discussing for definite what IP's VZ deals out on LTE.
Samsuck, was the checker you used IPv6 capable?
cmhfdisker said:
Same in Columbus, Ohio except that 3g was doing the same thing. I was trying to stream Tunewiki on the way to work around 8am and nothing would load. I tried rebooting but it didn't help. At that point I chalked it up to network problems. I jumped on wifi when I got to work and have been waiting for the threads to pop up here to confirm.
Click to expand...
Click to collapse
Same here in Reynoldsburg man. Went down forbme last night around 1am n spotty ever since...
4Geezy ON DopeDiculous's ROOTED TBeezy!
NickWarner said:
I too see addresses in the same IPv4 Class A (10.0.0.0) when on either LTE or 3G. I'm seeing non-routables, of course, which then get NAT'd through to a pool of external IPv4 addresses.
Running netcfg on the phone shows that I only get IPv4 addresses. I don't believe that these phones are receiving IPv6 addresses from Verizon, which makes sense if they're non-routable addresses, since they'll have to be NAT'd at some point.
Ok, so netcfg on Android only supports IPv4, which is my bad.
Click to expand...
Click to collapse
Man it sucks not being on 4g to try myself, but if someone could try usb tethering, and also wifi tethering, then IP checking on a IPv6 capable checker. Might find out if it is the culprit.
When you say checker what do you mean? How did I check my IP?
I just browsed to http://whatismyip.com
I pinged the different sites via the terminal emulator.
nbdysreal said:
Man it sucks not being on 4g to try myself, but if someone could try usb tethering, and also wifi tethering, then IP checking on a IPv6 capable checker. Might find out if it is the culprit.
Click to expand...
Click to collapse
Ok, when I'm on LTE, I do indeed get a public, routable IPv6 address. Using http://whatismyipv6.net on the phone, I can both see the address and traceroute back to it. Awesome.
On 3G, going back to the same site shows me that I only have an IPv4 address. It's a non-routable 10.0.0.0 address that gets NAT'd to a 166.250.0.0 address on the outside.
Anyone try the IPv6 Beta for ICS Nexus S? They have IPv6 enabled on 3G now.
https://sites.google.com/site/tmoipv6/lg-mytouch
Didn't work for me. Lost data.
I set up the apn for it, still waiting on the confirmation from t-mobile saying they've provisioned my number for use of ipv6.
dls5375 said:
Didn't work for me. Lost data.
Click to expand...
Click to collapse
What did not work for you?
I read this review that it worked well. http://www.prolixium.com/mynews?id=963
Highlights were that users get public IPv6 addresses and inbound connections to the phone work
its not working for me either. ive been exchanging emails with a person from that tmobile beta program, and he has a theory why its not working for me, custom rom. im on cm9. cm9 might not include the correct RIL files. i will try with a stock rom later on.
elgato99 said:
What did not work for you?
I read this review that it worked well. http://www.prolixium.com/mynews?id=963
Highlights were that users get public IPv6 addresses and inbound connections to the phone work
Click to expand...
Click to collapse
I set it up the way the instructions said to, rebooted and lost my data connection. It came back when I restored default.
IPv6 works fine for me with the stock Nexus S IML74K firmware, both with the special beta APN and the standard epc.tmobile.com APN (which is IPv6-enabled in the Bay Area). I did some reading on the topic last night for a friend, and it does look like you need support from the cellular radio for IPv6 to work correctly (for Android, I assume that means both baseband and RIL).
Apart from just doing it, what are the advantages of doing it?
mobilehavoc said:
Apart from just doing it, what are the advantages of doing it?
Click to expand...
Click to collapse
Fair question.
To people with mobile phones, the benefits are real public IPv6 addresses that allow for the bidirection flow of traffic. Read -- inbound connections... can have a web server or ssh server on your phone... A phone now becomes a real node on the real Internet, not a "mobile web" experience. Actually, each mobile phone is assigned 2^64 IPv6 addresses... that is a codified standard (yes, there are a lot of IPv6 addresses, no i dont think this a bright, but it is not actually a problem). There is no NAT from IPv6 to IPv6 addresses. But, other than that, not a whole lot is different from a user perspective. One can wax poetic about re-establishment of the internet's end to end principle, or how IPv6 is going to help battery life... but it gets kinda hand wavy. This is why IPv6 has been around for 10+ years without much traction.
The real benefit i see is to the mobile network providers, or Internet in general. Mobile devices are growing at a very high rate and there is just not enough IPv4 addresses to go around. Internet wide, IPv4 is pretty much exhausted.
I thought this article had some interesting pointers http://tech.slashdot.org/story/12/01/13/2348206/ipv6-only-is-becoming-viable
And, Facebook, Google, Bing, Yahoo ... are all turning on IPv6 for good in June. On the Internet, IPv6 is a pretty big deal in terms of how data flows through the tubes.... But, ideally, plane old joes dont have to care about IPv6. It should just work.
Here is some info on the World IPv6 launch day http://www.worldipv6launch.org/
Thanks. I noticed on the site they say P2P services like Skype won't work with IPv6 and there's obviously going to be some compatibility issues. I'm excited to try it out but at the same time I don't want to break apps or functionality. Guessing by this fall people will adopting it more and there'll be less breaks.
Right, some technologies are going to evolve quicker than others. The slashdot article had a link to a list of apps that work and dont work, i think it said 85% work fine... but a few fail. In any event, for this beta, switching between the IPv4 APN and the IPv6 APN is pretty easy (3 taps). I think one of the goals is to create an early adopter critical mass to find the broken things, complain, and get them fixed.
Here is another interesting link about getting the apps cleaned up http://www.gossamer-threads.com/lists/nsp/ipv6/32908
And, if you really want to go deep, there is this code which fixes the broken apps by doing translation on the phone from IPv4 to IPv6
http://code.google.com/p/android-clat/
Works fine for me....CM9 Euroskank kang and the Trinity t132 kernel. The lack of mms support makes it a non daily use apn for me..(kids, grandparents, etc...lots o' pictures)...but otherwise...good to go here...
working here now too. cm9 kang and trinity t144. i did have to flash the newest radio then let it sit there for a bit before it connected to data for the first time. now it connects quick every time. ive found one problem though, it wont let my laptop get data while its tethered, even though the phone has a good data connection. as soon as i change my apn back to the original and let it connect, data starts flowing to my laptop again. will someone else try to tether. it connects fine, just no data flow.
I got it working with the browser but my signal bars never turn blue and Sync doesn't work at all along with most background sync apps. Seems odd. I'm on 4.0.2 stock. I switched back to iPV4 and everything works perfectly. At least I have it configured to try later on in the summer.
mobilehavoc said:
I got it working with the browser but my signal bars never turn blue and Sync doesn't work at all along with most background sync apps. Seems odd. I'm on 4.0.2 stock. I switched back to iPV4 and everything works perfectly. At least I have it configured to try later on in the summer.
Click to expand...
Click to collapse
syncs here just fine with blue bars.
simms22 said:
syncs here just fine with blue bars.
Click to expand...
Click to collapse
Which APN are you using? The website lists one and the email I got from T-Mobile listed a slightly different one?
I tried it again and it worked this time with the blue bars and sync using the scpcf000 APN. Wonder why it didn't work before? Wonder if different towers/regions have issues because I was travelling when it wasn't working. Who knows.
I would keep it but no MMS is a bummer - if there were some practical advantage to using IPV6 right now I'd stick with it but there doesn't seem to be. Yet.
mobilehavoc said:
Which APN are you using? The website lists one and the email I got from T-Mobile listed a slightly different one?
Click to expand...
Click to collapse
epc-scpcf000.t-mobile.com
simms22 said:
ive found one problem though, it wont let my laptop get data while its tethered, even though the phone has a good data connection. as soon as i change my apn back to the original and let it connect, data starts flowing to my laptop again. will someone else try to tether. it connects fine, just no data flow.
Click to expand...
Click to collapse
Yeah, no Internet connection on my laptop when I try to tether either. It looks like Android's tethering infrastructure isn't IPv6-aware yet -- the laptop isn't picking up an IPv6 address, and the phone doesn't have an IPv4 address, so it's not capable of routing IPv4 traffic to the Internet.
That said, even if Android were to grow IPv6-aware tethering, providing Internet access is going to be a problem. I can see four possible approaches:
(1) The phone assigns IPv4 addresses to tethered devices (as it does now), and implements NAT46 to translate that traffic into IPv6 traffic to send upstream. I don't know of any NAT46 implementations, though, never mind any ones suitable for a phone.
(2) The phone assigns IPv6 unique local addresses to tethered devices, and implements NAT66 to push that traffic upstream. (Basically, this is like the current tethering setup, except with IPv6 everywhere instead of IPv4.) Highly experimental NAT66 standards and implementations exist, but their very existence seems to be controversial (one of the original ideas behind IPv6 was to have enough address space to not have to use NAT in the first place).
(3) The cell provider assigns a /64 or larger block of globally-routable IPv6 addresses to the phone, and the phone assigns those addresses to tethered devices. (This is the approach fixed-line broadband providers are taking.) As far as I know, though, there isn't a standardized way to hand out prefixes (other than DHCPv6, which people don't seem to like either), and of course, this requires carrier involvement, with implications for everyone who wants to tether without a carrier-approved tethering plan.
(4) The cell provider assigns an IPv4 address (public or private) to the phone, and tethered clients use the existing IPv4 tethering infrastructure. This requires no changes on our end (it'd work right now on carriers that provide dual-stack access), but T-Mobile has apparently decided to assign IPv6 addresses only and use NAT64/DNS64 to provide access to the IPv4 Internet, so this won't work for us.
I found this article to be well written and informative for IPv6 on ICS http://www.androidpolice.com/2012/0...ere-is-what-it-all-means-and-yes-no-more-nat/
http://dan.drown.org/android/clat/
I tried this code out. It is pretty cool since it allows some additional functionality by doing a NAT from IPv4 to IPv6 locally on the phone. Skype and a few other apps that require IPv4 now work while they did not work before.
I used to tether my nexus 5 to the wifi nexus 7 without issue. The new D6603 works exactly the same way. I can get the two devices to connect to each other, but data trickles through so slow that webpages time out. I know some small amount of data is getting through because from google I can get instant auto suggestions as I begin a search. But if I click on any of the links google brings up the webpage never loads.
I called Tmobile who's mostly useless. Unsupported device yadda yadda. They confirmed my tethering option is still active, but otherwise they aren't helping.
is there a setting or something I need to change? Anybody else have luck with this working, or experience the same issue?
Have you tried multiple locations? There might be wifi interference in your current spot
Yes
It seems like a repeat of the issue I had with T-mobile blocking tethered data when I first got a nexus 5. Apparently they added code to 4.4 to redirect tethered data to a different apn.
Double check your APN settings, try setting the APN protocol to IPv4/IPv6 if it's set to only IPv6
That fixed it! Thanks! It was set for IPv6 only.
Hoping someone can help. I have a Nexus 5 on the AT&T network. Been using it without issue since Halloween 2014. All of a sudden, the past couple of days, I'm having some issues with MMS messages. I started a new group message and only one person received it. I haven't been able to text pictures to people. And today I have been receiving notification stating "Can't download MMS - check your APN settings". I can send regular one on one text messages just fine and sometimes group messages do go through. Sometimes not. Pictures don't seem to be going through at all.
Nothing has changed on my phone and I definitely haven't touched the APN settings. I'm using the "phone" APN for AT&T with all of the correct settings founds online.
I had a friend who's using a 2014 Moto X Pure Edition send me his APN (also AT&T) and he has one called "nxtgenphone" but all of the other settings are identical to the "phone" APN. I've tried added a new APN for "nxtgenphone" but when I select it and then reboot, the phone goes back to the "phone" APN automatically.
Anyone know what could be going on? Is it an AT&T issue? My issue? Other? I'm not sure what to do or check at this point.
Again, everything has worked just fine for months. This is a recent issue the past couple of days.
Thanks!
Bronson
I had a similar issue with Net10. What fixed it for me was moving my active APN to be the first APN.
I just noticed I have the same problem. I am on AT&T with my N5 running 5.1(D) also, my APN it set to ATT Phone, and all settings are confirmed. googled the problem and the "google messenger" app seems to be buggy. It has been updated recently and I think its now more messed up than before...
If on LTE and WIFI I have mms problems
If on LTE, 3g or H only mms goes through!!!
If I use "hangouts" (which I hate becuase if you search for a contact, it puts your google+ contacts up 1st) things seem to work fine in all forms of connection LTE/WIFI/3G/H etc....
So till they fix the "Google Messenger" App, I am forced to use "Hangouts" as it is more reliable for now
I'm on AT&T & the last time I tried the "Google Messenger" App a couple of weeks ago, I had trouble with MMS. I run CM and just went back to the CM messanger, and it was fine. So it seems there is an issue with AT&T & the Google Messenger app that didn't exist before. I wonder if it is specific to the N5 or on other phones.
Well here's another funky thing to add... As stated above I have problems with sending and receiving mms with Google's messenger application at "home" but not with Google's hangout application at "home" where I first noticed the problem. Well while I was at "work" today about 15 miles away from home. I tried Google's messenger application and it worked!!!
So I am now thinking it has something to do with AT&T tower at my home location and Google's messenger application. Since Google's hangout works when I am "home" and away...
Now what???
Sent from my Nexus 5 using XDA Premium HD app
Another update to my dilemma, when at "home" and I turn my "WIFI" off and restart the phone. Things seem to work, as I look more and more into this problem I am having with sending and receiving mms on AT&T. I am starting to see a pattern that Google's Messenger application may have an issue where it is suppose to "Turn Off" Wifi use cellular data to send and receive the mms and then "Turn On" wifi after it is done with the mms process.... But this does not explain why things work while I am not away from my "Home" location!!!!
Getting to the root of my problem!!!! FIXED!!!!!!
I am starting to think that the MMS problem is not with AT&T and the google messenger app, or 5.1(D), or my APN setting!!!!
But with my wifi router at home!!!
After more reading up on this and also the fact that I have "No" problems sending or receiving MMS while "Away" from home using another WIFI source or with WIFI off. I was starting to think if the problem was "Caused" by my wifi router a linksys wrt54g running dd-wrt??? So what I did was to connect to a Public Wifi I have outside of my house and I was able to send and receive MMS without any problems!!!!
Just recently I had to change a setting on my router to allow my xbox360 to download some content.
That setting was to "Allow - UPnP service" I went back into the router, reversed my settings and rebooted the router, made sure my phone was connected to the "home" wifi and checked my IP address to see if it was connected to my ISP. Attemped to send a MMS and GUESS WHAT!!!! IT WENT TROUGH!!!!! for a short period of time then it stoped again... I went back into the routers setup page and also turned off the STATIC IP I set for the phone, no luck. Then I remembered I have OpenDNS and my router was using the OPENDNS DNS addresses. went to my opendns dashboard and looked at what was blocked by them and found that that MMS proxy site "proxy.mobile.att.net" was "Blocked" by openDNS. So I put that domain in the "Never Block" list and rebooted the router. So far I am able to send and recieve MMS again when I am on my Home network... This still does not explain again why "hangouts" works with all of setting I have chenged before coming to this conclusion. Unless Google Hangouts is not using the APN and uses some other form of traffic to the net???? Also Google's Messenger app is also using DATA via whatever WIFI connection. Thus is my OPENDNS was blocking the proxy it was not going through!!!!
I AM FIXED for now!!!!! :good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:
So all of you who have problems with Google's Messenger APP sending and/or receiving MMS. Yes check to make sure your APN settings are correct. If your are on WIFI, disconnect WIFI attempt to send and receive a MMS. If it goes through when your WIFI Connection is off, but cannot if your connected to WIFI. Then go into your routers setup page and see if UPnP is "ON" or "OFF". When I turned my "UPnP to OFF" and make sure your phone is not assigned a static
IP.... If your using a OpenDNS filter/Blocker check to see if its not blocking the MMS Proxy!!! Lets hope this is it!!!!
Holy crap, thank you for this!! I've had this issue pop up over the last few days and couldn't for the life of me figure out what was wrong. It seems that un-blocking the proxy did the trick for me, too. I took it one step further, though, and whitelisted the whole att.net domain.
Oddly enough, I noticed that with the domain un-blocked, I could not resolve proxy.mobile.att.net on my desktop. So our phones must know to hand-off to the wireless network if that happens. But with the site "blocked," it WAS being resolved, which is probably what confused the heck out things.
Anyway .. thanks again. Yes, I hit the button.