Well we’ve seen a fair amount of reminiscing in the blogs to date. It’s interesting even to me to hear from the Exchange veterans about the high-flying times back in the 4.0 and 5.5 days. I’m a ...
Updated Jul 01, 2019
Version 2.0
Blog Post
Hi Simon,
A number of different things may be happening, and it is hard to pinpoint anything with just this one bit of diagnostics information. Here are a couple of pointers to check out:
- SSL negotiation failure may indeed be a problem, but it is likely not due to your phone cert list. Unless your carrier has deployed a WAP2 end-to-end SSL capable gateway, your phone is probably communicating to gateway machine on carrier network using WTLS,
and that gateway computer initiates an SSL session with Exchange server on phone's behalf. If the gateway does not trust the SSL certificate installed on your Exchange server, the SSL handshake will fail and you may see an error 500. This is likely to occur
if the Exchange server has a self-issued certificate - most carrier gateways will trust SSL certs issued by large companies in that business, such as Thawte, Verisign, Baltimore, etc. Since the IE client uses a direct IP connection to Exchange and does not
have a carrier network/gateway to deal with, this might explain it working properly. If this is indeed the problem, purchasing an SSL certificate from a well-known issuer is probably the easiest workaround.
- Another thing to check is whether your Exchange server has URLScan enabled. We publish a guide (http://support.microsoft.com/default.aspx?scid=kb;en-us;823175) to configuring
URLScan to work with all Exchange web applications including OMA. If you do have URLScan enabled and configured as per above, you may need to also add the HEAD verb to [AllowVerbs] section for OMA. This is due to a device issue on certain firmware revisions
of SonyEricsson phones. We are in process of updating the KB to reflect this change.
Good luck!
Alex