1.
"Establishing an Encrypted Connection
If you want users to be able to establish an encrypted connection to an instance of SQL Server, you can do so by enabling encryption for the Multiprotocol Net-Library.

How to enable encryption after SQL Server has been installed (Network Utility)

Note If you want to use encryption with a failover cluster, you must install the server certificate with the fully qualified DNS name of the virtual server on all nodes in the failover cluster. For example, if you have a two-node cluster, with nodes named test1.redmond.corp.microsoft.com and test2.redmond.corp.microsoft.com and a virtual SQL Server "Virtsql", you need to get a certificate for "virtsql.redmond.corp.microsoft.com" and install the certificate on both nodes. You can then check the Force protocol encryption check box on the Server Network Utility to configure your failover cluster for encryption.


To enable encryption

1.On the Start menu, point to Programs/Microsoft SQL Server, and then click Server Network Utility

2.If Multiprotocol does not appear under Enabled protocols, click it under Disabled protocols, and then click Enable. Otherwise, skip to Step 3.

3.Under Enabled protocols, click Multiprotocol, and then click Properties.

4.Select the Enable encryption check box. "


2.
"Multiprotocol Clients
The Multiprotocol selection has two key features:

Automatic selection of an available network protocol to communicate with an instance of Microsoft® SQL Server™.
This is convenient when you want to connect to multiple servers running different network protocols but do not want to reconfigure the client connection for each server. If the client and server Net-Libraries for TCP/IP Sockets, NWLink IPX/SPX, or Named Pipes are installed on the client and server, the Multiprotocol Net-Library will automatically choose the first available network protocol to establish a connection.

Client encryption.
You can enforce encryption over the Multiprotocol Net-Library on clients running on the Microsoft Windows NT® 4.0, Windows® 2000, Windows 95, or Windows 98 operating system to prevent others from intercepting and viewing sensitive data.

The Multiprotocol Net-Library takes advantage of the remote procedure call (RPC) facility of Windows NT 4.0 and Windows 2000, which provides Windows Authentication. For the Multiprotocol Net-Library, clients determine the server address using the server name.


How to configure a client to use the Multiprotocol Net-Library (Client Network Utility)

Note Before creating a Multiprotocol client configuration, make sure your computer has at least one IPC protocol loaded under Multiprotocol on the server (Named Pipes, NWLink IPX/SPX, TCP/IP, or Windows Sockets).


To configure a client to use the Multiprotocol Net-Library

1.Click the Alias tab, and then click Add.

2.In the Add Network Library Configuration dialog box, click Multiprotocol.

3.In the Server alias box, enter the name of the instance of Microsoft® SQL Server™ listening on the Multiprotocol Net-Library.

4.Leave the Additional parameters box empty, unless the server requires specific parameters. Verify with your network administrator before entering parameters."