|
Posted by ahl on November 27, 2005, 3:17 am
Please log in for more thread options
1. Confirm that basic and integrated authentication is enabled on the
virtual directory that OMA is using. Exchange 2003 SP2 is reported to be
switching integrated authentication off for some unknown reason.
Read this for assistance;
http://support.microsoft.com/default.aspx?scid=kb;en-us;817379
2. Check that you have the correct SSL certificate installed on your WM5
device. Check the certificate's name and issue / expiry dates to confirm.
You may need to install the CA's certificate as well if using self generated
certificates.
3. Does the "server" entry on the client match the SSL certificate name?
4.. Are the proxy settings on the device interfering?
5. Is SSL (port443) is open at your perimeter firewall if using an external
FQDN?
6. If you are using external FQDN, can you loop back through your perimeter
firewall? Some can, some can't.
7. URLscan on the default website can interfere with dot com e-mail
addresses.
> All,
>
> I am getting similar issues and have taken the following (drastic)
> steps to resolve, but to no avail. These steps are an amalgamation of
> all the suggestions that I have been able to glean from artiles in
> various places on the web.
>
> - Ensured that Kerboros and NTLN are active on the IIS service
> (following a suggestion from an event in the application event log)
> - uninstalled office 2003
> - uninstalled activesync (currrent version 4.1)
> - reflashed the ROM on my device
> - rebooted the PC
> - re-installed office 2003
> - reinstalled activesync 4.1
> - created a partnership
> - synchronised successfully with the desktop (this has always been the
> case)
>
> The sync with the server then failed with an 85010014 error. The
> INTERESTING bit with this scenario is that synchronisation was working
> perfectly with the exchange server when SSL was not being used. Now,
> even if I turn SSL off again, I get an 8XXXXXXX error.
>
> There is some setting on the server somewhere (and I am convinced it is
> server side) that is creating this issue and we need to track it down
>
| 
XML Sitemap