DBNetLib Install

[Ron Harman]

I am trying to use secure SQL connections and it appears I need to use teh
DBNETLIB to do so. From where are these files installed?

Ron

[linda deng[MS]]

Hi Ron,

Encryption is implemented and configured by using the SQL
Server Multiprotocol Net-Library in SQL Server 7.0 and the Multiprotocol
Encryption is the only option. Please refer to Microsoft SQL Server 7.0
Books Online with keyword 'Encryption' for details.
You need Windows 2000 and SQL Server 2000 for higher
encryption by using certificates/SSL. The SSL encryption is performed
within the Super Socket Net-Library (Dbnetlib.dll and Ssnetlib.dll) and
applies to all inter-computer protocols supported by SQL Server 2000. The
files are installed from MDAC. It's shipped with Windows 2000/XP and SQL
Server as well. You can download the latest version from
www.microsoft.com/data. For more information, please see SQL Server 2000
Books Online with keyword 'Secure Sockets Layer' and 'Using Encryption
Methods'.

Sincerely,

Linda Deng
Microsoft Support Engineer

This posting is provided "AS IS" with no warranties, and confers no rights.

[Ron Harman]

Linda,

Thanks you for taking the time to reply. I ahve checked the documentation
but still am unclear. We have successfully used encryption with 2000/2000
but am having trouble with some of the clients. We use VB to connect to SQL
Server and our connection string works on some PC but not on others. It
appears that thosse that do not work do not have DBNETLIB so I made an
assumption. Oure connect string is:

driver={SQL Server};server=IA;database=dbname;uid=username;pwd=pword

I get errors (usually General Connection Errors) from some clients and not
others. I have tried all the paramaters (ENCRYPT=YES,Network=......) and
canot find the solution. Any help would be greatly appreciated. This has
caused us significant time.

Thanks again,

Ron

"linda deng[MS]" <lid...@online.microsoft.com> wrote in message
news:Eh2BzIdDCHA.1816@cpmsftngxa07...

[linda deng[MS]]

Hi Ron,

Please make sure whether those clients which can't work well can connect
to the SQL Server with the Client Tools such as QA, EM directly or not.
This is probably caused by the network.

[Ron Harman]

I tried that and reviewed it with out IT guy and we could find no
differences. However, if I disable the security on SQL Server, the clients
that could not connect with encryption, can. For those that could under
encryption, the change did not affect them. That is why i thought I must be
doing something wrong with the net-libs.

"linda deng[MS]" <lid...@online.microsoft.com> wrote in message

news:02bB2zCECHA.1600@cpmsftngxa08...

[linda deng[MS]]

Hi Ron,

You can follow the guide from the KB article (the link illustrated below)
to check whether the clients which can't work well are configured correctly
and how to enable the SSL Encryption for SQL Server.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q276553

Modify the ODBC or OLEDB connection string:

1. ODBC

Driver=SQLServer;Server=ServerNameHere;UID=UserIdHere;PWD=PasswordHere;Netwo
rk=DBNETLIB.DLL;Encrypt=YES

2. OLEDB
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=dbNameHere;Data Source=ServerNameHere;Use
Encryption for Data=True

Please see http://support.microsoft.com/default.aspx?scid=kb;en-us;Q316779
to check whether the error occurs in your issue and workaround it.

[Ron Harman]

Thank you again for your help and patience. I did those things but what if
the client does not have hte DBNETLIB library on their system. The
connection string will not work. How do I install DBNETLIB?

"linda deng[MS]" <lid...@online.microsoft.com> wrote in message

news:uJAjixeECHA.1816@cpmsftngxa08...

[Ron Harman]

And we used the "Enable SSL Encryption on the SQL Server" option. So we
should not have to import/export certificates, right?

"linda deng[MS]" <lid...@online.microsoft.com> wrote in message

news:uJAjixeECHA.1816@cpmsftngxa08...

[linda deng[MS]]

Hi Ron,

The following is from Microsoft SQL Server Books Online and it is for your
information.
SQL Server 2000 can use the Secure Sockets Layer (SSL) to encrypt all data
transmitted between an application computer and an instance of SQL Server
on a database computer. Both the client and the server computers must have
the proper certificates installed for SSL encryption to function.