certificate received from the remote server was issued

[chicagotech]

you try to setup Secure Wireless, but encounter "The certificate received from the remote server was issued by an un-trusted CA" failure.

From this message, it appears the ROOT CA certificate of CA which issue
certificate to IAS is not trusted by this client machine.

Analysis:
1. When establishing SSL connection, the IAS server will send Server hello
message to client which contain IAS server certificate.

2. Then the client will verify if the certificate is trusted by validating
if the ROOT certificate is in "Trusted Root Certificate Authority" store.

3. From the error message, it appears this ROOT Certificate which is the
root of ISA certificate chain is not in "Trusted Root Certificate
Authority" store of the client computer.

To resolve this kind of error, please follow the steps.

Suggestions:
1. Save the root certificate to a file.
a) On IAS server, please open this ISA server certificate, then click
"Certificate Path" Tab;
b) In "Certificate Path" Tab, please click Root Node;
c) Then please click "View Certificate" button;
d) In the new certificate window, please click "Details" button;
e) Please click "Copy to file¡­".
f) Follow the wizard and save the certificate to a file with extension .cer.

2) Install this root certificate to "Trusted Root Certificate Authority" of
client.
a) Copy the file saved in ISA server to client machine;
b). Run "MMC", click "Add/Remove Snap in" from file menu, please choose
"Certificate" .. "Computer Account"¡­ " Local Computer¡­" then finish.
c). Expand Certificate(local computer), right click "Trusted Root
Certificate Authority" .. "All Tasks" ¡­"Import".
d) Follow the wizard to import this save root certificate file.

[guest]

I ended up fixing my problem. As I noted in my question, iPhones were working correctly with wifi, however my Windows Clients weren't with regards to certificate based authentication. This pinpoints an issue with my windows clients and they way I was setting up the connection for the wireless profile. The fix was to uncheck "Validate server certificate" in the "Smart Card or other Certificate Properties page".