StarQuest Technical Documents

Error: Connection refused by remote host or Connect Host <hostname> not found

Last Update: 26 June 2008
Product: StarSQL
Version: 5.x
Article ID: SQV00SQ029


The Host Name specified in the StarSQL data source setup does not match the hostname of the system you are trying to connect to or TCP/IP is not started on the host. This is an error message returned from the host when you try to connect via direct TCP/IP.


  1. Can you ping the host by name or IP address? At a command prompt type "ping <servername>"

If an IP address appears, then there is nothing wrong with the connection to the server. If you do not get an IP address, then you cannot connect with the server. Consult your Systems or Network Administrator.

Note: You can also try using the fully qualified name of the computer (i.e. or the IP address instead of the hostname in the StarSQL data source configuration.

  1. Does your host support direct TCP/IP connections?
    • On an AS/400, version v4r2 or later allows direct TCP/IP.
    • On a mainframe, DB2 for OS/390 version 5.1 or later allows direct TCP/IP.
    • On Windows/Unix/Linux, UDB version 5.1 or later allows direct TCP/IP.
    • On DB2 for VM/VSE, version 6.0 or later allows direct TCP/IP.
  1. Are TCP/IP services started on your host and do you have the correct port number?

Consult your Systems or Network Administrator for the correct TCP/IP port number and to verify that TCP/IP services are started. For directions on how to verify or turn on TCP/IP access on an iSeries host, refer to the technical document entitled How to Enable DRDA over TCP/IP for OS/400 V4R2 and later.

  1. (StarPipes users only) Is StarPipes running on the gateway server?

Verify that the StarPipes service (Windows) or StarPipes job (iSeries) is running and listening on the port used in the StarSQL data source configuration.



The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.