> # Connection Handshaking

> If you are experiencing problems during handshaking after the low-level TCP/IP connection has been made to a SequeLink Server, follow these recommendations:

> - You may have specified a TCP/IP port that is not used by a SequeLink service.
> - If the specified port is serviced by a SequeLink Server of an earlier, incompatible version (SequeLink 4.x), the following errors can occur:
> - Error 2200. The client did not receive a reply from the server within the specified time frame. This error occurs only if a connection timeout is specified. See error message 2200 for more details.
> - Error 2300. The server closed the transport connection. See error message 2300 for more details.
> - If the specified port is serviced by a server that is not a SequeLink server, the following errors can occur:
> - Error 2200. The client did not receive a reply from the server within the specified time frame. This error occurs only if a connection timeout is specified. See error message 2200 for more details.
> - Error 2300. The server closed the transport connection. See error message 2300 for more details.
> - Error 2310. The server went down while trying to process the handshake request. The connection was closed. See error message 2310 for more details.
> - Error 2315. The server received the handshake request and returned a non-IIOP reply that the client could not understand. See error message 2315 for more details.
> - You may be connecting with a previous, incompatible version of the SequeLink Client (SequeLink 4.x) to a SequeLink 6.0 Server:
> - The client receives an error message that informs you that the server has closed the connection during the initial handshake.
> - If the specified port is serviced by a SequeLink 6.0 Server, the following errors can occur:
> - Error 2200. The client did not receive a reply from the server within the specified time frame. This error occurs only if a connection timeout is specified. See error message 2200 for more details.
> - Error 2312. A connection was established with the server, but no data was received on the server within the keep alive period. Increase the keep alive setting on the server. See error message 2312 for more details.