We have 3x instances of SQL Server 2012 installed on a single remote server - there's the default MSSQLSERVER instance, then \INSTANCE01 and \INSTANCE02. I can remotely connect to the default MSSQLSERVER instance through SSMS, but I cannot connect to
either of the additional named instances (\INSTANCE01 or \INSTANCE02).
For example, if I try to connect to "sql.domain.com", I can successfully access the default instance on the remote server. If I try to connect to "sql.domain.com\INSTANCE01", I get an error stating"A network-related or instance-specific error occurred while establishing a connection to SQL Server".HOWEVER - if I try to connect to "sql.domain.com\INSTANCE01, 49301" (where 49301 is the TCP Port for the TCP/IP Protocol for this SQL Server instance), I am able to successfully connect.
This leads me to think that there's a communication issue with the SQL Server Browser service running on the remote SQL Server and my workstation.
The following items have been verified:
- SQL Server Browser is running on the remote SQL Server
- Windows Firewall has been disabled on the SQL Server
- TCP Ports 1433, 1434, 1954, and 49301 have been opened up on the remote destination's firewall
- UDP Port 1434 has been opened up on the remote destination's firewall
Thoughts? Did I miss something?