>Hi Kevin,
>
>>I have SQL Server 2005 running on Windows Server 2003 R2. I have enabled Remote connections in the Surface Area Configuration dialog. I can work with SQL while on the server.
>>
>>When I attempt to connect from my other PC's running Windows XP Professional I get :
>>
>>"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."
>>
>>I can see the server name in SSMS, I just can't connect. The Windows Firewall is not running. Anyone know what;s going on here?
>
>I had a similar issue recently (you could look at the thread number 1441364 in December. I am pretty sure it turned out to be a firewall issue and I had to get a port open to make it work. I proved it to be a firewall by turning off the firewall on both my desktop and the server and retested. Then I turned them on one at a time to recheck. I can't remember what I did specifically to but there is a tool out there also called PFP port checker that was helpful when I was trying to get the specific ports open. In my case I had to open the port on the server for the sql server instance. I found which one by checkin in SSMS on the server under the magement section of the database to see which port the SQL server was listening to. I learned of this from someone in the thread I mentioned above.
>Tim

Excellent! I'll try it.

Thanks