Typically SQL Server uses TCP port 1443, which may be blocked by a firewall. There may be other ports that need to be opened, depending on how SQL Server is configured.
For more information see
https://docs.microsoft.com/en-us/sql/sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access?view=sql-server-2017 If the correct ports have been opened in the firewall but there is still connection issue, then turn off the firewall or configure the firewall to "allow all traffic" temporarily.Then test the DSN connection again to see if it is successful. If it works, then the firewall is blocking a necessary port/protocol to connect to SQL Server. If the DSN connection fails, the firewall is not the cause of the connection issue.
If the firewall is the issue, turn the firewall on again and enable logging to determine which port is blocked/dropped. Then open the port in the firewall by making a rule. The following example is with Windows Firewall.
1. Open the Windows Firewall Advanced Settings, click on Properties. Select the correct tab and select the Customize button under the Logging section
2. Select "Yes" next to Logged Dropped Packets, then click OK and OK again:
3. Launch the Statistica client (or walk through the System DSN configuration again) to reproduce the error.
4. Check the Firewall log file to check which packet has been dropped. Below, the field for "src-ip" is the workstation/client IP address, which is 10.9.102.192 and the "dst-port" is the port which was blocked, which is 56547:
5. Create a rule to open the blocked port (see
https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-firewall/create-an-inbound-port-rule):
Now the DSN configuration walk through will proceed and Statistica will work without any issues.
Related knowledge article:
https://support.tibco.com/s/article/How-to-resolve-SQL-Server-error-when-setting-up-System-DSN-ODBC-Connection-for-TIBCO-Statistica-Database