SQL Server TCP and UDP Ports

Microsoft-SQL-Server-2012

SQL Server is a complex application that can be difficult to allow access to through a firewall. The subsystems and features that Microsoft has added—and continues to add—to SQL Server have significantly increased the network connections that the platform uses. Sometime it’s difficult to figure out which firewall ports to open for each SQL Server feature. To help you, here’s a rundown of commonly used SQL Server network ports as reported by this article by Michael Otey:

  • TCP 1433 – TCP port 1433 is the default port for SQL Server. This port is also the official Internet Assigned Number Authority (IANA) socket number for SQL Server. Client systems use TCP 1433 to connect to the database engine; SQL Server Management Studio (SSMS) uses the port to manage SQL Server instances across the network. You can reconfigure SQL Server to listen on a different port, but 1433 is by far the most common implementation.
  • TCP 1434 – TCP port 1434 is the default port for the Dedicated Admin Connection. You can start the Dedicated Admin Connection through sqlcmd or by typing ADMIN: followed by the server name in the SSMS Connect to Database Engine dialog box.
  • UDP 1434 – UDP port 1434 is used for SQL Server named instances. The SQL Server Browser service listens on this port for incoming connections to a named instance. The service then responds to the client with the TCP port number for the requested named instance.
  • TCP 2383 – TCP port 2383 is the default port for SQL Server Analysis Services.
  • TCP 2382 – TCP port 2382 is used for connection requests to a named instance of Analysis Services. Much like the SQL Server Browser service does for the relational database engine on UDP 1434, the SQL Server Browser listens on TCP 2382 for requests for Analysis Services named instances. Analysis Services then redirects the request to the appropriate port for the named instance.
  • TCP 135 – TCP port 135 has several uses. The Transact-SQL debugger uses the port. TCP 135 is also used to start, stop, and control SQL Server Integration Services, although it is required only if you connect to a remote instance of the service from SSMS.
  • TCP 80 and 443 – TCP ports 80 and 443 are most typically used for report server access. However, they also support URL requests to SQL Server and Analysis Services. TCP 80 is the standard port for HTTP connections that use a URL. TCP 443 is used for HTTPS connections that use secure sockets layer (SSL).

This summary should cover your port needs, but you can find more detailed information about the TCP and UDP ports that SQL Server uses in the Microsoft article “Configure the Windows Firewall to Allow SQL Server Access.”

Advertisements

3 thoughts on “SQL Server TCP and UDP Ports”

  1. I’m bored to death at work so I decided to browse your blog on my iPhone during lunch break. I really like the information you provide here and can’t wait to read more about SQL Server.

    Like

  2. Can I just say what a relief to find someone who actually knows what theyre talking about on the internet. You definitely know how to bring an issue to light and make it important. More people need to read this and understand this side of the story. I cant believe youre not more popular because you definitely have the gift.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s