We have just noticed that if a users password is changed in AD that the
mobile phones continue to sync for at least 24 hours even though they have
the old password.  What could be causing this behavior.
Exchange 2003 sp2, ISA 2006, Win 2003 forest, mobile 6 devices.

I have an exchange server 2007 and am trying to sync some Windows based
phones. They are using Windows mobile 5 and 6. I can sync if I put the phone
in the cradle and sync with the exchange server locally but cannot sync ota.
I get the error 0x85010018.

Is it possible to use a host header in Exchange 2003 IIS settings?  I put
in a new mail server and needed to reissue my SSL certificate, but can only
issue it with the same common name as the old server.  So, I added a host
header to the new server's default website, etc.  I also ...

Hello?  Is there a IPHONE compatible version of Mobile Outlook?
Or, is there an email client for IPHONE that can connect
to Exchange 2000?

I received a new WM6 phone late last week (was using WM5 for quite a
while with no issues)... when I went to sync it with Exchange over the
air, I had forgotten about the whole need to put a cert on the device
via a CAB file. I talked to our Exchange admin on the phone and he

I would like to setup ActiveSync to use both, the client certficate and
login and password. But there is no configuration for the login and password
once the application determines it is required to use certificate.
How you achieve the goal?

I published RPC over HTTPS using ISA Server 2006 (Exchange 2007, Outlook
2007), everything works fine.
But when I'm connection to rpc/https from the internal network, I need to
login first.

Has anyone had any luck using host headers in their Exchange IIS settings
(Windows 2003 R2, Exch 2003 SP2) and having their mobile devices sync successfully?
I tried using a host header and implementing SSL, but cannot do so.  I wanted
to use my existing cert that I have, and ...

We just purchased some new Samsung Blackjack II's with WM6. Prior to that
we had some old WM3?4?, I don't know. But they worked fine.
At the beginning of March our certs on our Exchange2003 server expired, so
we updated it. It is purchased and an office Equifax(?) if I recall right

Well, this time it is me asking the question instead of answering it.....
After implementing this successfully in around 85 servers during the last 12
months, I finally came to a situation in which things are not working and I
can't find out why. Here is my situation: