Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am new to managing servers but I have just been given full access to set up an MS SQL Database on win server 2003. I have created a Database successfully and can connect locally (via remote desktop server)

Problem is I can't connect to the database from my personal computer (remotely, via ms sql server management studio). I have followed several tutorials such as:

Also, allow remote connections is enabled in sql and windows firewall is disabled.

The error I am receiving is:

Cannot connect to 'servername'


A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

Any help will be great, thanks!

share|improve this question

There may be other firewalls between the boxes. But first check that SQL server is configured to listen for network connections. by default (for security) it will not accept network connections.

Have you configured the network to accept TCP/IP or named pipe connections? And verified that it is listening on those connections? How to configure SQL Server 2005 to allow remote connections

share|improve this answer

Can you "ping" the destination server?, can you "telnet" to sql on the destination server?

telnet <servername> 1433
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.