Troubleshooting SQL Server

Overview

Connection with SQL Server may fail for a number of reasons. This topic identifies known issues and procedures to rectify connection issues.

SQL Server Connection Checklist

Applies to: SQL 2005

1. Windows Firewall on Client (workstation) must be Off. Windows Firewall is known to block SQL Ports 1433 and 1434 TCP / UDP even when excluded under settings.
2. SQL Server browser must be running (applies to SQL Server only (not MSDE)).
   1. Open SQL Server Surface Area Configuration under: SQL Server 2005 > Configurations Tools > SQL Server Surface Area Configuration.
   2. Select SQL Server Browser menu and check that the service status is "running".
3. Check that SQL Server is using TCP:
   1. Open SQL Server Surface Area Configuration under: SQL Server 2005 > Configurations Tools > SQL Server Surface Area Configuration.
   2. Select Remote Connections and select the Local and Remote Connections option to enable it.
   3. Select the Using TCP/IP and Named Pipes option.

Identifying connections with the local machine

Applies to: Windows 2000, XP

Netstat identifies connections with the local machine. This is helpful when troubleshooting SQL Server connections, which use Ports 1433 and 1434 TCP and UDP.

1. Run "netstat -a" from the Windows command line (or "netstat /?" for a list of valid commands).

A list of connections with the local machine is displayed.