Please keep in mind that without knowledge of your specific problem I can only point you towards the right direction.

Windows XP Running Service Pack 2 and higher (This includes Vista and Windows 7)
Windows XP SP 2 and higher by default turns on the Personal Firewall Component of Windows XP. This will by default block your connection to your SQL Server. You will need to open the firewall to allow this traffic, or turn off the firewall.

There are several steps that I am going to lay out here to attempt to find the problem. We will be starting with the most basic, and working up to the more complex. Some of the more complex will involve people from network security, network engineering and/or your ISP.

1. Can you ping the server?
From a command prompt type:

ping {servername}

If you can not ping the server then you need to make sure that both you and the server are online. (This may not mean that either you or the server are offline. It may simply mean that someone has blocked ICMP packets from passing from you to the server for some reason.)

2. Can you telnet to the SQL Service port on the SQL Server?
From a command prompt type:

telnet {servername} 1433

If you get a black window with a flashing cursor that means that you have connected to the SQL Server. If you get an error message that means that something is blocking your connection to the SQL Server. Check for firewalls running on both machines, or on the network between you and the server. If the server is hosted by an ISP outside of your company’s control, check with them, and with your ISP to ensure that neither of them are blocking port 1433. If they are blocking access to the SQL Server they will have another way for you to access the SQL Server, probably a web based version of Enterprise Manager. There are several on the market, and they all work fairly well.

There are a couple of ways to check what port SQL Server is listening on.
2a (SQL 2000). Log on to the servers console, and open Enterprise Manager. Right click on the server and click properties. Click Network Configuration. Check the properties for TCP/IP. It will tell you what TCP port the SQL Server is listening on.

2b (SQL 2005/2008). Log onto the servers console and open the SQL Server Configuration Manager.  Navigate to the SQL Server 200n Network Configuration and select the “Protocols for MSSQLSERVER (or YourInstanceName if a named instance).  Open the TCP/IP protocol in the right hand pane.  On the IP Addresses tab the port number that SQL Server should be listening on is shown.

2c. Check the Current SQL Server Log (the ERRORLOG if your looking at the actual file). At the beginning of the log there should be one line for each IP on the server. Something like:

SQL server listening on 127.0.0.1: 1433.

That’s the port that it’s listening on.

If these lines aren’t there, and you’ve checked the TCP/IP is turned on, then there is probably an error saying that the port couldn’t be opened. This means that something else was using the port at startup. Odds are what ever was using it no longer is, and a service restart will fix the problem.

3. Can you connect to the file share on the server?
If this is being blocked that could also explain why you can not get connected. By default SQL Server will use TCP/IP port 1433 as it’s default connection method, with named pipes as a backup. If you can’t connect to the Windows file share you won’t be able to connect to the SQL Server over named pipes.

4. Can you connect to the SQL server from another machine on the same network as the workstation that isn’t working? If so then the problem is probably with the nonworking workstation, or some setting on a router or firewall that is preventing this machines access.

5. Are there any firewalls or ACLs on your network preventing access?

At this point odds are you are either connected to the SQL Server or you know why you are not. If you still can’t connect post a question in one of the SQL Server forums and someone will do there best to help you. You will want to post the results of these questions so that they don’t ask you to try them again.

This post is a copy of an FAQ that I posted on tek-tips.com a while back.

Denny

I can’t stress this enough.  Actually reading the error messages when there is a problem is key to solving the problems.

Most of the time (I admit, not all the time) SQL Server will give you some very useful information about what to do next.

Recently someone posted the following error message and asked how to resolve it.

Msg 682, Level 22, State 148, Line 1
Internal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption.

Now just by reading this error figuring out the next step should be pretty easy.  Run DBCC CHECKDB and post that information, or better yet after it runs and tells you that there is corruption in your database, follow the instructions that it gives you.  Why should you do this?  Well because when you post this error message on a forum you will be told to go and run DBCC CHECKDB and report back.

Those that answer questions online don’t have any magical power to know what’s happening on your SQL Server.  If you don’t read the errors and follow what they tell you, we are not going to be able to help any beyond that.

My rant now ends.

Denny

1. Don’t use topics like “Help!!!” or “It doesn’t work”.  Using a descriptive topic will make more people want to read your thread and help you out.
2. Be polite when talking to the people who are trying to help you.  They aren’t getting paid to do this, so be nice to them.  It’s always nice to get a thank you from the poster.
3. Check your spelling and grammar.  It doesn’t have to be perfect, but many people prefer proper spelling and grammar. (Mine isn’t the best, but I do try.)  If English isn’t your first language and people are giving you a hard time about your spelling or grammar some people will be a little more forgiving once they know that you are not a native English speaker.
4. If the message board is in English and you are posting an error message which is in another language, please translate it to English.  More people will be able to read it that way.  You may not get the translation perfect, but it’s usually close enough to get the point across.
5. Don’t post just the error number.  There are thousands of error messages and we need the entire error message.
6. Don’t just say that it’s broken.  Be specific about what isn’t working.
7. Let the readers know what you have done to try to fix the problem already.  That will save you time as the people trying to help won’t have to have you try stuff twice.
8. If you find the solution your self post it to the thread.  This will help the next person who has the same problem.  These forums are all about helping others and this is a great way to give back to the community.
9. Please remember that the people responding aren’t computers.  It may take time for someone to read your thread who knows the answer.

Denny