asked on

SQL Server Management Studio - How to connect to non-default instance on non-default port?

Unfortunately, I have a need to expose SQL to the Internet for one of our SQL servers.

To help with security issues, I've disabled the SA account and have created a PAT in our firewall that will map a non-standard external port to 1433.

I have 2 instance of SQL server on the particular server. Below is an example of my scenario:

PAT in firewall setup for external IP of 8.8.8.8 with a port of 6789 that maps to an internal IP of 192.168.10.1 on port 1433.

The 2 SQL instances are SQL01 and SQL01\MSSQL2008. I am wanting to connect to the SQL01\MSSQL2008 instance.

In SSMS from an external source, I'm entering "8.8.8.8\MSSQL2008,6789" but it's connecting me to the default named SQL01 instance and not the SQL01\MSSQL2008 instance.

Am I missing something? Thanks for any help in advance.

ASKER CERTIFIED SOLUTION

Rezwan Islam

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

sciggs

ASKER

Internally I need 1433 to stay the same as we have multiple apps pointing to the instance. I think the routing is fine, as I can connect to the default instance over 6789 remotely, just not the named instance.

sciggs

ASKER

Nevermind. Doing a bit more research and realizing that 1433 is for the default instance. I think you are correct, if I change the named instance port that should get what I need.

sciggs

ASKER

I was unaware that a named instance uses a dynamic port. The answer helped me to do a bit more research and I was able to change the port for named instance to a static port different from 1433.