Database Connectivity Requirements
This article outlines the connectivity requirements for establishing a connection between databases and the Curiosity Platform in the Windows environment.
1 - Pre-Requisites Verification
Before attempting a connection, ensure that the following pre-requisites are in place:
1.1 Port Configuration
Port 8091 (configurable): Ensure that this port is open for inbound communication, both at the network level and within the Windows Firewall.
Outbound Ports: Ensure that outbound communication is allowed (both at the network level and within the Windows Firewall) to any external applications that the VIP needs to connect to (e.g., databases).
Optional - Ports 8081–8085: Open these ports for inbound communication, both at the network level and within the Windows Firewall. This is only necessary if additional VIP servers are being utilized.
2 - Connectivity Verification via PowerShell
2.1 Verifying Access on Windows Machines
Open Windows PowerShell.
Run the following command:
tnc -p <port_number> <hostname>
Replace
<port_number>
with the relevant port and<hostname>
with the target server's hostname.
Success: If the command executes successfully, you can proceed with connecting the database to the Curiosity Platform.
Failure: If the command fails, proceed with the troubleshooting steps below:
Hostname Resolution: If the command returns a hostname successfully, the issue is likely related to the port configuration. Continue to Section 2.2 - Firewall Troubleshooting.
If the command does not return the hostname, this may indicate a DNS or network issue.
2.2 Troubleshooting Firewall Configuration
If the command in Section 2.1 fails, follow these steps to diagnose and resolve potential firewall issues:
Type "Firewall" in the Windows start menu and open Windows Defender Firewall with Advanced Security.
In the left pane, select Inbound Rules, then click on New Rule.
Choose Port, then specify the port number used in your connection.
Select Allow the connection.
Ensure all connection profiles (Domain, Private, Public) are selected.
Click Finish to save the rule.
Retest the connection in PowerShell by running the same
tnc
command as in Section 2.1.Success: If the command succeeds, the firewall issue has been resolved.
Failure: If the command still fails, it suggests that the issue is related to networking.
Need Assistance?
If you continue to experience issues or need further assistance with connecting your database to the Curiosity Platform, please contact your Curiosity representative.