>>>>>>>I have been trying to get SQL 2005 Remote Access configured on my Win 2003 server. I followed the directions here:
>>>>>>>http://support.microsoft.com/kb/914277
>>>>>>>
>>>>>>>
>>>>>>>When I attempt to connect to SQL on the server from my WinXP PC I get this:
>>>>>>
>>>>>>Connect using what technology?
>>>>>>>
>>>>>>>
>>>>>>>

>>>>>>>
>>>>>>>Cannot connect to MAROIS-DEV1.
>>>>>>>------------------------------
>>>>>>>ADDITIONAL INFORMATION:
>>>>>>>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: 1326)
>>>>>>>For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=1326&LinkId=20476
>>>>>>>

>>>>>>>
>>>>>>>The link points to nothing.
>>>>>>>
>>>>>>>The KB page says to add exceptions in the firewall. When I enable the firewall, even with the exceptions, I see cannot see MAROIS-DEV1 in the list of network servers. When I disable the firewall I can see it, I just cannot connect.
>>>>>>>
>>>>>>>Anyone know what's going on?
>>>>>>
>>>>>>Snip : "I see cannot see MAROIS-DEV1" - wanna take another stab at that statement :-}
>>>>>>Anyway - can you connect using the IP address of the server rather than the instance name ?
>>>>>
>>>>>I tried loggin in with the IP, and it failed to connect.
>>>>
>>>>I think this question was asked - but can you confirm that you've configured to allow remote connections over TCP/IP.
>>>>Have you allowed the SQL Service Browser to fire up ? If so does SMSE show the server when you use 'Browse for more' ?
>>>>Are you attempting to use Windows or SQL Server authentication ?
>>>
>>>Yes
>>
>>Four questions there, one a multiple choice. 'Yes' doesn't exactly work as an answer......
>
>Yes I confirmed that I configured to allow remote connections over TCP/IP
>Yes I allowed the SQL Service Browser to fire up
>Yes SMSE show the server when you I 'Browse for more'
>Yes I tried Windows & SQL Server authentication

Hmm, So management studio sees the SQL server instance and you're using SQL server authentication.
Does the login that you are using have a default database and sufficient access thereto (Not sure of my ground here but I think that can be a problem....)