Microsoft KB Archive/322144

= FIX: SECDoClientHandShake Cannot Connect to SQL Server =

Article ID: 322144

Article Last Modified on 10/29/2007

-

APPLIES TO


 * Microsoft Data Access Components 2.7

-



This article was previously published under Q322144



SYMPTOMS
When attempting to connect to Microsoft SQL Server 2000, you may receive one of the following error messages:

Unable to connect to server. Server msg 18, level 16, state 1. SSL security error

-or-

Unable to connect to server. Reason: SSL security error. ConnectionOpen (SECDoClientHandShake)...

The client is unable to open a connection to the SQL Server.



CAUSE
This problem has been reported to occur if you have Microsoft SQL Server 2000 configured to load an SSL certificate to perform encryption and you are attempting to connect over a slow or low bandwidth network connection to the target SQL Server.



RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next MDAC service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version           Size    File name --  07-May-2002  16:37  2000.81.8707.0     61,440  Dbnetlib.dll



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This bug was corrected in MDAC SP1.



MORE INFORMATION
Note that this problem occurs only if a Secure Sockets Layer (SSL) certificate is installed on the computer that is running Microsoft SQL Server 2000 and the certificate meets the requirements for Microsoft SQL Server to perform encryption. You do not have to enable &quot;Force Protocol Encryption&quot; on the client or on the server for this problem to occur. The SQL Server network libraries try to use encryption internally (even with &quot;Force Protocol Encryption&quot; disabled) to encrypt the login packet if SQL Server finds an SSL certificate that meets the requirements for SQL Server to perform encryption.

For additional information about how to confirm that the SSL certificate meets the requirements for SQL Server to perform encryption, click the article number below to view the article in the Microsoft Knowledge Base:

316898 HOW TO: Enable SSL Encryption for SQL Server 2000 with Microsoft Management Console

Typically, if you have an SSL certificate on the computer with the same name as the SQL Server name, and if the certificate permits Server Authentication, this meets the basic requirements for SQL Server to perform SSL encryption.

This problem has been reported when a Virtual Private Network (VPN) is used to connect to SQL Server if the SSL encryption requirements are met. It has been reported but not verified that you can resolve this problem by increasing the connection timeout value. Additionally, this problem has been reported to occur intermittently (for example, in one out of 100 connection attempts under certain network conditions). If the problem still occurs after you apply this hotfix, try to increase the connection timeout value to alleviate the problem.

