Re: Problems with ActiveSync - Windows Mobile Devices - 0x80072F05



thank you for the reply. If I uncheck the box "server requires SSL", it
works fine. The unfortunate part about this though is our cert was just
renewed with Verisign and works fine with any browser around. I just
verified this by connecting directly to https://mydnshost.dom.com/oma and the
cert was correctly read by IE. It shows the correct dates in it and worked
fine. We use the same cert for several other apps and they work fine as
well. As well, if I can connect to the owa/oma url via the phones browser
without issue (which to me means 443 is working fine as well), we can
effectively rule out that our firewall is blocking 443. Please assist, we
had this issue about a year ago and gave up, but now our users want to use
windows mobile devices instead of blackberry's.

"John Oliver, Jr. [MVP]" wrote:

Can you successfully sync without using SSL for testing purposes? If you
can, then this would lead one to believe the SSL cert was not reissued
properly or port 443 is not open on your firewall.

--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2007
Microsoft Certified Partner

"Jared" <Jared@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:476AA47B-CDC1-4AF2-9CA7-BC18CC53FF8C@xxxxxxxxxxxxxxxx
Oh Yeah, and it's a Windows Mobile 5 smartphone.

"Jared" wrote:

All,

We have tried repeatedly to get ActiveSync working with new windows
mobile
devices and unfortunately, the devices always state the following error:

0x80072F05 - "the security certificate on the server has expired. Check
that
the date and time on your device are correct."

Now normally this would be self explanatory, but it's not. We have
checked
the time/date/timezone on both hte device and all of our exchange
servers.
they are all correct. We have actually just recently renewed our Cert
for 2
more years so we know it's correct and valid, as well as the fact that
all of
our OWA clients work fine and don't report cert errors.

Has anyone else had this issue and what was done to solve it. Note, this
is
an Exchange 2003 SP2 on Server 2003 SP1. Are there any additional ports
we
need open on the firewall (other than SSL and 80)? We have tried with
various devices and vendors, with no luck. Hopefully someone can help,
otherwise I'll just open a premier ticket soon.



.



Relevant Pages

  • =?ISO-8859-1?Q?Re:_SSL/TLS_Woes_FTP?=
    ... server needs to allow incoming connections to ports higher than 1024. ... you may need firewall adjustments. ... The z/OS FTP client is also very picky about server certificates. ... server cert must be signed by a CA acceptable to the client, ...
    (bit.listserv.ibm-main)
  • Re: 2 Certs for 1 OWA exchange server DR site
    ... Server for example, or another firewall. ... The users will connect to the DNS ... The issue is with the cert. ...
    (microsoft.public.exchange.admin)
  • Re: Loss of Webmail after renewing our Certificate
    ... Nothing to abnormal in the event logs. ... If you deselect the "require SSL" box, ... there a method to uninstall a cert and reinstall or anything like ... I'd take a look at the server and make sure that the cert was ...
    (microsoft.public.exchange.admin)
  • Re: http_403 error, but not for everyone
    ... As far as the SSL cert is concerned, as I stated I can login successfully ... > - if the server you connect to is not a frontend exchange server see this ... The server is setup SSL, ...
    (microsoft.public.pocketpc.phone_edition)
  • SSL Cert and EAS
    ... I have just purchased a godaddy SSL cert for my WM5.0 AKU2 device and I ... The security certifcate on the server is invalid. ... Administrator or ISP to install a valid certificate on the server. ...
    (microsoft.public.exchange.admin)