We have an existing certificate (global sign) that works fine when a Windows Mobile application (.NET 3.5) tried to use a web service (also written in .NET 3.5) hosted in IIS.
However, when we make the re-issued certificate (global mark) live, the Windows Mobile application cannot connect to the web service, the error we get is "Could not establish trust with the remote server . " Ive tried to search this on Google many times and did not find a suitable fix.
We also tried to copy (and install) the ROOT and intermediate certificate in the chain to the device, but this still does not work.
When we test a new certificate with a PC web browser (IE, Firefox, Opera), a desktop application that uses a web service (.NET 3.5) and even Internet Explorer on a Windows Mobile device, the .NET web service description / documentation pages are displayed without problems (no warnings or errors), it seems that the problem is only on the Windows mobile device when using the Compact Framework application (3.5) trying to use the web service.
We confirmed that the certificate was installed correctly on the SSL buyer’s website, and after our Google searches, we encountered and implemented (as a test) the "trust everyone" ICertificatePolicy handler, this solved the problem, but I was hoping that this problem could be solved by changing the configuration / setting rather than changing code and redeploying more than 150 Windows-based mobile devices.
The ICertificatePolicy crawler found an error that returned when checking the certificate: the problem parameter was set to: -2146762481 (0x800B010F in HEX), which, I believe, is a "CN No MATCH" error, but Ive looked for it both in its numerical form and in the form of a name and have not yet found a resolution other than changing the code "Trust everyone."