[vinmontRD]

It's 4:50pm, Eastern Time, as I type this... I've been using UMA with my 8900 since I got it about 18 months ago, and it's generally been excellent. I'm suddenly running into issues, and trying to pinpoint the cause.

I've been using 5.x OS's for months. Most recently, I had 610 installed for a while -- UMA worked fine with that. I upgraded to 822 a few days ago, and UMA still worked just fine -- maybe better than with 610.

This morning, the only change I made was to uninstall App World, and install the beta 2.x App World. The install went just fine, I rebooted the 8900. Sometime over the next 30 to 60 mins (I wasn't really paying attention), I noticed that UMA was not connected. I checked -- and the WiFi signal is still fine. I also tried rebooting my WiFi router (although that hasn't been necessary for several months now).

I also tried toggling my WiFi connection on the 8900 on and off several times. I tried a battery pull on the 8900.

With all the tests, I watched WiFi connect, and then UMA connect (first uma then UMA) as usual. About 30 seconds later, UMA dropped (it appears I have no connection to TMobile's network, although WiFi is live. Web browsing and data updates for apps like BerryWeather are lightning fast, as expected over WiFi. But I cannot connect to T-Mobile as I normally do via UMA.

Mobile Network Options, as always, are set to WiFi Preferred, and Network Selection, as always, is set to Automatic. I tried toggling Mobile Network off and on -- still no joy. Mobile Network (T-Mobile) will NOT connect.

Whereas I could get UMA to connect for about 30 seconds before dropping, perhaps half an hour ago, I now cannot get UMA to connect at all -- despite repeated battery pulls and router resets.

My settings are the same as always -- UMA has been superb for me for more than the past year. Only times I recall it going out were due to other UMA and/or FIOS outages -- 12/9/09, 10/2/09 and 8/5/08.

Anyone have ideas? Are others in the Central NJ area (I'm near Princeton -- West Windsor) having UMA issues? Is your router also connected via FIOS to the Internet?

Thanks in advance for any constructive ideas on this!

[K Bear]

Post as of 1728 in the Poconos, no UMA issues. I'm currently connected. Make sure you powercycle your router and do a battery pull. It may just be your connection rather than a T-Mobile issue.

[vinmontRD]

Post as of 1728 in the Poconos, no UMA issues. I'm currently connected. Make sure you powercycle your router and do a battery pull. It may just be your connection rather than a T-Mobile issue.

Thanks K Bear -- already power-cycled the router a couple of times (although I'm sure once was enough), and also tried resetting the 8900 via (alt+shift+del -- soft reset), and then did a couple of battery pulls. No luck.

UMA has been superb for me for the past 12 to 18 months -- works great at home (where my GPRS/EDGE signal is weak to non-existent), and has always been great a mobile hotspots like Panera, Best Buy, my public library, Dunkin Donuts, and many more. Truly have not had UMA issues at all -- except for the few brief UMA outages over the past year or so, and in the last 2.5 hours...

- Jon

[K Bear]

Do you have any signal if you turn off your WiFi connection?

[vinmontRD]

Do you have any signal if you turn off your WiFi connection?

In my basement office right now -- very weak ( -104 dBm ) signal. Every now and then the red X over the signal strength indicator is replaced briefly by a lower-case "gprs", or momentarily an uppercase GPRS. But that doesn't last long -- soon to be replaced by the red X.

This is normal in this location. UMA generally covers the situation beautifully.

[K Bear]

Do you have an internet feed?

[vinmontRD]

Hi again -- I had been posting / replying via my home office PC...so just to nicely verify that my 8900 has a good wifi data connection I fired up the native browser, came to crackberry mobile and logged in, found this thread and I'm now replying via my 8900. Still no uma --- but wifi is fine, I apparently have an ip address from the router's dhcp server, etc.

- Jon

Posted from my CrackBerry at wapforums.crackberry.com

[K Bear]

Try deleting the WiFi profile, do a soft reset of the 8900, then re-add the profile. If that doesn't help, then I'd call 611 and speak directly with Tech care and let them know the steps you've already taken. This should speed up the call.

[vinmontRD]

Good suggestions - thanks. BTW -- also just re-sent service books fro tmo's website...

Will try deleting / re-adding wifi profile. If no lcuk, will try 611 next.

Thx again... - Jon

Posted from my CrackBerry at wapforums.crackberry.com

[K Bear]

Anytime Jon. I try to do what I can to help my T-Mobile family out.

[vinmontRD]

Finally got everything resolved today and thought I'd share just in case anyone else runs into this. I was home from work today with a nasty cough / cold / headache -- couldn't deal with the office, but was OK for on and off work on the PC and a couple of routers...

After much experimenting to try to get UMA working again on my 8900, I noticed that the "T-Mobile@Home" phones in my house also had stopped working! Not happy about that -- but these landline replacements also talk to T-Mobile's network over UMA, so it became far more plausible to reject the assessment that the 8900 was at fault -- and far more likely that something was blocking UMA traffic.

I called 611 (T-Mobile Customer Care), and was quickly bumped to a somebody rather knowledgeable in @Home Support who also was very familiar with Blackberry's and UMA.

After I explained the whole setup, he had me check out a configuration page in the Actiontec -- the "General" page under Firewall Settings. With this, you can apparently do some broad-brush changes before having to delve deeply into specific firewall rules. The page allows a choice between 3 settings: "Maximum Security", "Typical Security" and "Minimum Security". Turns out that my Actiontec had been set to "Minimum" for the past year (working fine), and a recent firmware push by Verizon had, unbeknownst to me, changed this to "Typical" -- and wound up blocking ports 500 and 4500 needed for UMA to work.

Since I had done all the basic troubleshooting, we were able to skip over a lot -- but we quickly got to the point of doing a full reset on the Linksys WRTU54G-TM router provided by T-Mobile for @Home service (also the same one my 8900 connects to over WiFi) -- this router is downline from the Actiontec router provided by Verizon for FIOS service.

Once the full reset was done, and the change in settings on the Actiontec (above) were in place, UMA came back, and now both the 8900 and the @Home phones are all working properly again.

Thanks again for everyone's input!

- Jon