 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Exchange Server / Mobility / July 2008Push mail not working for one phone
I am the exchange admin for my company. I have about 10 users all using windows mobile devices that are wireless syncing with our exchange server. All have been working just fine for over a year now. I recently bought myself a T-mobile Wing and setup push email on it, and it does not work. Here's the setup: All incoming traffic hits a server running Microsoft ISA Server 2000 sp2, it has the registry tweak to allow direct push, as well as the proper rules to allow traffic through. This goes to a server running Exchange 2003 SP2. The other users that have been using pushmail with no problems have the following carriers/devices: Sprint/Sprint Mogul Sprint/Motorola Q Sprint/Palm Treo 700wx AT&T/HTC 8125 So on my T-mobile Wing (With T-mobile as the carrier) I setup the exchange server settings in ActiveSync on the phone. When I manually hit the sync button, it syncs up no problem. Syncs all mail and contacts. But it will not stay connected. It's getting heartbeat failures with the error code 0x85010018. So mail is not being delivered to the phone as it arrives, instead it is basically hooking up every 8-10 minutes and forcing a sync, at which point I get email. When I turn on Verbose logging for ActiveSync, the log looks like this (note: Personal information has been removed from the log, these are not the actual server settings/usernames/etc): =-=- [24/06/2008 09:17:0212.000] -=-= =-=-=-= Client Request =-=-=-= POST Microsoft-Server-ActiveSync? User=PersonalStuff&DeviceType=PocketPC&Cmd=Ping MS-ASProtocolVersion: 2.5 Content-Type: application/vnd.ms-sync.wbxml User-Agent: MSFT-PPC/0.0.0 -=-=-=- Start of Body -=-=-=- <?xml version="1.0" encoding="utf-8"?><Ping xmlns="Ping:"><HeartbeatInterval>480</ HeartbeatInterval><Folders><Folder><Id>3f10a362c3b18845bfef6d14d8b10bb9-5569b</ Id><Class>Email</Class></Folder></Folders></Ping> =-=- [24/06/2008 09:17:0213.000] -=-= =-=-=-= Server Response =-=-=- HTTP/1.1 401 Access Denied Date: Tue, 24 Jun 2008 14:17:13 GMT Server: Microsoft-IIS/5.0 WWW-Authenticate: Basic realm="mail.mycompany.com" Proxy-Support: Session-Based-Authentication Content-Type: text/html Content-Length: 24 -=-=-=- Start of Body -=-=-=- <?xml version="1.0" encoding="utf-8"?><Ping xmlns="Ping:"><HeartbeatInterval>480</ HeartbeatInterval><Folders><Folder><Id>3f10a362c3b18845bfef6d14d8b10bb9-5569b</ Id><Class>Email</Class></Folder></Folders></Ping> =-=- [24/06/2008 09:17:0246.000] -=-= =-=-=-= Server Response =-=-=- HTTP/1.1 504 Gateway Timeout Content-Length: 1244 When I turn on verbose logging for the other phones, the logs look identical to this one, except it doesn't have the 504 Gateway Timeout entry and push mail works flawlessly for those phones. I originally thought it was an issue with the ISA server blocking something, but then I opened up the IIS logs on the exchange server, and I see the ping request entry being logged with a 200 OK response. So the ping is getting there. Another quirk is that I can setup a VPN connection on my Wing, and then set the exchange server entry in ActiveSync to the internal NETBIOS name. In this case, push mail works flawlessly. I've been wracking my brain for a week now trying to figure out what would cause something like this, and I'm at a total loss.... what is the difference between the Wing and all the other phones that are syncing normally? Have you tried recreating the direct push partnership? Worst case, a hard reset of the phone then reconnect with EAS.  SignatureJohn Oliver, Jr MCSE, MCT, CCNA Exchange MVP 2008 Microsoft Certified Partner >I am the exchange admin for my company. I have about 10 users all > using windows mobile devices that are wireless syncing with our [quoted text clipped - 81 lines] > the difference between the Wing and all the other phones that are > syncing normally? On Jul 1, 6:58 pm, "John Oliver, Jr. [MVP]" <jcolive...@hotmail.com> wrote: > Have you tried recreating the direct push partnership? Worst case, a hard > reset of the phone then reconnect with EAS. [quoted text clipped - 94 lines] > > the difference between the Wing and all the other phones that are > > syncing normally? Tried both of the above and same issue. It never worked from the moment I took the phone out of the box, so hard reset does nothing. So all your other phones in the org are ok and this is the only one that doesn't? Tried setting it up to run against your lab? Tried getting the mobile provider to swap the phone out? > So all your other phones in the org are ok and this is the only one > that doesn't? > Tried setting it up to run against your lab? > Tried getting the mobile provider to swap the phone out? Not sure what you mean when you say setting it up to run against my lab. I haven't tried swapping the phone out yet. I called T-mobile tech support and made it up to their tier3 techs and they're all stumped. They say if it will manually sync, then direct push should work, and that there is nothing wrong with the phone. None of the local stores have this phone, so if I want to swap it I have to ship it back to T- mobile. >> So all your other phones in the org are ok and this is the only one >> that doesn't? [quoted text clipped - 3 lines] >Not sure what you mean when you say setting it up to run against my >lab. You have a lab? Of course you have a lab. It's on some hardware inside VMware. It's all non-expiring 32bit development stuff that you construct when you need. Test the phone against that. >I haven't tried swapping the phone out yet. I called T-mobile tech >support and made it up to their tier3 techs and they're all stumped. >They say if it will manually sync, then direct push should work, and >that there is nothing wrong with the phone. None of the local stores >have this phone, so if I want to swap it I have to ship it back to T- >mobile. > >> So all your other phones in the org are ok and this is the only one > >> that doesn't? [quoted text clipped - 16 lines] > >have this phone, so if I want to swap it I have to ship it back to T- > >mobile. Unfortunately no, I don't have anything of the sort. >Unfortunately no, I don't have anything of the sort. Well, it's all a free download for evaluation. There's not one piece of software that you cannot get on evaluation without payment. Virtual PC, Virtual Server or VMware Server are all free. All you need is a decent PC that can run a DC, an FE and a BE. That's no more than 768MB of RAM really so a workstation with a Gig is fine. You should always have a lab set up or available because that's where you should go before you start asking questions in groups and other fora. > >Unfortunately no, I don't have anything of the sort. > [quoted text clipped - 7 lines] > you should go before you start asking questions in groups and other > fora. I guess I just don't understand what that is going to tell me that I don't already know? I don't have a FE/BE setup now... single exchange server. This is a very small company, 15 employees total... I don't have another machine that I could setup running VM Server anyway. >> >Unfortunately no, I don't have anything of the sort. >> [quoted text clipped - 12 lines] >server. This is a very small company, 15 employees total... I don't >have another machine that I could setup running VM Server anyway. It is going to tell you that if the lab kit you run up still doesn't allow the phone to work then the phone is without a doubt the thing that's wrong. I only mention this because you don't seem to have persuaded the telco to swap the phone out yet. If you had swapped the phone out and everything was ok you wouldn't be in these groups. If you did get the phone swapped and the new phone didn't work then you would have had the lab to check against. Never mind though, you just call that telco and get the phone swapped. One of the things that come to my attention is that this is the only phone you have with T-Mobile as an operator. Together the information that the phone is getting a heartbeat error, it makes very possible that T-Mobile requires a shorter heartbeat than you have configured at your server. If any of the other phones is SIM unlocked, you could try putting the T-Mo SIM card in it to see if it will fail as well. If it does, my case is proven. Then you need to change the registry of the server to allow shorter heartbeats. Helio Signature---- Helio Diamant MS-MVP/Mobile Devices Editor - PocketPCFreak.com >>> >Unfortunately no, I don't have anything of the sort. >>> [quoted text clipped - 24 lines] > > Never mind though, you just call that telco and get the phone swapped. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.