SSL No Longer Works when Existing Certificate is Installed

SSL No Longer Works when Existing Certificate is Installed

am 12.01.2008 02:07:24 von Christopher Koeber

I have a seemingly simple issue that I cannot figure out.

I am running a website using IIS 6 with an SQL Server 2000 backend on
Windows Server 2003 Standard Edition. Using the SelfSSL tool that is part
of the IIS 6 Resource Kit I am able to generate a self-signing ssl
certificate without issue. I am also able to use several older certificates
that either coorespond to older systems or to a previous instance of the
said server.

When I attempt to install a valid certificate issued by Thawte the SSL
portion of the website stops responding altogether. I keep
getting "Connection Interrupted" or similar messages from clients
connecting to the website. I have restarted the server everytime I
installed a certificate to attempt to see if there was an conflict with an
item resident in memory.

Is there anything that I have not looked at or need to do? Thank you in
advance.

--
Regards,

Christopher Kurtis Koeber

Re: SSL No Longer Works when Existing Certificate is Installed

am 12.01.2008 04:43:55 von Ken Schaefer

Did you check the httperr.log file on the server?

Additionally, check the Windows Event Logs for any errors that might be
there (especially from SChannel)

Cheers
Ken


"Christopher Koeber" wrote in message
news:fpUhj.62781$z92.59849@fe09.news.easynews.com...
>I have a seemingly simple issue that I cannot figure out.
>
> I am running a website using IIS 6 with an SQL Server 2000 backend on
> Windows Server 2003 Standard Edition. Using the SelfSSL tool that is part
> of the IIS 6 Resource Kit I am able to generate a self-signing ssl
> certificate without issue. I am also able to use several older
> certificates
> that either coorespond to older systems or to a previous instance of the
> said server.
>
> When I attempt to install a valid certificate issued by Thawte the SSL
> portion of the website stops responding altogether. I keep
> getting "Connection Interrupted" or similar messages from clients
> connecting to the website. I have restarted the server everytime I
> installed a certificate to attempt to see if there was an conflict with an
> item resident in memory.
>
> Is there anything that I have not looked at or need to do? Thank you in
> advance.
>
> --
> Regards,
>
> Christopher Kurtis Koeber

Re: SSL No Longer Works when Existing Certificate is Installed

am 12.01.2008 06:57:19 von David Wang

On Jan 11, 5:07=A0pm, Christopher Koeber wrote:
> I have a seemingly simple issue that I cannot figure out.
>
> I am running a website using IIS 6 with an SQL Server 2000 backend on
> Windows Server 2003 Standard Edition. Using the SelfSSL tool that is part
> of the IIS 6 Resource Kit I am able to generate a self-signing ssl
> certificate without issue. I am also able to use several older certificate=
s
> that either coorespond to older systems or to a previous instance of the
> said server.
>
> When I attempt to install a valid certificate issued by Thawte the SSL
> portion of the website stops responding altogether. I keep
> getting "Connection Interrupted" or similar messages from clients
> connecting to the website. I have restarted the server everytime I
> installed a certificate to attempt to see if there was an conflict with an=

> item resident in memory.
>
> Is there anything that I have not looked at or need to do? Thank you in
> advance.
>
> --
> Regards,
>
> Christopher Kurtis Koeber


Run SSL Diagnostics.

http://www.microsoft.com/downloads/details.aspx?familyid=3D9 bfa49bc-376b-4a5=
4-95aa-73c9156706e7&displaylang=3Den


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: SSL No Longer Works when Existing Certificate is Installed

am 12.01.2008 15:08:33 von Christopher Koeber

Awesome tool! I pinpointed the issue. The problem was that the certificate
didn't have a provate key as part of the certifcate.

For future reference for anyone to solve that problem visit

http://blogs.iis.net/lprete/archive/2007/11/25/assign-a-priv ate-key-to-a-new-certificate-after-you-use-the-certificates- snap-in-to-delete-the-original-certificate-in-internet-infor mation-services.aspx

Thanks for the assist.

--
Regards,

Christopher Kurtis Koeber

David Wang wrote:

