Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2014-12-03
4
Medium Priority
?
277 Views
Last Modified: 2014-12-03
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.
0
Comment
Question by:sciggs
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 3

Accepted Solution

by:
Rezwan Islam earned 2000 total points
ID: 40479920
May be configure SQL01\MSSQL2008 on a different Port other than 1433. Set up SNAT firewall rule.
0
 

Author Comment

by:sciggs
ID: 40479931
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.
0
 

Author Comment

by:sciggs
ID: 40479981
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.
0
 

Author Closing Comment

by:sciggs
ID: 40480083
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.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question