Client Server Pre-Requisite Overview

Before any client installations can take place you should ensure that the appropriate environment is available and that you attend to each of the following items. You should work through the pre-requisite checklist below to ensure that you achieve a successful installation or alternatively you can run the Client Server pre-checker which will do an automatic pre-install check.

System Requirements

  • The minimum operating systems supported is: Windows server 2008 R2 64 bit.
  • SQL Server 2012 (any edition) or higher.
  • Microsoft .NET framework 4.8 or higher must be installed.
  • The server that will be used for the Conductor4SQL Client server must have network connectivity, to communicate with the Central Server.
  • The user performing the installation must be in the sys-admin user role in SQL Server.

Networking

The following ports must be open for proper communication between the Central Server and Client Server:

Required Ports

Port 4321 (TCP) - This port must be open on both the Central Server and Client Server to allow bidirectional communication between them.

SQL Server Ports - The Central Server needs access to the SQL Server instance on the Client Server. The specific ports required depend on your SQL Server configuration:

  • Default SQL Server Instance: Port 1433 (TCP) must be open
  • Named SQL Server Instance:
    • UDP port 1434 (SQL Browser service) must be open
    • The dynamic port assigned to the SQL Server instance must be open
    • If no specific port is configured for the named instance, the entire dynamic port range (49152 - 65535) must be open on the client side

Configuration Example

For example, if your Central Server is 10.0.0.100 and the Client Server is 10.0.0.101, then configure your firewall as follows:

Conductor4SQL Communication:

  • Allow the Client Server to connect to tcp://10.0.0.100:4321
  • Allow the Central Server to connect to tcp://10.0.0.101:4321

SQL Server Access:

  • Default Instance: Open port 1433 (tcp://10.0.0.101:1433) and allow traffic from the Central Server
  • Named Instance: Open UDP port 1434 (udp://10.0.0.101:1434) and either:
    • Configure the SQL Server to use a specific port and open that port, OR
    • Open the entire dynamic port range (49152 - 65535) in your firewall configuration

Note: While DNS names can be used instead of IP addresses for either the Central Server and/or Client Server configuration, if the DNS name does not resolve to an IP address, communication will fail between the two servers in question.

Authentication

  • Mixed-Mode authentication must be enabled in Microsoft SQL Server (if you have configured Conductor4SQL to use SQL Authentication)
  • A username with sys-admin role is required

SQL Server services

If you wish to use Enterprise Data Sync with this client the "SQL Server Agent (MSSQLSERVER)" must be set to start automatically