January 30, 2006 at 1:40 pm
I installed SQL 2005 on a Virtual Windows 2003 Server and ran into a connection issue. When trying to connect to the default SQL Server instance in Management Studio I get this error:
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 error : 40 - could not open a connection to SQL Server) (Microsoft SQL Server, Error 53).
However, the server is set to allow remote connections and all protocols are enabled. I tried connecting with the "servername, port #" and got the same error; but I was able to connect using the IP address.
I tried creating an ODBC source using the SQL Native Client and got the same error. Then I created an ODBC DSN using the SQL 2000 driver and was able to connect to the server name using Named Pipes and also TCP/IP. I didn't have any connection issues with SQL 2005 on a normal Windows 2003 server.
This is just a test box but I was wondering if this is by design, is it a bug, or is there something that I'm not doing properly?
Linda
January 31, 2006 at 3:09 am
Perhaps you have DNS / name lookup issues?
Can you ping your server by name / by IP?
Can you open any file shares (like \\SERVER\c$)? If not, then does it work if you use the IP address?
Try putting an entry in your hosts file or fixing up your DNS settings...
January 31, 2006 at 5:51 am
I can ping both ways successfully and can map to any shares. Interesting thing though, I can connect to SQL Server by name this morning. Just wondered if Active Directory had something to do with it... Very curious.
March 2, 2006 at 5:10 pm
I have similar kind of issue with a new installation of SQL Server 2005. Since I already have SQL Server 2000 on that server, I installed 2005 on a named instance called "SQL2005" . I could connect to database engine through Managerment studio using "servername\SQL2005" from the server.
I am able to conncet to Analysis Services and Reporting services through using "servername\SQL2005" from another computer. I get an error when I try to connect to SQL Server database engine and Integration Services from another computer. I even tried "ipaddress\SQL2005". I ping the servername and ip address. Both returned results.
The error I am getting is as follows
----------------
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
-----------------
Any kind of help is appriciated.
Thanks,
Promod.
March 3, 2006 at 9:44 pm
Run the surface area configuration tool - turn on the browser service (I think this allows clients to look up the port number for different instances - used to be the UDP 1434 in SQL 2000???) and also you must tick the box elsewhere in the tool to enable remote client connections.
SQL is install this way to help isolate breakouts of future worm viruses, etc...
March 3, 2006 at 9:44 pm
PS - you should probably open up a new thread if you have a new issue as ppl don't tend to look at the old threads...
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply