SQL Server uses a dynamic link library (DLL), called a Net Library, to communicate with a particular network protocol. A matching pair of Net Libraries must be active on both client and server computers to support the desired network protocol. For example, to enable a client application to communicate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets Net Library (DBNETLIB.dll) must be configured to connect to that server on the client computer, and the server TCP/IP Sockets Net Library (SSNETLIB.dll) must be listening on the server computer. Also in this case the TCP/IP protocol stack must be installed on both the client and server computers

After installing SQL Server 2000, you need to define the behaviors of the client Net Libraries by using the Client Network Utility and server Net Libraries by using the Server Network Utility. All the server Net Libraries are installed during the server portion of SQL Server Setup, but some of them may not be active. By default, SQL Server enables and listens on TCP/IP, Named Pipes, and Shared Memory. For a client to connect to a server running SQL Server 2000, the client must use a client Net Library that matches one of the server Net Libraries the server is currently listening on.


source site:

http://www.sqljunkies .com /HowT o/2E1101E0-D5C1-4DBD-A398-FE48 5DFA4 39B.scuk

Answered by R.P. Singh , an ibibo Master, at 6:01 PM on July 22, 2008

SQL Server uses a dynamic link library (DLL), called a Net Library, to communicate with a particular network protocol. A matching pair of Net Libraries must be active on both client and server computers to support the desired network protocol. For example, to enable a client application to communicate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets Net Library (DBNETLIB.dll) must be configured to connect to that server on the client computer, and the server TCP/IP Sockets Net Library (SSNETLIB.dll) must be listening on the server computer. Also in this case the TCP/IP protocol stack must be installed on both the client and server computers

After installing SQL Server 2000, you need to define the behaviors of the client Net Libraries by using the Client Network Utility and server Net Libraries by using the Server Network Utility. All the server Net Libraries are installed during the server portion of SQL Server Setup, but some of them may not be active. By default, SQL Server enables and listens on TCP/IP, Named Pipes, and Shared Memory. For a client to connect to a server running SQL Server 2000, the client must use a client Net Library that matches one of the server Net Libraries the server is currently listening on.


source site:

http://www.sqljunkies .com /HowT o/2E1101E0-D5C1-4DBD-A398-FE48 5DFA4 39B.scuk

Answered by Rocky , an ibibo Master, at 8:02 PM on July 19, 2008

SQL Server uses a dynamic link library (DLL), called a Net Library, to communicate with a particular network protocol. A matching pair of Net Libraries must be active on both client and server computers to support the desired network protocol. For example, to enable a client application to communicate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets Net Library (DBNETLIB.dll) must be configured to connect to that server on the client computer, and the server TCP/IP Sockets Net Library (SSNETLIB.dll) must be listening on the server computer. Also in this case the TCP/IP protocol stack must be installed on both the client and server computers

After installing SQL Server 2000, you need to define the behaviors of the client Net Libraries by using the Client Network Utility and server Net Libraries by using the Server Network Utility. All the server Net Libraries are installed during the server portion of SQL Server Setup, but some of them may not be active. By default, SQL Server enables and listens on TCP/IP, Named Pipes, and Shared Memory. For a client to connect to a server running SQL Server 2000, the client must use a client Net Library that matches one of the server Net Libraries the server is currently listening on.


source site:

http://www.sqljunkies .com /HowT o/2E1101E0-D5C1-4DBD-A398-FE48 5DFA4 39B.scuk

Answered by .... ..... , an ibibo Master, at 8:23 PM on July 16, 2008

SQL Server uses a dynamic link library (DLL), called a Net Library, to communicate with a particular network protocol. A matching pair of Net Libraries must be active on both client and server computers to support the desired network protocol. For example, to enable a client application to communicate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets Net Library (DBNETLIB.dll) must be configured to connect to that server on the client computer, and the server TCP/IP Sockets Net Library (SSNETLIB.dll) must be listening on the server computer. Also in this case the TCP/IP protocol stack must be installed on both the client and server computers

