Resolution:
"CONN (accept) failed to open {end of file}" implies that the server that generates this message (1) successfully
accepted the underlying socket connection and (2) the connection attempt was terminated by the processes that was attempting to get a connection before the TipcConn level handshake completed. The key here is that it was the process that was trying to connect, not the RTserver, that terminated the connection attempt.  You may be able to resolve this by setting the undocumented option _Conn_Init_Timeout in the client. The default value for this option is 30 seconds, try setting it to 45 seconds and see if that resolves the problem.  This error can be the result of a heavily loaded network, network latency (such as across a WAN), or in some cases because the RTserver is busy with other tasks and did not respond to the client's handshake request quickly enough.

What does it mean when RTserver reports "CONN (accept) failed to open {end of file}"?