Windows Firewall Configuration for SQL Applications in CS Professional Suite

Show expandable text

This article provides basic instructions on how to add exceptions for SQL-related processes to Microsoft Windows Firewall to prevent issues operating CS Professional Suite SQL-based applications. Additional questions about setting firewall exceptions should be directed to your firm's IT professional. You can also refer to the Firewall guidelines for CS Professional Suite applications for more information.

Creating rules

  1. Open the Control Panel.
  2. Click Administrative Tools. The path there depends on whether Control Panel is in Category, Small icons or Large icons view.
    • In Category view, choose System and Security and then Administrative tools.
    • In Small or Large icon view, choose Administrative tools.
  3. Open Windows Firewall with Advanced Security.
  4. Click Inbound Rules on the left side of the window and then New Rule on the right side.
  5. In the New Inbound Rule Wizard dialog, use the following information to create a port exception.
    1. Select  Port
    2. Select  TCP and specify port  1433
    3. Allow the connection
    4. Choose all three profiles (Domain, Private & Public)
    5. Name the rule "SQL Server TCP 1433"
  6. Click New Rule again and use the following information to create another port exception.
    1. Select Port
    2. Select UDP and specify port 1434
    3. Allow the connection
    4. Choose all three profiles (Domain, Private & Public)
    5. Name the rule "SQL Server UDP 1434"
  7. Click New Rule again and use the following information to create a program exception.
    1. Select Program
    2. Click Browse to select sqlservr.exe at the applicable location. Show me.
      • If SQL Server is installed by a CS Professional Suite application: C:\Program Files\Microsoft SQL Server\MSSQL[SQLVersion]<INSTANCE_NAME>\MSSQL\Binn\
      • If a 32-bit version of SQL Server is installed on a 64-bit operating system: C:\Program Files (x86)\Microsoft SQL Server\MSSQL[SQLVersion]<INSTANCE_NAME>\MSSQL\Binn\
      • If a 64-bit version of SQL Server is installed on a 64-bit operating system: C:\Program Files\Microsoft SQL Server\MSSQL[SQLVersion]<INSTANCE_NAME>\MSSQL\Binn\
      • If a 32-bit version of SQL Server is installed on a 32-bit operating system: C:\Program Files\Microsoft SQL Server\MSSQL[SQLVersion]<INSTANCE_NAME>\MSSQL\Binn\

        Note: Where <INSTANCE_NAME> is the name of your SQL instance, and [SQLVersion] refers to the following:

      • 11 = SQL Server 2012
      • 12 = SQL Server 2014
      • 13 = SQL Server 2016
      • 14 = SQL Server 2017
    3. Allow the connection
    4. Choose all three profiles (Domain, Private & Public)
    5. Name the rule sqlservr.exe
  8. Click New Rule again and use the following information to create another program exception.
    1. Select  Program
    2. Click  Browse to select sqlbrowser.exe at this location: C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe.  If you're working on a 64-bit computer, the sqlbrowser.exe will be in C:\Program Files (x86).
    3. Allow the connection
    4. Choose all three profiles (Domain, Private & Public)
    5. Name the rule sqlbrowser.exe

If connecting a named instance through a firewall, you may need to configure the Database engine to listen to a specific port, so that port can be opened in the firewall. For more information, refer to the Microsoft topic: Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager)External link(What's this?).

This icon appears alongside links to resources that are not developed or maintained by Thomson Reuters. We provide access to these resources for your convenience, but we are not responsible for their accuracy. If you need additional assistance, please consult your qualified technician and/or the vendor who developed the resource.

Related articles SQL Server best practices for CS Professional Suite applications

Was this article helpful?

Thank you for the feedback!

Internal only

If a firm asks for help beyond the steps listed in this article, this is beyond the scope of support. See Internal: Overcoming objections during systems troubleshooting for positioning on the scope of support.

Users can be directed to this external article regarding scope of support, Contacting our Support team.