I have set up a test environment for publishing Exchange 2003 ActiveSync with ISA 2006.
It does not seem to work if the internal name of the Exchange Server is different from the external one. The ISA Server uses a certficate with the external name (equal to the Public Name, e.g. eas.domain.tld), and the Exchange Server uses a cert. with the internal name (e.g. exch.domain.tld).
This setup works for OWA and RPC/HTTPS, but not for Active Sync so far; the Windows Mobile 5.0 emulator gives error 85010014 and in the ISA logging I see Internal server error 500, which usually points to a wrong certificate common name.
"Forward the original hostheader..." is not checked and I can see the request going to exch.domain.tld in the Isa server 2006 log.
Have I missed a step?!
If you need more info, don t hesitate to ask :)
< Message edited by Christoph37 -- 21.Apr.2008 8:59:51 AM >
If I open IE and browse to https://eas.domain.tld, I get an authentication form. After I enter my credentials I get a page with error 101/105, which states that authentication does work, but WM 5.0 keeps getting error 85010014.
The ISA server was not the culprit. And it can handle different external and internal names for ActiveSync quite well.
The problem was that I only had one Exchange Server and Active Sync doesn´t work if SSL is enabled on the /Exchange virtual directory. The problem does not occur if you have an Exchange FE/BE configuration.