|
Posted by szurlo on December 21, 2006, 11:26 am
Please log in for more thread options
Hi all,
My company is in the process of migrating from Blackberries to Windows
Mobile 5.0 phones (Sprint PPC6700 / VZW XV6700) and we're having some
rather odd issues with direct push.
Basic overview of our infrastructure:
Stand-alone Exchange 2003 server w/SP2. This server is also our DC.
We are NOT using SSL (yet). No CA is even installed on the server.
HTTP timeout on the firewall has been increased to 30 minutes.
Everything else on the server is "installation defaults".
The problem we are having is that we often get delays in receiving
e-mails, in some cases an hour or more after the message appears on the
exchange server.
Additionally, sometimes a handset will receive e-mail almost instantly
for several days and then start receiving them in batches every 10
minutes or so. I can fix this for a while by doing one of two things:
Making any kind of change to the folder selection for syncing on the
handset, I.E add or remove any folder for synchronization. The other
"fix" is to hard reset the device. (Soft reset DOES NOT fix it). Either
method will restore almost instantaneous e-mail delivery for anywhere
from a few hours to several days. Just a note: forcing a sync or
forcing a send/receive from pocket outlook on the handset always
works, even when push appears to be broken.
I have enabled verbose logging on my handset and have looked at the
entries in the NON_IPM_SUBTREE on exchange and I can see current
AutdState.xml files, folder files, etc.
The problem is I can't seem to find a good source of information on the
web of what exactly I should/should not be seeing in these logs and
files.
I also can't find any source that explains where to look to see that
exchange is actually pushing change notifications down to the handset.
All the information I have found is about the communication from the
handset TO IIS and exchange, not back down.
At any rate, the only thing I have found that looks suspicious is a
huge number of 401 response codes in the IIS logs and in the handset
ActiveSync logs, but they are kind of odd. See below:
(Please note that in the examples below I have replaced the true user
and domain names with generic values.)
In the below example from our IIS logs you can see that the ping
command from the handset has the cs-username field set to "-". These
fail 100% of the time with 401 for every user. The logs on the device
show the same error.
POST /Microsoft-Server-ActiveSync
User=username&DeviceId=748A1E66F12610F623202AB3C88026D8&DeviceType=PocketPC&Cmd=Ping
80 - 68.30.35.63 MSFT-PPC/5.1.2000 401 2 2148074254
However, there is another version of the ping POST that appears
occasionally in the logs that also has a "Log=" value, and DOES supply
the cs-username value, and returns 200 every time.
POST /Microsoft-Server-ActiveSync
User=username&DeviceId=748A1E66F12610F623202AB3C88026D8&DeviceType=PocketPC&Cmd=Ping&Log=V4TNASNC:0A0C0D0FS:0A0C0D0SP:2C21I11377S110484R0S0L780H0P
80 ourdomain\username 68.30.35.63 MSFT-PPC/5.1.2000 200 0 0
SUBSCRIBES appear to always populate the cs-username field and always
appear to result in 200.
All of the other METHODS (PROPFIND, SEARCH, UNSUBSCRIBE, etc) I have
seen in the logs seem to behave in the following manner:
There will be an entry for the given method WITHOUT the cs-username,
which returns 401, followed IMMEDIALTY by another one that DOES include
the cs-username, which always results in a 200 series response. See
example below from our logs.
UNSUBSCRIBE /exchange/username@ourdomain.com/ - 80 - 10.1.1.202
Microsoft-Server-ActiveSync/6.5.7638.1 401 1 0
UNSUBSCRIBE /exchange/username@ourdomain.com/ - 80 OURDOMAIN\username
10.1.1.202 Microsoft-Server-ActiveSync/6.5.7638.1 207 0 0
The one exception to this rule appears to be the first example I showed
above, where &cmd=Ping only. These fail and are NOT followed by a
second attempt that contains a valid cs-username. If my understanding
of Direct Push is even remotely correct, then it would seem this would
be a pretty significant problem. Isn't this the command that provides
the exchange server with the connection information that exchange then
uses to push down change notifications?
Any insight anyone could provide me would be GREATLY appreciated. This
thing is kicking my butt ;)
Regards,
Steve Zurlo
|
| Similar Threads | Posted | | Direct Push | August 24, 2006, 9:49 am |
| Direct Push Stumper | December 14, 2006, 2:02 pm |
| EAS Direct Push Problems | January 19, 2007, 8:51 pm |
| Exchange Direct Push | May 2, 2007, 6:20 am |
| Direct Push on Treo 700w (WM5.0) | January 6, 2006, 7:17 pm |
| Synchronize Tasks with direct push | April 12, 2006, 9:43 am |
| No Direct Push icon on my phone | April 24, 2006, 11:27 am |
| Direct Push changes the dates of the emails | July 26, 2006, 5:49 am |
| show ALL Sent Items w/ WM5 & direct push/OMA | July 11, 2007, 7:08 pm |
| PPC + Activesync with Direct Push and laptop ? | August 14, 2007, 7:24 pm |
|
XML Sitemap