Very odd my Tilt can be.  When initiating web browesing it only peridocially connects to the internet.  My only option is to turn the phone off/on and relaunch IE to display the web page.  Anyone else getting this?  Can you help?

Bruce - Welcome to the Connection forum.

I also have an AT&T TILT,which I love.

I find this can sometimes happen if WiFi is turned on, and the wireless connection is not very strong. I keep wireless permanently off, and just use the phone connection for internet access.

Hey Laura!  I too keep WiFi turned off, but this does not seem to do the trick.  Again, this happens intermittently and can only be resolved by turning the phone off/on.  Frustrating.  Otherwise I do like the device overall.

Bruce, I use a Tytnn II on AT&T and observe what I thnk you describe. I start IE and try to open a page and nothing loads. I also notice at the same time that ActiveSync is no longer connected to the Exchange server. Basically, even though the device is showing that it is still connected to the data network, it really isn't even though you are connected just fine to the voice network.

I haven't spent too much time troubleshooting this because I just go into the Communications Manager, shut off the phone (aka, Plane Mode) and then turn the phone back on and all is well. I suspect what happens is that the wireless radio loses connection, isn't successfully able to reconnect and just drops. Or it may be that something like the IP address of the device expires.

Welcome Frank - I think you are correct here - I think it just loses the data connection and turning the phone off then on does the trick. I like your option of shutting it off via Flight Mode - this would be a quicker way of doing things.

I get this all the time on my Blackjack II as well. Except I get a "403 Not Allowed" error.

I have to reboot the phone for the 403 error, but for the problem with the pages just not loading, I can simply toggle my proxy setting and it starts working again.

-Andrea

Agreed that the solution is not cumbersome, just the experience is frustrating.  Thanks for the thoughts!

This can be done without neeing to fully reset the phone. Tap on the "3G" or "H" icon at the top of the screen and select "Disconnect". The phone will immediately reconnect and data should be working.  After the latest ROM update for the Tilt I haven't had this problem anymore.

Thanks for the input and I will be sure to try that next time it happens.  Also, I forgot about that ROM update, so thanks for that reminder too.

I have heard also from customers about this same issue. I'm trying to find specifically if this has been fixed in the 6.1 update. If I find out anything for sure I will post it here.

I see this quite a bit with AT&T, and it's not limited to one type of device.

This is prolly more connected to the radio firmware of the device, and its ability to successfully traverse different towers. I'm sure the AT&T tower hardware has a good bit to do with this as well.

As a general rule, I show all my clients how to disable/enable the radio on their device and tell them they should get in the habit of doing that periodically when travelling, especially if they go outside a 50/60 mile range.

Great news, folks. We've received some great technical information from the Windows Mobile team about what's causing this issue, and even better, how to fix it!

According to our mobile technology and engineering contacts at Microsoft, the solution is:

"The issue is with the proxies that AT&T uses... In IE, under Menu > Tools > Options > Connections, set the network to INTERNET, un-checking 'Automatically detect..' and this will bypass the proxy. This works 100% of the time unless there is something else going on with radio but that would be unrelated to this issue.

 

Brief issue summary: The WAP Proxy (MAC) is designed to ensure that devices have active data connections for less than 24 hours. If the device exceeds this time, the gateway rejects the outbound request with a 403 – Access Forbidden. This is for legacy devices that did not normally maintain always-on connections such as smart devices. So, with our always-on presence we exceed this timer restriction and are denied outbound access.

 

Changing the pathing to INTERNET instead of WAP works around this."

Cool! Hope that helps everyone who is experiencing this issue.

Bill's workaround works for any WinMob device on the AT&T network.  In fact, new phones should already be set for this from the store.

 I must have some abnormal version if IE as there is no option for Connections under the IE Menu. Alas, I am still experiencing inconsistent connectivity issues...

Bruce Margetich:

I must have some abnormal version if IE as there is no option for Connections under the IE Menu.

You are not abnormal Bruce...I do not see it there either.....