Isolating Connection Problems

Note For immediate help in diagnosing your connection problems, see the new online setup troubleshooter on the Product Support Web site. For more information, see Help with Connectivity.

When an application or tool has problems connecting to Microsoft® SQL Server™ 2000, there might be a problem with SQL Server, with the network, or with both. Regardless of the network you are running on, there are several items that you can check to isolate the problem. Check that:

For servers running Microsoft Windows NT® 4.0, the local connection to SQL Server over Named Pipes is available. You can test a local Named Pipes connection by using osql with no servername argument. If you cannot make a local connection using Named Pipes, either you are using an invalid login or there is a problem with SQL Server.
For servers running Microsoft Windows® 95 or Microsoft Windows 98, the local connection to SQL Server uses the Shared Memory Net-Library.
The network components match the requirements specified in Network Protocols.
The default client Net-Library is appropriate for your network. You can determine and, if necessary, change the default client Net-Library by using SQL Server Client Network Utility in the Microsoft SQL Server program group.
The network connection information on the server is appropriate for your network (if you are running SQL Server and listening on other interprocess communication (IPC) mechanisms in addition to Named Pipes). You can determine and, if necessary, change the network SQL Server is listening on using SQL Server Server Network Utility in the Microsoft SQL Server program group.
The network connection between the client workstation and the server is established. If you test the network connection and determine that it is not open, check that:
- The hardware connection is not disabled due to loose connectors or plugs.
- The network software is installed and running on both the client workstation and the server.

Isolating Connection Problems

See Also