SSLFTPClientServerCompatibility Property

public SecureFTPCompatibilityFlags ServerCompatibility { get; set; }

Public Property ServerCompatibility As SecureFTPCompatibilityFlags
	Get
	Set

public:
property SecureFTPCompatibilityFlags ServerCompatibility {
	SecureFTPCompatibilityFlags get ();
	void set (SecureFTPCompatibilityFlags value);
}

member ServerCompatibility : SecureFTPCompatibilityFlags with get, set

Property Value

The most severe barrier to server compatilibilty is the lack of FTPS support on the server. Most FTP servers can be configured to support FTPS, but some only support SFTP (SSH File Transfer Protocol), which in fact is not FTP in the conventional sense. SFTP is not supported by SSLFTPClient.

The second most common server incompatibility problem is caused by differing level of adherence to the standard for how SSL/TLS sockets should be closed. By default SSLFTPClient 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 then you should first try SecureFTPCompatibilityFlags.DisableDataSSLWaitOnClose and, if the problem still occurs, SecureFTPCompatibilityFlags.SSLDisableDataClosure. If you experience hanging as you close your secure FTP session then you should first try SecureFTPCompatibilityFlags.SSLDisableControlWaitOnClose and, if the problem still occurs, SecureFTPCompatibilityFlags.SSLDisableControlClosure.

Reference