>>>>>>>>>>>>>>>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
>>>>>>>>>>
>>>>>>>>>>Which one - SQL or Windows Authentication?
>>>>>>>>>>
>>>>>>>>>>Judging from your previous msg to me you were connecting in SQL Management Studio via Windows authentication. To do that remotely your connection string will need to use a trusted connection.
>>>>>>>>>>
>>>>>>>>>>To use SQL authentication, you'll have needed to set the server itself to use Mixed authentication when you set it up.
>>>>>>>>>
>>>>>>>>>Who's talking connection strings???
>>>>>>>>>
>>>>>>>>>I simply want to open SSMS on my workstantion and connect to SQL Server on my Windows Server.
>>>>>>>>>
>>>>>>>>>At any rate, I'm using Windows Authentication.
>>>>>>>>
>>>>>>>>I'll ask a seemingly dumb question - are both machines on a local network on the same windows domain?
>>>>>>>
>>>>>>>They're both on the same network in the same workgroup. I do not have a domain set up.
>>>>>>
>>>>>>I don't think that will work with Windows Security since you are not the same user from machine to machine.
>>>>>>
>>>>>>Try enabling Mixed Mode authentication (if it isn't already enabled) and try connecting as the sa user.
>>>>>>
>>>>>>To change authentication mode, on the SQL Server machine..
>>>>>>
>>>>>> In Object Explorer, right-click the server, and then click Properties.
>>>>>> On the Security page, select SQL Server and Windows Authentication mode.
>>>>>> Restart the SQL Server service.
>>>>>
>>>>>Same error.
>>>>
>>>>The machine where SQL Server is installed does not have another firewall installed (like part of an A/V suite)?
>>>
>>>I have not yet installed AV
>>
>>From the remote machine, try telnetting to the SQL server's IP address on port 1433..
>>example..
>>telnet 10.1.2.10 1433
>>
>>If SQL or something else is listening, you should wind up with a black command window.
>>
>>If a firewall is blocking you or SQL is not listening on that port, you'll probably get a connection refused message..
>
>It sounds like it might be some kind of rights issue??? Are you sure the server machine and the sql server itself has your user setup?..and you sure you have all the rights needed Kevin?

I had asked him to try logging in as sa - there should not be a rights issue with that.

Kevin - can you log in as sa from SSMS on the SQL server machine?