FAQ > Network > TCP/IP

0 - The operation completed successfully

The error 0 isn't an actual error: The partner disconnected the TCP connection. If !MC5 displays this error in most cases the reason is one of the following two:

1.If the error occurs while establishing a connection to an OFTP2 partner most likely an error occurred on the partners side while establishing the encrypted TLS connection and the partners system disconnects without any error messages (some implementations regard any error message regarding the encrypted connection as potential security risk). The cause for this can be an invalid certificate or no common cipher suites. Validate that your own certificate is present and valid in Settings / OFTP2 / Security. There you can also activate the usage of additional cipher suites. For more information about the settings see Reference / Settings / OFTP/OFTP2 / Security.

2.If the error occurs after successfully connecting to the partner, e.g. after all files have been transmitted, it is highly likely your partner is using an OPFT software using a faulty OFTP protocol implementation. For a protocol conform disconnect both parties have to negotiate disconnect on OFTP level. Only afterwards the TCP connection might be disconnected. Some OFTP/OFTP2 software implementations violate the protocol and disconnect too early. !MC5 displays this as error as the software can't distinguish between an intentional disconnect and a real error.

10053 - Software caused connection abort

This error occurs, if the connection get aborted within the local network, e.g. if the remote host didn't acknowledge sent TCP packets. Usually this means, network traffic gets blocked somewhere between the local computer and the remote host.

A common cause for this error are anti virus software of software firewalls. Turn off all respective software or change it's configuration so, that network traffic is allowed.

If the problem persists, the local network configuration can be the cause. Check for firewalls and their configuration in the local network and configure then so, that connections to the remote host are allowed. You can use the Windows Command Prompt to try to ping the remote host. If the ping fails the remote host is blocked somewhere and using tracert might help you find out where.