The following post describes about the troubleshoot steps involved when we find that the SQL
server management studio is not getting connected to the sql server 2005 instance (using TCP/named pipes)
The following error comes sometimes when we try to connect to remote SQL server :
1. First check whether the firewall is turned on. If it is then you have to do the following
settings :
1. Add an exception for sqlsrvr.exe and sqlbrowser.exe (must be in
Program Files/
Microsoft SQL Server/ 90/shared)
2. Add a port
number 1432 (it is
the port on which SQL database listens the requests coming from its clients).
2. Go to Start ->
Programs -> Microsoft SQL Server 2005 ->
Configuration Tools -> SQL Server
Configuration Manager. From the left pane, click on Protocols for
. Enable Shared Memory, Named pipes, TCP/IP.
3. Go to Start -> Programs -> Microsoft SQL Server 2005 -> Configuration Tools -> SQL Server Surface Area Configuration. Click on "Surface area configuration for services and connections". Under MSSQL -> Database Engine, select Remote connections and choose "Using both TCP/IP and named pipes".
So with these steps your SQL client would be getting connected to remote sql server.