Hey all.

I bought a N770 last week due to Buy.com's closeout deal. I really like the thing so far. It's fantastic to whip it out while watching TV to look up something on Wikipedia or IMDB. I'm tempted to buy an N800 just to see if it's even better. I digress....

I'm having one small problem that I was hoping someone might be able to help me with. I ocasionally tether my 770 to my Cingular branded 8125 Windows Mobile 5 phone to get internet access when I'm away from WiFi. The 770 is so far superior at web browsing that it's not even funny. I had no problems pairing the devices, and only a couple of minor quirks with the DUN setup (changing number to *99#, same stuff as this info). It works, but I'm having a lot of problems establishing the connection and then keeping the connection alive.

The 770 usually takes 3 or 4 tries to actually connect to AT&T/Cingular, with a 'connection failed' message in between each attempt. I know the N770 is communicating with the 8125 because the 8125 has a connection status icon, and it changes to indicate that a data call is in progress on each attempt. When I do get a connection, it works brilliantly for about the first 500k-1mb worth of data transfer. Nice and speedy. And then it will just stop. I have to disconnect and reconnect to get it to work again. I am pretty sure it's something in how the N770 and 8125 are communicating. The N770 DUN works perfectly on my old Moto V330 with the same network & SIM card (instant connection, many MB of data with no hiccups), and the 8125 DUN works perfectly when using my laptop and bluetooth adapter. So in other words, it appears that there is nothing wrong with the my AT&T setup, the 8125's DUN connection, nor the N770's DUN abilities since it's perfect with the V330.

One common bit of advice I've seen elsewhere is to add the "at+cgdcont=1,"IP","WAP.CINGULAR"" info under the advanced AT settings. It didn't seem to matter but I have a feeling that something in here may make a difference.

Does anyone have any ideas on what the problem might be? It 'feels' like a configuration problem somewhere. Is there some sort of timeout setting or data-rate setting that may need to be tinkered with on the N770 to get it to more effectively communicate with the 8125?

I'm open to any advice, including dumping the 8125 for a Nokia N75.

Since I started it, I thought I ought to finish it....

I believe I have figured out the problem. I use an Exchange server to take advantage of the DirectPush mail on my 8125. It seems that DirectPush stuff was trying to initiate a connection while I had the N770 tethered. This was halting the data on the N770. I discovered that if I temporarily disable DirectPush on the 8125, that then the N770 1) almost always connects on the very first attempt, and 2) does not appear to drop the connection.

So, anyone trying to tether using a WindowsMobile device with DirectPush mail, you might want to go into the connections manager and disable DirectPush while you're trying to do a tethering session on the N770/N800.