Alright, I'll look into Certificate Server and try signing
a new certificate that way. I still don't
understand why I'd be able to access the page with SSL
using a browser running on the server and have it show up
on the logs, and not get anything on the test computers. It
seems like even if it was a certificate problem something
would still show up in the server logs, especially if its
just that the certificate isn't signed by a trusted CA. I
would think the server would be contacted, note it in the
log, start the handshake, and then have the client computer
fail to recognize the certificate. I guess it depends on
how the server logs work. Any explanation for a newbie?
>-----Original Message-----
>That's why something is wrong. you should get
>the prompt from all browsers. and maybe something
>wrong with the cert too.
>
>I'm not familair with openssl, but if you have a W2k Server,
>you might want to try this
>HOW TO: Configure SSL in a Windows 2000 IIS 5.0 Test
Environment by Using
>Certificate Server 2.0
>http://support.microsoft.com/?id=290625
>
>Using Certificate Server 2.0 to Generate a Server
Certificate for Use with
>IIS 5.0
>http://support.microsoft.com/?id=228984
>
>
>--
>Regards,
>Bernard Cheah
>http://support.microsoft.com/
>Please respond to newsgroups only ...