Skip to main content

Testing Connectivity to a Specific TCP Port From the Delphix Engine (KBA1732)




Applicable Delphix Versions

This article applies to the following versions of the Delphix Engine:

Major Release

Sub Releases




The Delphix Engine establishes connections to databases and host environments in a number of ways including JDBC and ssh.

Delphix documentation has a comprehensive list of incoming and outgoing ports that need to be accessible for each of the data platforms supported (search the documentation site for the key words "Network and Connectivity Requirements"). Very often when setting up new environments it is necessary to test connectivity between the Delphix Engine and a listening port on another host. Customers can easily test connectivity to ports listening on the Delphix Engine from their own hosts using various tests (telnet, mconnect, netcat, nc, etc.). Since customers do not have access to operating system commands on the Delphix Engine, connectivity to ports on other hosts can be tested from the Delphix Command Line Interface (CLI).

Troubleshooting Connectivity to a Specific TCP Port

Most frequently this error presents itself when adding a new environment or linking a new dSource with an error message indicating a failure to connect to a specific port:

The TCP/IP connection to the host, port 1433 has failed. Error: "Connection timed out: no further information. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".

It is also possible to see this type of error message in existing environments for various reasons (database is down, firewall or networking changes, etc). 


If you know the listening port number (or it is displayed in the error message), use the "ssh" test from Delphix's Command Line Interface (CLI) to try connecting to the desired port. Unless you are testing connectivity to an actual ssh port, it is perfectly acceptable to use a dummy user name and password.

The "jdbc" test is only compatible with Oracle at the time of this writing.

The "connector" test is used for testing connectivity to the Delphix Connector running on Windows hosts.

$ ssh delphix_admin@
Password:> connectivity connectivity> ls
ssh connectivity> ssh connectivity ssh *> ls 
    type: SSHConnectivity
    address: (required)
        type: KerberosCredential
    port: 22 (*)
    username: (required) connectivity ssh *> set address= connectivity ssh *> set port=12345 connectivity ssh *> set username=dummyuser connectivity ssh *> set credentials.type=PasswordCredential connectivity ssh *> set credentials.password=dummypassword connectivity ssh *> commit
   Error: Unable to SSH to host "".
  Action: Make sure "" is running and is reachable via SSH from the Delphix Engine. 
  Diagnoses: Failure:Could not connect on SSH port 12345 on host "". connectivity ssh *> set port=1433 connectivity ssh *> commit
   Error: Unable to SSH to host "".
  Action: Make sure "" is running and is reachable via SSH from the Delphix Engine. 
  Diagnoses: Success:Reached a server listening on port 1433 on host "" from the Delphix Engine.

The "Diagnoses" indicates whether the Delphix engine can successfully reach the port on the specified host.

If it is unable to successfully reach the port, make sure that there is a process listening on the port by logging in directly to the specified host and issuing the netstat command:

UNIX: netstat -an | grep 5400
tcp        0      0  *                   LISTEN 

Windows: netstat -an | find "1433"
  TCP               LISTENING

If you are able to confirm that the port is listening on the IP (or ANY address but Delphix cannot reach the host, please raise a ticket with your network/firewall team to request connectivity be granted between the two hosts.

Related Articles