pasaga,
If I'm understanding what you did, you should be able to use the IIS
Server Certificate wizard to delete the current server certificate, then
use the wizard again to create a certificate request. You'll then need
to submit the resulting certificate request contents (a .TXT file) to
whoever you are using as your CA.
They'll return a server cert back to you, and then you use the IIS
Server Certificate wizard again to "process" this (i.e., install the
cert).
[quoted text, click to view] pasaga wrote:
>
> hi there! i have the SAME problem. would you be so kind to let me know
> what you actually to fix ssl problem? thanks so much! psg
>
> "BG" <bg3@uasystem.ua.edu> wrote in message news:<1e3d01c38473$0b70e780$a001280a@phx.gbl>...
> > I think I have determined the source of my problem. When
> > I originally started the Server Certificate Wizard, I
> > selected Assign an existing Certificate. I used the
> > certificate generated by the server during the CA service
> > startup. I should have created a new one.
> >
> > >-----Original Message-----
> > >I recently installed SSL using the MS CA Services. When
> > I
> > >connect from a client, it tells me I need to use https.
> > >So, I do, and I get parge not found. The IIS log shows
> > >error 403. I have the diagnostic tool and when I run the
> > >simulated handshake, i get
> > >System time: Fri, 26 Sep 2003 18:35:24 GMT
> > >Connecting to (server_ip_address):443
> > >Connected
> > >Handshake: 108 bytes sent
> > >Handshake: 829 bytes received
> > >Handshake: 118 bytes sent
> > >#WARNING:Handshake: unspecified error receiving data
> > >#WARNING:Handshake: 0x80090304 (-2146893052) error
> > >
> > >The main SSL Diag window has only two entries that might
> > >help:
> > >
> > >#Could not impersonate server account
> > >
> > >SSLStoreName = MY
> > >
> > >I am doing all of this from the server.
> > >
> > >
> > >
> > >.