I'm trying to run a test from my test environment which is a non-domain Windows 2000 server to access my domain 2003 with SQL2005. I have install 2005 tools to try to access the SQL server.
- I have try following the KB265808 - no success.
- Reading alot of blogs and it seems all are pointing to the same problem. "Remote access" but the settign is enabled.
Error Message:TITLE: Connect to Server
Cannot connect to ardsqldatawh.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
Question: Could Windows 2003 security be blocking access? I'm using sa account to access.
Also, sa account does not seems to work for remote access. It is ok when accessing locally.
Any help would be appreciated.
949jc
Hi 959jc,
Have you configured the Windows firewall on your server machine to allow remote connections? If you're intending to use Named Pipes, then you will need to enable the "File and Print sharing" exception. Also, please take a look at this topic in the BOL for additional info regarding configuring firewalls: http://msdn2.microsoft.com/en-us/library/ms175043.aspx.
Another consideration is whether you've restarted your instance after enabling remote protocols.
Otherwise, please provide your connection string and the contents of your error log after you've restarted the service.
Thanks,
Il-Sung.
No comments:
Post a Comment