"Cannot find server" or "DNS" Errors When Using SSL (Q & A)

Dichiarazione di non responsabilità per contenuto KB ritirato

Il contenuto di questo articolo è riferito a prodotti per cui Microsoft non offre più il supporto. Questo articolo viene pertanto offerto "così com'è" e non sarà più aggiornato.


The "Cannot find server" or "DNS error" browser error messages are symptoms of several different problems. This article lists some of the more common reasons this error may occur when the Web site is using Secure Sockets Layer (SSL) and is therefore accessed by using https://.

More Information

  • Was the Web server certificate part of an export or import process? There is a known problem during the import process in which the wrong cryptographic service provider (CSP) is chosen. You may also see an Schannel Event ID: 36871 message. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

    261655 Cannot Make an SSL Connection After Exporting and Importing an Server Certificate
  • Is the Web Server running Windows 2000, and has the Web server certificate recently renewed? The usual renewal process involves sending a renewal request to the Web server certificate issuer (that is, a Certificate Authority such as VeriSign, Netscape, or Microsoft.) A fix has been developed that ensures that a standard PKCS10-formatted renewal request is created. For more information, see the following Knowledge Base article:
    262979 Cannot Renew Verisign Certificates in IIS 5.0
  • Is the Sspifilt.dll file loaded on the IIS master properties ISAPI Filter tab? If not, add the Sspifilt.dll name and the \Winnt\System32\Inetsrv\Sspifilt.dll execution path to the IIS master properties ISAPI Filter tab.

  • Were any changes made to the IIS computer or Web site while a certificate request was pending? (For example, a certificate request was generated and sent to VeriSign. Before the certificate was installed, a service pack was applied, the high encryption pack was installed, or the Web site bindings were changed.) If so, you must generate a new certificate request. It is important that you do not change anything while a certificate request is pending.

  • Does the Web site have a secure identity? To confirm this, follow these steps:

    1. Make sure that the Web site is bound to a secure port.
      1. From the Microsoft Management Console (MMC), right-click the Web site and click Properties.
      2. On the Web Site tab, note the IP address (this may be All Unassigned) and SSL port.NOTE: If the SSL port is blank, type 443 and restart the IIS service. If the port is dimmed, a server certificate has not been successfully installed. For more information, see the following Knowledge Base article:
        228836 Installing a New Certificate with Certificate Wizard for Use in SSL/TLS
    2. Confirm that the Web site is correctly bound to the network card.
      1. From a command prompt, type netstat -an.
      2. If the Web site was bound to the All Unassigned IP address and SSL port 443, verify that the Local Address entry is

        If the Web site was bound to a specific IP address (for example, and SSL port 443, verify that the Local Address entry is IPaddress:443 (for example,

ID articolo: 292296 - Ultima revisione: 20 nov 2006 - Revisione: 1