Ports used by SQL Server





SQL Default Instance


SQL Named Instance




1434 By default, remote connections to the Dedicated Administrator Connection are disabled. Port 1434 for the default instance. Other ports are used for named instances.
SQL Browser


1434 SQL Server Named instances in default configuration.

May be required for SQL Server Browser Service when using named instances. Because in case of named instances TCP port is dynamic determined when the Database Engine starts.

The SQL Server Browser service listens for incoming connections to a named instance and provides the client the TCP port number that corresponds to that named instance. Normally the SQL Server Browser service is started whenever named instances of the Database Engine are used. The SQL Server Browser service does not have to be started if the client is configured to connect to the specific port of the named instance.

SQL Browser   2382  
DTS   3882  
SSAS   2382, 2383, 2393, 2394, 2725  
Cluster Service


Cluster Admin   137  


RPC Dynamic Port   5000-5100  
RDP   3389  
Win 2008 Dynamic Port Range   49152-65535  
Service Broker


4022 There is no default port for SQL Server Service Broker, but this is the conventional configuration used in BOL.
SQL Debugger   RPC  
SSL   443  
HTTP endpoint


  SQL Server instance running over an HTTP endpoint, used for an HTTP connection through a URL. Can be specified when an HTTP endpoint is created. The default is TCP port 80 for CLEAR_PORT traffic and 443 for SSL_PORT traffic.
HTTPS endpoint


443 Default instance running over an HTTPS endpoint. Used for an HTTPS connection through a URL. HTTPS is an HTTP connection that uses secure sockets layer (SSL).
iSCSI   3260, 860 Doesn’t support teamed NIC.
SMB   445  
NetBIOS Session Service   139  
SQL Agent File Copy   135  
SQL Agent File Copy UNC Shares   137, 138, 139, 445  
Transact-SQL debugger


135 The IPsec exception might also be required.

If using Visual Studio, on the Visual Studio host computer, you must also add Devenv.exe to the Exceptions list and open TCP port 135.

If using Management Studio, on the Management Studio host computer, you must also add ssms.exe to the Exceptions list and open TCP port 135. For more information, see Configuring the Transact-SQL Debugger

Database Mirroring


  Though BOL examples use TCP port 7022 there is no default port for Database mirroring. It is very important to avoid interrupting an in-use mirroring endpoint, especially in high-safety mode with automatic failover. Firewall configuration must avoid breaking quorum. For details, see Specifying a Server Network Address (Database Mirroring).


1433 Replication connections to SQL Server using regular Database Engine ports

Web synchronization and FTP/UNC access for replication snapshot require additional ports to be opened on the firewall. To transfer initial data and schema from one location to another, replication can use FTP (TCP port 21), or sync over HTTP (TCP port 80) or File and Print Sharing (TCP port 137,138, or 139).

For sync over HTTP, replication uses the IIS endpoint (ports for which are configurable but is port 80 by default), but the IIS process connects to the backend SQL Server through the standard ports (1433 for the default instance.

During Web synchronization using FTP, the FTP transfer is between IIS and the SQL Server publisher, not between subscriber and IIS.

For details, see Configuring Microsoft Internet Security and Acceleration Server for Microsoft SQL Server 2000 Replication over the Internet.

To get a list of currently operative ones check –

SELECT name, protocol_desc, port, state_desc FROM sys.tcp_endpoints

How to capture network traffic with Network Monitor


Basics of Reading TCP/IP Traces


TCP Ports Needed for Communication to SQL Server Through a Firewall


About learnersstreak

For an insight in my doings, I'm involved in installation & support of SQL Server, performance optimization, virtualization & consolidation. At times into designing databases, more often with trouble shooting. Have automated some of the key tasks using DMO/SMO with VB script & powershell; leading to savings for a few professional tools. As with most DBA's I do all back-up / recovery for my bread & butter, while for high availablity I've implimented mirroring, replication & Log shipping as applicable with or without clusters. Doing SSIS for ETL as dataprovider.
This entry was posted in Uncategorized. Bookmark the permalink.