Error 1432 with 'errno 0' when try to connect client/server: First things to rule out.

« Go Back


Article Number000020621
EnvironmentProduct: Progress
Version: 9.x
Product: OpenEdge
Version: 10.x,11.x
OS: All supported platforms
Question/Problem Description
Client Server connection fails with error 1432 errno 0.
Client connecting to a database server fails with error 1432  errno 0.
Error 1432 when trying to connect a client using -H hostname -S servicename.
Error 1432 with 'errno 0' when try to connect client/server to the database.
Error 1432 with 'errno 0' and -S is specified with Service Name.
Error 1432 with 'errno 0' using -H hostname in connection parameters.
Steps to Reproduce
Clarifying Information
The database is running multi-user mode.
The database has not been started with the -H parameter.
Cannot connect a client to a remote database server.
Client fails to connect with client/server connection parameters to a database.
The host name is specified with the remote host -H parameter in the connection string is the same as that the database is running on.
The Service Name specified with the -S parameter in the connection string is the same as that used by the Login Broker
Error Message** Could not connect to server for database <DATABASE>, errno <ERRNO>. (1432)
Defect/Enhancement Number
Error 1432 specifically with 'errno 0' means that the client attempting to connect to the database server did not find the named database process listening on the port at the IP address where the database server is supposed to be running. This issue is typically caused by TCP/IP configuration issues, such as:
  • The service name resolves to a different port number in the services file on the client vs that on the server machine.
  • The host name does not resolve to the correct IP address
  • There is something blocking the 3-way handshake
When the 1432 Client-Server connection failure is limited to all local and remote connections 

1. The Database License 

When running Personal Database, 4GL Development, or OpenStudio/Provision licenses, the database server will accept local logins only as all these licenses contain the Personal Database.

Ensure the Database License is either WorkGroup or Enterprise to start the database

When the 1432 Client-Server connection failure is limited to certain remote connections 

1.  Firewall

A firewall between the client machine(s) and the database server will cause error 1432 or eventually "No more servers available". Verify the existence of an active firewall and then the firewall rules: 
  • On the client machine 
  • Between the client machine and the database server 
  • On the database server

2.  TCP/IP configuration issues 

a.  Client/Server Database Startup parameters 
  • -minport, -maxport
Remote servers are known to not function properly when spawned on a port in the configured -minport -maxport range that are reserved in the /etc/services. 

Configure "-minport ; -maxport database startup parameters to use this unreserved range.
  • -PendConnTime
While this parameter will not prevent 1432 errors, it will assist with removing pending connections in order that those clients that can connect still have connection slots available. Refer to Article 000001603, What is the -PendConnTime parameter?    

b.  Differences between the: hostname <> IP <> a NIC 

If the database is started with the -H parameter, remove it from the startup parameters and restart the database or use a test database.

Starting with Progress 9.x:
-H can use the IP address instead of the hostname
-S can use the the port number instead of the service name


The database is started on the host (IP address
There is no -H parameter used to start the database

$   proserve <dbname> -S 5678

Connect the client with the IP Address and Service port number:
$   pro <dbname> -H -S 5678

If the connection succeeds by using the IP address and port Number instead of the hostname and service name, on both the client and server machines:

Check the services files (etc/services) 
Ensure that the servicename that is usually specified with the "-S" parameter maps to the same port number on both machines.

Check the IP address in the DNS configuration matches the hosts files (etc/hosts)

Check the and DNS to ensure that the hostname used with the -H parameter resolves to the correct IP address of the server machine where the database is running, from the client machine. Hostname must be the alias of IP number of the server machine where the database is started.

If the connection fails when by using the IP address and port Number 

Verify that Remote Servers are started when connecting and that those processes (by PID) are visible at the Operating System Level.  Refer to Article

Connect the client directly to a spawned remote server that still has open connection slots available (-Ma)

mpro dbname -S 3000 (where 3000 is the port the remote server is listening on)

If this succeeds the issue is between the database login broker sending the remote port number back to the client, which is then timing out with 1432.

Contact the Network Administrators to assist with analyzing the output of non-Progress utilities to assist in diagnosing where in the 3-way-handshake the connection is failing:

Examples: "tracert", "pathping", ipconfig /renew, ipconfig all, telnet, ftp get filename

Otherwise please open a Technical Support call in your region (via Phone or directly with your SupportLink credentials) providing the appropriate evidence relating to your situation so that we may assist you further.
References to Other Documentation:
Progress Article(s):
000012081, Why define specific minport maxport ranges?  
Last Modified Date2/6/2018 5:16 PM

Did this article resolve your question/issue?


Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025