Forum Discussion
On-premises Gateway for SQL Server Instance
Hi CeeVee33 , Thank you for reaching out to the Microsoft Community Forum.
Please consider below:
- Ensure TCP/IP is enabled for the SQL Server instance in SQL Server Configuration Manager. Since you mentioned limited access, request your database administrator (DBA) to verify this.
- Test Connectivity from the Gateway Server. the port may be blocked by a firewall or network policy. Also, Ensure SQL Server is configured to allow remote connections.
- Ensure the SQL Server Browser Service is running, as it helps resolve named instances to their correct ports. If this service is stopped, one may not find the instance unless a static port is used.
SQL Server Browser service - Named instances use dynamic ports by default, meaning the port can change. Ask your DBA to find the current port. If possible, configure a static port and ensure the firewall allows inbound traffic on that port.
Configure SQL Server to listen on a specific TCP port - If using a dynamic port, find the actual port using SQL Server Configuration Manager or DBA. Connect using ServerName,PortNumber to bypass SQL Server Browser.
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Hi CeeVee33 is the SQL server instance you're trying to connect to a named instance? If so can you check if TCP/IP is enabled and the SQL Serrver Browser Service on the server is started?
Is there a default instance installed on the SQL Server? If so are you able to connect to that using SSMS from the gateway server?
Hi AndyDDC - Yes, trying to connect to named instance. I do not have enough access to check TCP/IP settings. I can connect to it from my laptop, so I guess Browser Service is on.
There is no default instance installed.
Do I need to get the named instance's port open?
Hi CeeVee33 , Thank you for reaching out to the Microsoft Community Forum.
Please consider below:
- Ensure TCP/IP is enabled for the SQL Server instance in SQL Server Configuration Manager. Since you mentioned limited access, request your database administrator (DBA) to verify this.
- Test Connectivity from the Gateway Server. the port may be blocked by a firewall or network policy. Also, Ensure SQL Server is configured to allow remote connections.
- Ensure the SQL Server Browser Service is running, as it helps resolve named instances to their correct ports. If this service is stopped, one may not find the instance unless a static port is used.
SQL Server Browser service - Named instances use dynamic ports by default, meaning the port can change. Ask your DBA to find the current port. If possible, configure a static port and ensure the firewall allows inbound traffic on that port.
Configure SQL Server to listen on a specific TCP port - If using a dynamic port, find the actual port using SQL Server Configuration Manager or DBA. Connect using ServerName,PortNumber to bypass SQL Server Browser.
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.Hey v-hashadapu - thank you!!
I've asked questions and raised port open ticket. I'll ping here if I can not get it resolved through it.
Thanks