After installing SQL Server 2000, you need to define the behaviors of the client Net Libraries by using the Client Network Utility and server Net Libraries by using the Server Network Utility. All the server Net Libraries are installed during the server portion of SQL Server Setup, but some of them may not be active. By default, SQL Server enables and listens on TCP/IP, Named Pipes, and Shared Memory. For a client to connect to a server running SQL Server 2000, the client must use a client Net Library that matches one of the server Net Libraries the server is currently listening on.


source site:

http://www.sqljunkies .com /HowT o/2E1101E0-D5C1-4DBD-A398-FE48 5DFA4 39B.scuk

Answered by Ni .. , an ibibo Master, at 8:49 PM on July 13, 2008

SQL Server uses a dynamic link library (DLL), called a Net Library, to communicate with a particular network protocol. A matching pair of Net Libraries must be active on both client and server computers to support the desired network protocol. For example, to enable a client application to communicate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets Net Library (DBNETLIB.dll) must be configured to connect to that server on the client computer, and the server TCP/IP Sockets Net Library (SSNETLIB.dll) must be listening on the server computer. Also in this case the TCP/IP protocol stack must be installed on both the client and server computers

After installing SQL Server 2000, you need to define the behaviors of the client Net Libraries by using the Client Network Utility and server Net Libraries by using the Server Network Utility. All the server Net Libraries are installed during the server portion of SQL Server Setup, but some of them may not be active. By default, SQL Server enables and listens on TCP/IP, Named Pipes, and Shared Memory. For a client to connect to a server running SQL Server 2000, the client must use a client Net Library that matches one of the server Net Libraries the server is currently listening on.


source site:

http://www.sqljunkies .com /HowT o/2E1101E0-D5C1-4DBD-A398-FE48 5DFA4 39B.scuk

Answered by Raksha , an ibibo Master, at 9:24 AM on July 10, 2008

well, SQL Server uses a dynamic link library (DLL), called a Net Library, to communicate with a particular network protocol. A matching pair of Net Libraries must be active on both client and server computers to support the desired network protocol. For example, to enable a client application to communicate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets Net Library (DBNETLIB.dll) must be configured to connect to that server on the client computer, and the server TCP/IP Sockets Net Library (SSNETLIB.dll) must be listening on the server computer. Also in this case the TCP/IP protocol stack must be installed on both the client and server computers

After installing SQL Server 2000, you need to define the behaviors of the client Net Libraries by using the Client Network Utility and server Net Libraries by using the Server Network Utility. All the server Net Libraries are installed during the server portion of SQL Server Setup, but some of them may not be active. By default, SQL Server enables and listens on TCP/IP, Named Pipes, and Shared Memory. For a client to connect to a server running SQL Server 2000, the client must use a client Net Library that matches one of the server Net Libraries the server is currently listening on.


source site:

http://www.sqljunkies .com /HowT o/2E1101E0-D5C1-4DBD-A398-FE48 5DFA4 39B.scuk

Answered by Romi , an ibibo Master, at 11:52 AM on July 06, 2008

SQL Server uses a dynamic link library (DLL), called a Net Library, to communicate with a particular network protocol. A matching pair of Net Libraries must be active on both client and server computers to support the desired network protocol. For example, to enable a client application to communicate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets Net Library (DBNETLIB.dll) must be configured to connect to that server on the client computer, and the server TCP/IP Sockets Net Library (SSNETLIB.dll) must be listening on the server computer. Also in this case the TCP/IP protocol stack must be installed on both the client and server computers

After installing SQL Server 2000, you need to define the behaviors of the client Net Libraries by using the Client Network Utility and server Net Libraries by using the Server Network Utility. All the server Net Libraries are installed during the server portion of SQL Server Setup, but some of them may not be active. By default, SQL Server enables and listens on TCP/IP, Named Pipes, and Shared Memory. For a client to connect to a server running SQL Server 2000, the client must use a client Net Library that matches one of the server Net Libraries the server is currently listening on.


