Common server incompatibility problems are caused by differing level of adherence to the relevant standards. This is particularly applicable to FTPS. For example, the standard dictates how SSL/TLS sockets should be closed. By default SecureFTPConnection will attempt to close sockets in the standard-compliant way. While this is the most secure, it occasionally will cause hanging as it waits for a response from the client which never arrives. The ServerCompatibility property is provided for controlling this behaviour. If you experience hanging when a data-transfer is complete using FTPS then you should first try SSLDisableDataWaitOnClose and, if the problem still occurs, SSLDisableDataClosure. If you experience hanging as you close your FTPS session then you should first try SSLDisableControlWaitOnClose and, if the problem still occurs, SSLDisableControlClosure.

For SFTP, some servers return an error saying the file does not exist after creating it. By default, the client does a permission change after creating the file, which is done to ensure the file permissions are correct. If this error is encountered, try using SSHDisableChmodAfterPut to eliminate the problem.