Article ID: 324839 - Last Review: July 7, 2008 - Revision: 4.1 Cannot Open SSL-Enabled Web SiteThis article was previously published under Q324839 We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 7.0 running on Microsoft Windows Server 2008. IIS 7.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site: http://www.microsoft.com/technet/security/prodtech/IIS.mspx
(http://www.microsoft.com/technet/security/prodtech/IIS.mspx)
For more information about IIS 7.0, visit the following Microsoft Web site: http://www.iis.net/default.aspx?tabid=1
(http://www.iis.net/default.aspx?tabid=1)
IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986
(http://support.microsoft.com/kb/256986/EN-US/
)
Description of the Microsoft Windows Registry
SYMPTOMS
When you try to open a Web site that has Secure Sockets Layer (SSL) enabled in Internet Information Server (IIS) 4.0 or Internet Information Services (IIS) 5.0 with https, the browser stops responding (hangs) after the SSL handshake. The system log shows the following event:
Event Source: W3svc Event ID: 23 Event Type: information Description: For compatibility with previous versions of IIS, the filter '<drive>\winroot\System32\Inetsrv\Sspifilt.dll' was loaded as a global filter from the registry. To control the filter with the Internet Service Manager, remove the filter from the registry and add it as a global filter with Internet Service Manager. Filters in the registry are stored at "HKLM\System\CurrentControlSet\Services\W3Svc\Parameters\Filter DLLs". CAUSE
To enable SSL for Web sites in IIS 4.0 and IIS 5.0, the Web sites must have the Sspifilt.dll global filter loaded from the Internet Service Manager instead of from the registry.
RESOLUTIONWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk.
REFERENCESFor additional information about this problem when you are using IIS 4.0, click the article number below
to view the article in the Microsoft Knowledge Base:
289582
(http://support.microsoft.com/kb/289582/EN-US/
)
HTTPS Connections Fail After You Upgrade to Windows NT 4.0 Option Pack (IIS 4.0) and Enable SSL
| Article Translations
|

Back to the top
