Relyence User Guide
Allow Remote TCP Access to SQL Server

Allow Remote TCP Access to SQL Server

In order for Relyence to be able to communicate with a remote SQL Server Instance, SQL Server must be able to accept remote connections and TCP access must be allowed.

Note that all of these actions are to be done on the server where the SQL Server Instance resides.

Allow Remote Connections in SQL Server

  1. If you do not already have SQL Server Management Studio, download and install it from this link.
  2. Open SQL Server Management Studio and connect to your SQL Server Instance.
  3. Right click on your SQL Server Instance in the tree on the left (the top level item) and click Properties.
  4. Click Connections on the left.
  5. If Allow remote connections to this server is unchecked, check this box.
  6. Click OK.

Allow TCP Access to your SQL Server Instance

  1. Click Start and search for SQL Server Configuration Manager.
    1. If you cannot find this application, it will be located on your hard drive at C:\Windows\SysWOW64\SQLServerManagerXX.msc where XX is a two-digit number such as 11, 12, 13, or 14.
  2. Open SQL Server Configuration Manager, expandSQL Server Network Configuration on the left, and select Protocols for <Your SQL Server Instance Name>.
    1. Note that if you are using the Default Instance for SQL Server, your SQL Server Instance Name will be MSSQLSERVER.
  3. In the pane on the right, find TCP/IP.
  4. If TCP/IP is set to Disable:
  1. Right click TCP/IP and select Enable.
  2. On the left pane, click SQL Server Services.
  3. In the pane on the right, find SQL Server (<Your SQL Server Instance Name>).
  4. Right click on this item and select Restart.

Find the Port that SQL Server is Listening On

  1. Open SQL Server Management Studio and connect to your SQL Server Instance.
  2. On the left, expand Management.
  3. Under Management, expand SQL Server Logs.
  4. Double click on the first log that contains the word Current.
  5. In the dialog that now shows:
    1. Click Filter in the toolbar at the top.
    2. For Message contains text, type server is listening on.
    3. Click the Apply filter checkbox.
    4. Click OK.
  6. Find the record similar to Server is listening on ['any' <ipv4> 1433].
    1. In the example listed above, 1433 is the port that SQL Server is listening on. Be sure to note the port that appears for you.

Allow the TCP Port through Windows Firewall

NOTE: This walk through assumes Windows Firewall is controlling network traffic for your system. If your network traffic is controlled by another firewall, be sure to apply these changes in the necessary locations within your organization.

  1. Click Start and search for Windows Firewall.
  2. Open Windows Firewall and click Advanced Settings on the left.
  3. Click Inbound Rules on the left.
  4. Sort the Local Port column and see if there is a rule present for the SQL Server port found in the previous section.
  5. If no rule exists for this port:
    1. Select New Rule on the right.
    2. Select Port and click Next.
    3. Select TCP, select Specified local ports, populate the port number found in the previous step, and click Next.
    4. Select Allow the connection and click Next.
    5. Select Domain, Private, and Public as needed (most likely you will require Domain and Private) and click Next.
    6. Enter a name such as Allow SQL Server for Relyence and click Finish.