June 8, 2015 at 5:37 pm
We have an Active/Passive 2-node SQL Server 2012 cluster.
I'm suddenly having trouble connecting to the active node by the server's physical name in SSMS. I've never had that issue before.
I tried both SQL and Windows authentication. Named Pipes and TCP are enabled, 1433 is used as the default port.
I get the following error message:
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) (.Net SqlClient Data Provider)
Thank you
June 9, 2015 at 5:35 am
firewall in operation maybe, have you checked this?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 9, 2015 at 6:29 am
Len-153367 (6/8/2015)
We have an Active/Passive 2-node SQL Server 2012 cluster.I'm suddenly having trouble connecting to the active node by the server's physical name in SSMS. I've never had that issue before.
I tried both SQL and Windows authentication. Named Pipes and TCP are enabled, 1433 is used as the default port.
I get the following error message:
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) (.Net SqlClient Data Provider)
Thank you
You're sure SQL Server is running?
Does the hostname resolve correctly? (nslookup, ping)
Try connecting in SSMS using the IP address and port number (192.168.0.100,1433)?
Try to telnet directly to IP and Port?
On the SQL server itself, netstat -an and make sure it is listening on port 1433 for the IP you expect.
Is Windows Firewall configured properly (already mentioned)?
June 9, 2015 at 6:44 am
You are giving wrong SQL Server name it seems. Double Check you SQL Server name.
You wont be able to connect to physical server unless SQL server and physical server have same name which i doubt
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply