Re: Activesync support codes 85020010 and 80070002



I assume you mean on the phone, and yes it is installed. There is only a
single server involved (no front end/back end).

Dennis Jennings

"Chris De Herrera" <spam@xxxxxxxxxxxxxxxx> wrote in message
news:OJ7diRvdGHA.4720@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
Since the host name is the same it uses the same digital certificate. Did
you try installing it? Finally are you using multiple servers?


--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com

ActiveSync 4.x Troubleshooting Guide -
http://www.pocketpcfaq.com/faqs/activesync/tshoot-as4x.htm

"Administrator" <administrator@xxxxxxxxxxxxxxx> wrote in message
news:99f1664f0bd18c843f051d39fed@xxxxxxxxxxxxxxxxxxxxxxx
Hello Chris,

The hostnames are the same: mail.userdomain.com and the digital
certificate matches that name. OMA is accessed by
https://mail.userdomain.com/oma and OWA with
https://mail.userdomain.com/exchange.

As I said earlier I find it strange that OMA says the device doesn't
trust the certificate and OWA does, because it connects directly.

Dennis

Hi,
Are the host names the same for OMA and OWA? Is the digital
certificate a
wildcard cert? Windows Mobile does not support wildcard certificates.
ActiveSync 4.x Troubleshooting Guide -
http://www.pocketpcfaq.com/faqs/activesync/tshoot-as4x.htm

"Dennis Jennings" <dennis@xxxxxxxx> wrote in message
news:eaVX3iVdGHA.2068@xxxxxxxxxxxxxxxxxxxxxxx

I am trying to set up Activesync between a Cingular 8125 and an
Exchange 2003 SP2 server. The sync will work fine between the 8125
and Outlook on the PC, but when I enable syncing with Exchange I get
the 85020010 when I am connected with USB and 80070002 when I try to
sync over the Cingular network.

I have installed the Certificate for the server--it is one from
GoDaddy which Microsoft says will work with WM5.0. If I browse to
OWA, the phone connects directly. If I browse to OMA, I get the
message that the certificate is not trusted even though it is already
installed in the root certificates. If I say continue anyway, I get
access to OMA.

Exchange Activesync does work with a PPC 2003, so the Exchange folks
say that the problem isn't at the Exchange end and sent me here for
help.

Anyone have some ideas? I have tried any of the ones I could find
that seem related. I even went to another PC and set up a new Outlook
profile and a fresh install of Activesync 4.1 and got the same
errors.

Dennis Jennings







.



Relevant Pages

  • Re: Mobile Sync 0x85010004 error on mobile5 device
    ... Browsing to OMA from my desktop again asks for authentication ... and clicking on it will install the certificate. ... Microsoft MVPs ... Are you running SBS/Exchange 2003 with Exchange Service Pack 2? ...
    (microsoft.public.windows.server.sbs)
  • Re: Activesync support codes 85020010 and 80070002
    ... Since the host name is the same it uses the same digital certificate. ... you try installing it? ... As I said earlier I find it strange that OMA says the device doesn't trust ... Exchange 2003 SP2 server. ...
    (microsoft.public.pocketpc.activesync)
  • Re: RPC over HTTP setup
    ... information about telling installing the certificate from my Exchange server ... However, even after installing ... "Integrated Windows Authentication" IS checked ...
    (microsoft.public.exchange.connectivity)
  • Re: Activesync support codes 85020010 and 80070002
    ... I spoke to the exchange admin they pointed me to the ssl certificate that is ... I was also thinking of installing the WM5 similator on my PC in order to be ... As I said earlier I find it strange that OMA says the device doesn't ... Exchange 2003 SP2 server. ...
    (microsoft.public.pocketpc.activesync)
  • ActiveSync Permissions Error
    ... I'm trying to set up ActiveSync for Exchange 2003 (same as OMA?). ... get further than I did without the certificate, ... I have Exchange Admin and Domain Admin permissions, ... On the server, I get no errors in the event logs. ...
    (microsoft.public.exchange.connectivity)