January 5, 2023 at 5:29 am
I'm on sql 2019 and I want to use static port 50010. I already set up an incoming firewall rule for port 50010 and deleted the default port 1433 firewall rule, however I can still connect to sql server using ssms without specifying the port number 50010 using "home\instance2019" instead of "home\instance2019,50010". What did I miss? I thought I was not supposed to be able to connect without the port number. I restarted the sql service on sql config manager too.
Side note on firewall rule:
Firewall rule Program and Services: C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Ssms.exe
Advanced: Private
January 5, 2023 at 6:04 am
Please use : SQL server configuration manager to adjust your TCP/IP port. Always disable shared memory due to security reasons.
To change the port assignment right-click on the TCP/IP protocol and select Properties using the IP address tab
under SQL Server Network Configuration section.
DBASupport
January 5, 2023 at 6:22 am
Thanks for the reply. I tried writing down all the details in my question but I guess you didn't understand.
I was asking why I can still connect to sql server without using the new port number?
January 5, 2023 at 8:03 am
The SQL Server Browser service will be the item which is allowing you to connect to the named instance on any port as that is what it is designed to do.
This service allows you to connect as either of the two below to successfully reach the instance.
home\instance2019
or
home,50010
If you want to force the connection string to use the port, disable the SQL Server Browser service.
January 5, 2023 at 2:14 pm
As a bit of a sidebar, we disable the SQL Server Browser as part of the security setup because it also kills some of the auto-discovery of machines.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2023 at 7:58 am
@Ant-Green
As you can see sql browser is disabled, static port is enable and I can connect without using the static port. Why I can still connect?
January 6, 2023 at 9:49 am
Are you connecting locally or are you actually crossing the network?
If so you're probably using named pipes rather than TCP IP
But to test TCP you need to be crossing the network, from another machine install SSMS and try to connect to the the instance across the network.
January 6, 2023 at 4:11 pm
I'm on sql 2019 and I want to use static port 50010. I already set up an incoming firewall rule for port 50010 and deleted the default port 1433 firewall rule, however I can still connect to sql server using ssms without specifying the port number 50010 using "home\instance2019" instead of "home\instance2019,50010". What did I miss? I thought I was not supposed to be able to connect without the port number. I restarted the sql service on sql config manager too.
Side note on firewall rule: Firewall rule Program and Services: C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Ssms.exe
Advanced: Private
Quick question, what are the UDP rules for the firewall?
😎
January 9, 2023 at 6:58 am
I hope this site helps resolve your question:
DBASupport
January 9, 2023 at 7:06 am
User datagram protocol (UDP) operates on top of the Internet Protocol (IP) to transmit datagrams over a network. UDP does not require the source and destination to establish a three-way handshake before transmission takes place.
DBASupport
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply