August 17, 2017 at 1:00 pm
Hello,
How can I make it available to connect to sql using servername\instance name with a SQL 2 node cluster? If I have 2 nodes named server1 and server2 with the instance named mssqlcluster2 and I try to connect in management studio using server1\mssqlcluster2 it does not allow me to connect? Using SQL 2016. The active node is on server1 as well. Appreciate the help.
-
August 17, 2017 at 1:06 pm
JP10 - Thursday, August 17, 2017 1:00 PMHello,How can I make it available to connect to sql using servername\instance name with a SQL 2 node cluster? If I have 2 nodes named server1 and server2 with the instance named mssqlcluster2 and I try to connect in management studio using server1\mssqlcluster2 it does not allow me to connect? Using SQL 2016. The active node is on server1 as well. Appreciate the help.
-
More details please, is HAG a BAG? That would explain this.
😎
August 17, 2017 at 1:14 pm
Not following you Eirikur? What more details do you need?
August 17, 2017 at 1:31 pm
Hum! Using SSMS, try using IP Address,port#. This will possibly identify if you have any issues DHCP name resolution.
Also, you may want to check SQL Sever Configuration Manager.
🙂
August 17, 2017 at 1:51 pm
IP's don't work either and Named Pipes is enabled for SQL Server Configuration manager
August 17, 2017 at 2:12 pm
Using the PowerShell or DOS console, can you use ping to either servers ip-address?
August 17, 2017 at 2:23 pm
all IP's come back with a ping.
August 17, 2017 at 2:42 pm
Any firewall rules that may need to be added by your security group?
August 17, 2017 at 4:18 pm
no.
August 17, 2017 at 8:46 pm
If this is a WSFC, then you should connect to the SQL Cluster Name - the one defined during SQL 2016 setup.
Because you have a named instance, it would by ClusterName\mssqlcluster2,port to connect from SSMS.
If you can't connect like this, look at the Windows firewall on the server. If you're on the same domain as the servers, then try turning off that firewall.
I guess one question should be if the cluster ever worked, meaning allowed connection to it from SSMS, or if it just stopped working. If it never worked, your DBA should be able to help get the initial configuration done.
August 18, 2017 at 9:16 am
JP10 - Thursday, August 17, 2017 1:00 PMHello,How can I make it available to connect to sql using servername\instance name with a SQL 2 node cluster? If I have 2 nodes named server1 and server2 with the instance named mssqlcluster2 and I try to connect in management studio using server1\mssqlcluster2 it does not allow me to connect? Using SQL 2016. The active node is on server1 as well. Appreciate the help.
-
Please read my stairway to AlwaysOn starting at this link
http://www.sqlservercentral.com/stairway/112556/
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply