Quote:
Originally Posted by phuangk
Certificate issue mainly happened on WM5 Smartphone device (correct me if i am wrong). I think there are 2 ways to load the certificate onto your phone.
1. Load certificate with the certificate loader (you can download certificate loader from Microsoft website) http://technet.microsoft.com/en-us/l.../aa997575.aspx
2. Load certificate manually by using cab method. http://blogs.msdn.com/windowsmobile/..._cab_file.aspx
However, your problem looks like you can load certificate, but you are loading the wrong certificate onto your phone. Maybe try to request a new certificate and load it again? Sorry I am not expert on this...  |
Thanks for the try guys! I figured it might be an easy registry fix like wm5. I tried updating the self-signed last night before posting, I even double check ed that it was a certified trusted root , right from the server, but still no good. I guess I gotta convince the company to buy certs, or just go back to 5.