>>>>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:
>>>>
>>>>
>>>>
>>>>
>>>>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?
>>>
>>>Make sure your are configured to use TCP/IP.
>>>
>>>Make sure the SQL Server is set to allow remote connections.
>>>
>>>Open TCP Port 1433 and you should be all set.
>>
>>I have done all this, and I still cannot connect remotely
>
>Are you using SQL Server or SQL Express? SQLExpress by default names its' first instance 'SQLExpress'.
>
>In that case, you need to try to connect to MAROIS-DEV1\SQLExpress (The Browse for more button does not show instance names - it only shows default instances on servers).
No, SQL 2005 full version
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people