source site:

http://www.sqljunkies .com /HowT o/2E1101E0-D5C1-4DBD-A398-FE48 5DFA4 39B.scuk

Answered by Gyan Singh , an ibibo Master, at 7:38 PM on June 27, 2008

SQL Server uses a dynamic link library (DLL), called a Net Library, to communicate with a particular network protocol. A matching pair of Net Libraries must be active on both client and server computers to support the desired network protocol. For example, to enable a client application to communicate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets Net Library (DBNETLIB.dll) must be configured to connect to that server on the client computer, and the server TCP/IP Sockets Net Library (SSNETLIB.dll) must be listening on the server computer. Also in this case the TCP/IP protocol stack must be installed on both the client and server computers

After installing SQL Server 2000, you need to define the behaviors of the client Net Libraries by using the Client Network Utility and server Net Libraries by using the Server Network Utility. All the server Net Libraries are installed during the server portion of SQL Server Setup, but some of them may not be active. By default, SQL Server enables and listens on TCP/IP, Named Pipes, and Shared Memory. For a client to connect to a server running SQL Server 2000, the client must use a client Net Library that matches one of the server Net Libraries the server is currently listening on.


source site:

http://www.sqljunkies .com /HowT o/2E1101E0-D5C1-4DBD-A398-FE48 5DFA4 39B.scuk

Answered by Sharad Singh , an ibibo Master, at 6:28 PM on June 27, 2008

SQL Server uses a dynamic link library (DLL), called a Net Library, to communicate with a particular network protocol. A matching pair of Net Libraries must be active on both client and server computers to support the desired network protocol. For example, to enable a client application to communicate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets Net Library (DBNETLIB.dll) must be configured to connect to that server on the client computer, and the server TCP/IP Sockets Net Library (SSNETLIB.dll) must be listening on the server computer. Also in this case the TCP/IP protocol stack must be installed on both the client and server computers

After installing SQL Server 2000, you need to define the behaviors of the client Net Libraries by using the Client Network Utility and server Net Libraries by using the Server Network Utility. All the server Net Libraries are installed during the server portion of SQL Server Setup, but some of them may not be active. By default, SQL Server enables and listens on TCP/IP, Named Pipes, and Shared Memory. For a client to connect to a server running SQL Server 2000, the client must use a client Net Library that matches one of the server Net Libraries the server is currently listening on.


source site:

http://www.sqljunkies .com /HowT o/2E1101E0-D5C1-4DBD-A398-FE48 5DFA4 39B.scuk

Answered by Shobhit , an ibibo Master, at 4:37 PM on June 26, 2008

hi there

SQL Server uses a dynamic link library (DLL), called a Net Library, to communicate with a particular network protocol. A matching pair of Net Libraries must be active on both client and server computers to support the desired network protocol. For example, to enable a client application to communicate with a specific instance of SQL Server across TCP/IP, the client TCP/IP Sockets Net Library (DBNETLIB.dll) must be configured to connect to that server on the client computer, and the server TCP/IP Sockets Net Library (SSNETLIB.dll) must be listening on the server computer. Also in this case the TCP/IP protocol stack must be installed on both the client and server computers

After installing SQL Server 2000, you need to define the behaviors of the client Net Libraries by using the Client Network Utility and server Net Libraries by using the Server Network Utility. All the server Net Libraries are installed during the server portion of SQL Server Setup, but some of them may not be active. By default, SQL Server enables and listens on TCP/IP, Named Pipes, and Shared Memory. For a client to connect to a server running SQL Server 2000, the client must use a client Net Library that matches one of the server Net Libraries the server is currently listening on.


source site:

http://www.sqljunkies .com /HowT o/2E1101E0-D5C1-4DBD-A398-FE48 5DFA4 39B.scuk

Answered by Reeta K , an ibibo Master, at 3:29 PM on June 26, 2008