Creating a firewall rule for Glide access to your Digita/CCH/TaxCalc system

If you wish to use our connectors for Digita, CCH or TaxCalc you shall need to create an exception in your firewalls to allow the Glide integration server to connect to your MS SQL Server. If you follow our guidance this exception shall be limited to both our IP address and also to connections targeting the SQL Server, this is necessary to ensure your firewall remains effective.

There are many different firewall applications available which will all have slightly different interfaces. We have provided guidance below for the Windows firewall, other firewalls will operate on the same basic principles. Where ever possible we have copied content from the Windows SQL Server official documentation which is available in full  here. We shall aim to keep this guide up to date where the windows firewall is updated; however, if in any doubt please refer back to the official Microsoft documentation.

Step 1 -> Determine which port your MS SQL Server engine is configured to listen to for incoming connections.

By default MS SQL Server will use TCP port 1433.

If your database is on a named instance of SQL Server it will by default be using a dynamic port determined by the SQL Server browser service in which case you need to open UDP Port 1434 for the browser service. If you are using a named instance and have set the instance to listed to a fixed port you shall need to know which port you set this to.

Step 2 -> Open the port so that SQL Server can listen for incoming connections.

  1. From the start menu, type wf.msc. Click Windows Firewall with Advanced Security.
  2. In the left pane click Inbound rules.
  3. In the right pane, under Actions click New rule.... New Inbound Rule Wizard opens.
  4. On Rule type, click Port. Click Next.
  5. In the Protocol and Ports dialog box, select TCP. Select Specific local ports, and then type the port number of the instance of the Database Engine, such as 1433 (as determined in step 1 above).
  6. Click Next.
  7. On Action, click Allow the connection.
  8. Profile, include all three profiles. Click Next.
  9. On Name, type a name for the rule. Click Finish.

If you are using dynamic ports (assigned by the SQL Server browser service) then you would need to create an incoming rule specific to the program as opposed to the port, guidance can be found  here. This is in addition to the UDP Port 1434 required for the browser service.  Microsoft recommend configuring the instance to use a fixed port as opposed to this.

Step 3 -> Finally we need to allow the connection from Glide's IP address into the network

  1. Repeat 1-3 from step 2 (above).
  2. For rule type select Custom.
  3. Click All programs. Click Next. (If you limit to a single program here then you may effect other programs looking to use the port and other ports looking to connect to MS SQL Server)
  4. In Protocol type select TCP.
  5. In Local port select Specific port and enter your port number from step 1.
  6. In the Which remote IP addresses section select These IP addresses and add the Glide IP address (this will be supplied on request by Glide)
  7. In the action section select Allow the connection
  8. Profile, include all three profiles. Click Next.
  9. On Name, type a name for the rule. Click Finish.

At this point you should have successfully configured your firewalls to allow an incoming connection from the Glide integration server. If you have not done so already you shall need to create MS SQL Server read-only user credentials for Glide to connect with as well as enabling remote access to the MS SQL Server, both are covered in these articles ( DigitaCCH).

When you are ready contact Glide and we shall test the connection.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us