> On Jan 11, 5:07 pm, Christopher Koeber wrote:
>> I have a seemingly simple issue that I cannot figure out.
>>
>> I am running a website using IIS 6 with an SQL Server 2000 backend on
>> Windows Server 2003 Standard Edition. Using the SelfSSL tool that is part
>> of the IIS 6 Resource Kit I am able to generate a self-signing ssl
>> certificate without issue. I am also able to use several older
>> certificates that either coorespond to older systems or to a previous
>> instance of the said server.
>>
>> When I attempt to install a valid certificate issued by Thawte the SSL
>> portion of the website stops responding altogether. I keep
>> getting "Connection Interrupted" or similar messages from clients
>> connecting to the website. I have restarted the server everytime I
>> installed a certificate to attempt to see if there was an conflict with
>> an item resident in memory.
>>
>> Is there anything that I have not looked at or need to do? Thank you in
>> advance.
>>
>> --
>> Regards,
>>
>> Christopher Kurtis Koeber
>
>
> Run SSL Diagnostics.
>
>
http://www.microsoft.com/downloads/details.aspx?familyid=9bf a49bc-376b-4a54-95aa-73c9156706e7&displaylang=en
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //

Re: SSL No Longer Works when Existing Certificate is Installed

am 12.01.2008 15:08:33 von Christopher Koeber

Awesome tool! I pinpointed the issue. The problem was that the certificate
didn't have a provate key as part of the certifcate.

For future reference for anyone to solve that problem visit

http://blogs.iis.net/lprete/archive/2007/11/25/assign-a-priv ate-key-to-a-new-certificate-after-you-use-the-certificates- snap-in-to-delete-the-original-certificate-in-internet-infor mation-services.aspx

Thanks for the assist.

--
Regards,

Christopher Kurtis Koeber

David Wang wrote:

> On Jan 11, 5:07 pm, Christopher Koeber wrote:
>> I have a seemingly simple issue that I cannot figure out.
>>
>> I am running a website using IIS 6 with an SQL Server 2000 backend on
>> Windows Server 2003 Standard Edition. Using the SelfSSL tool that is part
>> of the IIS 6 Resource Kit I am able to generate a self-signing ssl
>> certificate without issue. I am also able to use several older
>> certificates that either coorespond to older systems or to a previous
>> instance of the said server.
>>
>> When I attempt to install a valid certificate issued by Thawte the SSL
>> portion of the website stops responding altogether. I keep
>> getting "Connection Interrupted" or similar messages from clients
>> connecting to the website. I have restarted the server everytime I
>> installed a certificate to attempt to see if there was an conflict with
>> an item resident in memory.
>>
>> Is there anything that I have not looked at or need to do? Thank you in
>> advance.
>>
>> --
>> Regards,
>>
>> Christopher Kurtis Koeber
>
>
> Run SSL Diagnostics.
>
>
http://www.microsoft.com/downloads/details.aspx?familyid=9bf a49bc-376b-4a54-95aa-73c9156706e7&displaylang=en
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //

Re: SSL No Longer Works when Existing Certificate is Installed

am 12.01.2008 15:10:47 von Christopher Koeber

Thanks. The problem was that the certificate I installed didn't have a
private key. Solved using SSL Diagnostics and the certificate repair tools
within Windows.
--
Regards,

Christopher Kurtis Koeber

Ken Schaefer wrote:

> Did you check the httperr.log file on the server?
>
> Additionally, check the Windows Event Logs for any errors that might be
> there (especially from SChannel)
>
> Cheers
> Ken
>
>
> "Christopher Koeber" wrote in message
> news:fpUhj.62781$z92.59849@fe09.news.easynews.com...
>>I have a seemingly simple issue that I cannot figure out.
>>
>> I am running a website using IIS 6 with an SQL Server 2000 backend on
>> Windows Server 2003 Standard Edition. Using the SelfSSL tool that is part
>> of the IIS 6 Resource Kit I am able to generate a self-signing ssl
>> certificate without issue. I am also able to use several older
>> certificates
>> that either coorespond to older systems or to a previous instance of the
>> said server.
>>
>> When I attempt to install a valid certificate issued by Thawte the SSL
>> portion of the website stops responding altogether. I keep
>> getting "Connection Interrupted" or similar messages from clients
>> connecting to the website. I have restarted the server everytime I
>> installed a certificate to attempt to see if there was an conflict with
>> an item resident in memory.
>>
>> Is there anything that I have not looked at or need to do? Thank you in
>> advance.
>>
>> --
>> Regards,
>>
>> Christopher Kurtis Koeber

