We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now

x

0x80072f06 error code - wm5 - activesync

fshguo
fshguo asked
on
Medium Priority
3,332 Views
Last Modified: 2008-02-20
Hi...I have a PDA device with WM5 tried to activesync with Exchange 2003 SP2, the self cerfiticate's common name is: the exchange's computer netbios name, ie. ex2003. I got the error message during the sync. 0x80072f06.

I might be able to get rid of this error message by purchasing a certicate with common name, ie. ex2003.mydomain.com, however, it would invlove of of client changes. Is there a way to disable the certificate check like in WM2003? or change the registry in the device to bypass this message?

Alternaltively if the ex2003 is used as the activesync's server address, the error message is: 0x85002003 the server could not be reached. this can be caused by temporary network conditions. but I am able to ping the ex2003 from the device. how to get around issue without replacing the cerficate?

thanks,
fshguo.
Comment
Watch Question

Expert of the Year 2007
Expert of the Year 2006
Commented:
You really should do the certificate change. If you purchase a certificate it shouldn't require any changes on the clients because there is nothing to install. If the purchased certificate is from a supplier who is trusted (RapidSSL and GoDaddy's certificates are trusted by IE6, GoDaddy's by Windows Mobile as well) then you will be fine, as the certificate will be checked against the trusted list first.

There are various hacks for trying to disable the certificate checking, but some of these have been disabled by the mobile phone operators.

Try this blog posting from a fellow Exchange MVP: http://winzenz.blogspot.com/2006/03/hacking-your-windows-mobile-50.html

However you may also want to read his followup: http://winzenz.blogspot.com/2006/08/more-on-windows-mobile-certificate.html

Simon.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Commented:
Alternate solution - turns out our IT group had used a wildcard for certification management (e.g., *.company.com) and WM5 was not able to handle the change. They added in the specific SMTP server address (e.g., smtp.company.com) and this sorted the problem.
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.