SQLServer2008 Port and Firewall settings

One, Microsoft SQL Server 2008r2 Database settings

1. Start the + program =>microsoft SQL Server 2008r2=> Configuration tool =>sql Server Configuration Manager

2. SQL Server Network Configuration =>sqlexpress Protocol =>TCP/IP protocol, set to Enabled.

3. Right-click TCP/IP properties and locate the option for the static IP address of the database installation server, this example is IP4, remove the TCP dynamic port, change the TCP port to 1433 (the default), and the active and enabled instead.

4. Remove the TCP dynamic port from the Ipall and change the TCP port to 1433.

5. Then, restart the SQL Server (SQLEXPRESS) service in the SQL Server service.

Second, configure Windows firewall on the database server

1. Log on to the server that has SQL Server installed.
2. Click Start, Administrative Tools, Windows Firewall with Advanced security.
3. Right-click Inbound Rules, and then click New Rule.
4. In the New Inbound Rule wizard dialog box, on the Rule Type page, click Ports, and then click Next.
5. On the Protocols and Ports page, click TCP, click Specific local ports, type 1433, and then click Next.
6. On the Operations page, click Allow Connections, and then click Next.
7. On the Configuration Files page, do all of the following:

• Select the Domain check box.
• Select the Private check box.
• Select the Public check box.

1. Click Next.
2. On the Name page, click Name, and then type a meaningful name for the new inbound rule.
3. Optionally, click Description (Optional), and then type a description for the inbound rule.
4. Click Finish.
5. When you use a named instance, the SQL Server Browser service may require UDP port 1434, which needs to be turned on.

Third, the port used by SQL Server

The following tables can help you determine the ports that SQL Server uses.

Ports used by the database engine

The following table lists the ports that are frequently used by the database engine.

Application Scenarios	Port	Comments
Default instance of SQL Server running over TCP	TCP Port 1433	This is the most common port allowed through the firewall. It applies to routine connections between the default database engine installation or a named instance that is the only running instance on the computer. (named instances have special considerations.) See dynamic ports later in this topic.)
Named instance of SQL Server with default configuration	This TCP port is a dynamic port that is determined when the database engine is started.	See the description in the Dynamic ports section below. When you use a named instance, the SQL Server Browser service may require UDP port 1434.
A named instance of SQL Server configured to use a fixed port	The port number configured by the administrator.	See the description in the Dynamic ports section below.
Dedicated Administrator Connection	For the default instance, TCP port 1434. Other ports are used for naming instances. See the error log for the port number.	By default, remote connections to a dedicated administrator connection (DAC) are not enabled. To enable a remote DAC, use the surface Area configuration facet. For more information, see Understanding surface Area Configurator.
SQL Server Browser Services	UDP Port 1434	The SQL Server Browser service listens for incoming connections to a named instance and provides the client with the TCP port number that corresponds to this named instance. Typically, the SQL Server Browser service is started whenever a named instance of the database engine is used. If the client is configured to connect to a specific port on a named instance, you do not have to start the SQL Server Browser service.
An instance of SQL Server running through the HTTP endpoint.	Can be specified when an HTTP endpoint is created. For clear_port communication, the default port is TCP port 80, and for Ssl_port traffic, the default port is 443.	An HTTP connection to be implemented via a URL.
The default instance of SQL Server that runs through the HTTPS endpoint.	TCP Port 443	Used for HTTPS connections that are implemented via URLs. HTTPS is an HTTP connection that uses Secure Sockets Layer (SSL).
Service Broker	TCP Port 4022. To verify the ports that are used, execute the following query: SELECT name, Protocol_desc, Port, State_desc From sys.tcp_endpoints WHERE type_desc = ' Service_broker '	For SQL Serverservice Broker, there is no default port, but this is the general configuration used in the Books Online sample.
Database mirroring	Administrator selected ports. To determine this port, execute the following query: SELECT name, Protocol_desc, Port, State_desc from sys.tcp_endpoints WHERE type_desc = ' Database_mirroring '	There is no default port for database mirroring, but the Books Online sample uses TCP port 7022. It is important to avoid interrupting the mirroring endpoint in use, especially in high-safety mode with automatic failover. Firewall configuration must avoid breaking the quorum. For more information, see Specifying Server network addresses (database mirroring).
Copy	with SQL Server The replication connection uses a typical general database engine port (TCP port 1433 for the default instance) Replication Snapshot Web synchronization and Ftp/unc access requires that additional ports be opened on the firewall. To transfer the initial data and schema from one location to another, replication can use FTP (TCP port 21) or synchronization over HTTP (TCP port 80) or File and print sharing (TCP port 137, 138, or 139).	for synchronization over HTTP, replication uses the IIS endpoint (its port is configurable, but port 80 by default), but the IIS process passes through the standard port (for the default instance 1433) connect to the back-end SQL Server. During Web synchronization using FTP, the FTP transfer is performed between IIS and the SQL Server Publisher, not between the Subscriber and IIS. For more information, see Configuring Microsoft Internet Security and Acceleration Server for Microsoft SQL Server Replication Over the Internet (configure Microsoft Internet Security and Acceleration Server for Microsoft SQL Server 2000 replication over the Internet).
Transact-SQL Debugger	TCP Port 135 See Special considerations for Port 135 IPsec exceptions may also be required.	If you are using Visual Studio, you must also add Devenv.exe to the Exceptions list and open TCP port 135 on the Visual Studio host computer. If you use Management Studio, you must also add Ssms.exe to the Exceptions list and open TCP port 135 on the Management studio host computer. For more information, see Configure and start the Transact-SQL debugger.

SQLServer2008 Port and Firewall settings