October 19, 2012 at 1:24 pm
I have installed SQL Server 2008 R2 on 5 new Servers within the last year.
I have not had any issues but on the last server I have connection issues.
The server that I'm having trouble with is a default instance of SQL Server.
I got a call from a user that they could not connect. They got an error something to the effect that SQL Server was not configured to allow remote connections.
I tried it on my machine and got the same error.
So I checked the Server and it is configured to allow remote connections
I checked the Protocols and the only one that was disabled was named pipes.
I enabled named pipes and I tried again and I did not get the remote connections was not configured, I just got a time out error.
I specified to connect in SSMS via Named Pipes and it connected.
I intended to research and hopefully resolve the issue but the user apprached me today and he was trying to import an Excel Document into a Database on that Server and it times out.
I created a new SSIS Package and when I created the connection when I clicked on the Database Drop Down I get nothing. I entered the Database name but it timed out on me.
If I specify TCP/IP as the protocol in SSMS I get the following error:
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 connection. (provider: TCP Provider, error:0 - A connection attampt failed because the connected party did not properly respond after a period of time, or established connection failed because the connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
Any help would be greatly appreciated.
Thank you.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
October 19, 2012 at 1:54 pm
It was a Windows Firewall Issue.
The following is a good article which was helpful to me in resoving the issue:
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
October 19, 2012 at 7:17 pm
I will make sure that the Named Pipes Protocol is disabled on all of my Servers for it is a Security Risk.
For one it bypassed the firewall.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply