A matching pair of SQL Server Net-Libraries must be installed on a client and server computer to support a particular network protocol (for example, client TCP/IP Sockets Net-Library, server TCP/IP Sockets Net-Library). Some Net-Libraries, such as Named Pipes and Multiprotocol, support several network protocols.
All of the Microsoft® SQL Server™ client and server Net-Libraries are installed by SQL Server Setup. By default, during setup, the following server Net-Libraries are activated to listen for clients:
After the network connections are installed and configured, SQL Server can listen on any combination of the server Net-Libraries simultaneously.
The correct network protocols should already be installed on the client and server. Network protocols are typically installed during Windows setup; they are not part of SQL Server Setup. A SQL Server Net-Library will not work unless its corresponding network protocol is already installed on both the client and server.
If you have installed SQL Server and want to change your server Net-Libraries, start SQL Server Network Utility. This application allows you to activate, deactivate, and reconfigure server Net-Libraries to listen for clients on their corresponding network protocols.
SQL Server on Windows 95/98 does not support the server Named Pipes Net-Library. If you are using a Windows 95/98 server to run SQL Server, either the default Net-Library for the client must be changed to TCP/IP Sockets or Multiprotocol, or a new configuration entry must be created on the client that uses one of those Net-Libraries.
After activating the appropriate server Net-Library supporting a particular network protocol, you must configure any clients accessing the server through that network protocol. Use SQL Server Client Network Utility to: