If "no certificate request" is set in the server, then the connection will not be authenticated by the certificate, only by password, this will degrade the security.
Also if "protect data channel" is disabled, the data channel is communicated in plain data. So someone can watch what is transferring one the network.
The problem may be because that the certificate published by the FTP server is not acceptable by Windows.
FTPES connection error
Re: FTPES connection error
I have self-signed and assigned it to the be used in the FTP server with the same results. I am really pushing hard on my hosting company to have them find the fix on the FTP server, but they are starting to push back on the software and not the server. Their stance is that other FTP clients like filezilla work fine. see log below.
Status: Resolving address of ftp.MyDomain.com
Status: Connecting to 8.8.8.8:21...
Status: Connection established, waiting for welcome message...
Response: 220 ProFTPD 1.3.3e Server (ProFTPD) [8.8.8.8]
Command: AUTH TLS
Response: 234 AUTH TLS successful
Status: Initializing TLS...
Status: Verifying certificate...
Command: USER MyUSERNAME
Status: TLS/SSL connection established.
Response: 331 Password required for MyUSERNAME
Command: PASS ****************************************
Response: 230 User MyUSERNAME logged in
Command: SYST
Response: 215 UNIX Type: L8
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: MFMT
Response: TVFS
Response: UTF8
Response: AUTH TLS
Response: MFF modify;UNIX.group;UNIX.mode;
Response: MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.mode*;UNIX.owner*;
Response: LANG ja-JP;bg-BG;en-US*;it-IT;zh-TW;fr-FR;ko-KR;ru-RU;zh-CN
Response: PBSZ
Response: PROT
Response: REST STREAM
Response: SIZE
Response: 211 End
Command: OPTS UTF8 ON
Response: 200 UTF8 set to on
Command: PBSZ 0
Response: 200 PBSZ 0 successful
Command: PROT P
Response: 200 Protection set to Private
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is the current directory
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (8,8,8,8,144,227).
Command: MLSD
Response: 150 Opening ASCII mode data connection for MLSD
Response: 226 Transfer complete
Status: Directory listing successful
Status: Resolving address of ftp.MyDomain.com
Status: Connecting to 8.8.8.8:21...
Status: Connection established, waiting for welcome message...
Response: 220 ProFTPD 1.3.3e Server (ProFTPD) [8.8.8.8]
Command: AUTH TLS
Response: 234 AUTH TLS successful
Status: Initializing TLS...
Status: Verifying certificate...
Command: USER MyUSERNAME
Status: TLS/SSL connection established.
Response: 331 Password required for MyUSERNAME
Command: PASS ****************************************
Response: 230 User MyUSERNAME logged in
Command: SYST
Response: 215 UNIX Type: L8
Command: FEAT
Response: 211-Features:
Response: MDTM
Response: MFMT
Response: TVFS
Response: UTF8
Response: AUTH TLS
Response: MFF modify;UNIX.group;UNIX.mode;
Response: MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.mode*;UNIX.owner*;
Response: LANG ja-JP;bg-BG;en-US*;it-IT;zh-TW;fr-FR;ko-KR;ru-RU;zh-CN
Response: PBSZ
Response: PROT
Response: REST STREAM
Response: SIZE
Response: 211 End
Command: OPTS UTF8 ON
Response: 200 UTF8 set to on
Command: PBSZ 0
Response: 200 PBSZ 0 successful
Command: PROT P
Response: 200 Protection set to Private
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is the current directory
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (8,8,8,8,144,227).
Command: MLSD
Response: 150 Opening ASCII mode data connection for MLSD
Response: 226 Transfer complete
Status: Directory listing successful
Re: FTPES connection error
Have you considered this any further? I would like to see this working soon and need further assistance. Thanks again for your assistance.
Re: FTPES connection error
Please work with "TLSOptions NoCertRequest" (Password only) for some months, we'll implement another FTP module by using OpenSSL in BestSync 2013. Then BestSync should be able to work like FileZilla etc application that is using OpenSSL.