Troy Tate
0 pts. | Jun 15 2009 11:47AM GMT
Be sure the SQL service is running on the server. You can also check at a cmd prompt to see if the server is listening on port 1433. Type netstat -a | find “LISTENING” . This will return a list of all of the listening ports on the server. If port 1433 (standard SQL port) is not shown then either the service is listening on another port or the service is not running.
Providence
15 pts. | Jun 15 2009 12:05PM GMT
I figured out my problem.
I’m ashamed to admit that the solution was rather simple, but I think my Google search keywords were bad
I hadnt set the server to allow remote connections : /
This can be done by running surface area configuration (Start » Programs » Microsoft SQL Server 2005 » Configuration Tools) and going to configuration for services and connections, and then under remote connections selecting local and remote connections.
Could have sworn I had this enabled but what ever






