[KBA-01433] How to configure SQL Server to listen on a specific TCP port - Omnicastâ„¢ | Security Center 4.0 - 5.4

series
Omnicastâ„¢ | Security Center 4.0 - 5.4
revised_modified
2016-02-26

[KBA-01433] How to configure SQL Server to listen on a specific TCP port

This article describes how to configure an instance of the SQL Server Database Engine to listen on a specific TCP port using the SQL Server Configuration Manager. If enabled, the default instance of the SQL Server Database Engine listens on TCP port 1433.

Summary

In some situations, clients are unable to communicate with SQL Server on the current listening port because another application or service has control of that TCP port.

NOTE: Although TCP port 1433 is reserved for SQL Server, Winsock applications use random ports greater than 1024, and can bind to 1433.

More Information

To set SQL Server to listen on a specific port:

  1. On the machine where SQL server is running click Start > SQL Server Configuration Manager
  2. Under SQL Server Network Configuration, select the SQL Server instance to configure. When selected, you will see the TCP/IP status as Enabled or Disabled on the right side of the SQL Server Configuration Manager.
  3. If the TCP/IP remote connection is disabled, enable it:
    1. Double-click TCP/IP to open the TCP/IP Properties.

    2. Under the Protocol tab, set Enabled to Yes.

    3. Under the IP Addresses tab, expand the IP2 section and make the following changes:
      • Ensure the correct IP address is listed.
      • Set Enabled to Yes.
      • Clear any TCP Dynamic Ports.
  4. Still under the IP Addresses tab, expand the IP All section and set TCP Port as required. SQL Server commonly runs on port 1433, but this configuration can be set as required.

  5. Click OK.
  6. Update Windows Firewall to open the SQL Server TCP port for inbound traffic.
  7. Restart all SQL services.