(This article applies to MS SQL 2005, 2008, 2008 R2, and 2012)
Windows firewall is usually the culprit in these scenarios. Open TCP
port 1433 for the service itself, and 1434 if you need to use the SQL
- Open cliconfg from a RUN prompt and make sure TCP/IP is an enabled protocol.
For SQL 2005/2008/2008 R2: Check the Services tool, Start > Administrative Tools > Services, to see that the service named SQL Server (MSSQLSERVER) is started.
For MS SQL 2012: Use the Windows key or hover over the left lower corner of the desktop and select Administrative Tools, then Services to see that the service named SQL Server (MSSQLSERVER) is started.
- Ensure that you are using the correct credentials to authenticate. The default SQL administrator account is named sa
and if you built the server from one of our server images with MSSQL
pre-installed, the password will be in a text file on the root of the C
- Use netstat –an from the command prompt to verify that the server is listening for SQL traffic on the correct ports.
- If the server is not listening for SQL traffic on the correct ports, use SQL Server Configuration Manager to change the ports.
you are using named instances when installing SQL, giving you the
ability to host multiple SQL versions or service types, you will have to
specify the name of the SQL instance when connecting rather than just
using the server’s name or IP. If you have created a named instance,
you will need to access it by appending the name to the server’s name or
IP, following a backslash (e.g. 220.127.116.11\SQLINSTANCENAME or