Re: SSL No Longer Works when Existing Certificate is Installed

am 12.01.2008 15:10:47 von Christopher Koeber

Thanks. The problem was that the certificate I installed didn't have a
private key. Solved using SSL Diagnostics and the certificate repair tools
within Windows.
--
Regards,

Christopher Kurtis Koeber

Ken Schaefer wrote:

> Did you check the httperr.log file on the server?
>
> Additionally, check the Windows Event Logs for any errors that might be
> there (especially from SChannel)
>
> Cheers
> Ken
>
>
> "Christopher Koeber" wrote in message
> news:fpUhj.62781$z92.59849@fe09.news.easynews.com...
>>I have a seemingly simple issue that I cannot figure out.
>>
>> I am running a website using IIS 6 with an SQL Server 2000 backend on
>> Windows Server 2003 Standard Edition. Using the SelfSSL tool that is part
>> of the IIS 6 Resource Kit I am able to generate a self-signing ssl
>> certificate without issue. I am also able to use several older
>> certificates
>> that either coorespond to older systems or to a previous instance of the
>> said server.
>>
>> When I attempt to install a valid certificate issued by Thawte the SSL
>> portion of the website stops responding altogether. I keep
>> getting "Connection Interrupted" or similar messages from clients
>> connecting to the website. I have restarted the server everytime I
>> installed a certificate to attempt to see if there was an conflict with
>> an item resident in memory.
>>
>> Is there anything that I have not looked at or need to do? Thank you in
>> advance.
>>
>> --
>> Regards,
>>
>> Christopher Kurtis Koeber

Re: SSL No Longer Works when Existing Certificate is Installed

am 13.01.2008 07:10:16 von Ken Schaefer

In the case that you don't have the private key, an error is logged by
Schannel in the Windows Event logs.

You should review those logs for issues/errors :-)

Cheers
Ken


"Christopher Koeber" wrote in message
news:HT3ij.316901$ZO3.241162@fe02.news.easynews.com...
> Thanks. The problem was that the certificate I installed didn't have a
> private key. Solved using SSL Diagnostics and the certificate repair tools
> within Windows.
> --
> Regards,
>
> Christopher Kurtis Koeber
>
> Ken Schaefer wrote:
>
>> Did you check the httperr.log file on the server?
>>
>> Additionally, check the Windows Event Logs for any errors that might be
>> there (especially from SChannel)
>>
>> Cheers
>> Ken
>>
>>
>> "Christopher Koeber" wrote in message
>> news:fpUhj.62781$z92.59849@fe09.news.easynews.com...
>>>I have a seemingly simple issue that I cannot figure out.
>>>
>>> I am running a website using IIS 6 with an SQL Server 2000 backend on
>>> Windows Server 2003 Standard Edition. Using the SelfSSL tool that is
>>> part
>>> of the IIS 6 Resource Kit I am able to generate a self-signing ssl
>>> certificate without issue. I am also able to use several older
>>> certificates
>>> that either coorespond to older systems or to a previous instance of the
>>> said server.
>>>
>>> When I attempt to install a valid certificate issued by Thawte the SSL
>>> portion of the website stops responding altogether. I keep
>>> getting "Connection Interrupted" or similar messages from clients
>>> connecting to the website. I have restarted the server everytime I
>>> installed a certificate to attempt to see if there was an conflict with
>>> an item resident in memory.
>>>
>>> Is there anything that I have not looked at or need to do? Thank you in
>>> advance.
>>>
>>> --
>>> Regards,
>>>
>>> Christopher Kurtis Koeber
>