Svemu - Reparto Sviluppo wrote: >> With method ReceiveAsync the component doesn't try to >> establish a secure data channel/connection. However some server >> may require it, just a guess (haven't read your attached log yet). >> If so, do not use method ReceiveAsync but the low level methods >> instead. > > (the ftp server is only one for all customers).
My guess was not correct. >> Strange, was it possible to post a common FTP log as well? > i don't understant very well, what is the problem to post the log? It takes some time to read and understand the full debug log. The log entries of data socket seem ok and the file should have been received, correct? 18.09.16.171 ! Data Session Connected (Get) 18.09.16.171 033FB3B0 TryToSend 808 18.09.16.171 033FB3B0 TriggerDataSent 808 [..] 18.09.16.218 033FB3B0 *CloseCalled 808 18.09.16.218 033FB3B0 TCustomWSocket.Shutdown 1 808 However the multi-line 226 response looks strange to me: 18.09.16.171 ! Data Session Connected (Get) [..] 18.09.16.203 >|150 Accepted data connection| [..] 18.09.16.218 >|226-Options: -a | [..] 18.09.16.218 >|226 246 matches total| Normal flow would look like this: 18.09.16.171 ! Data Session Connected (Get) [..] 18.09.16.203 >|150 Accepted data connection| [..] 18.09.16.218 >|226 Transfer OK| Afterwards the server actually doesn't perform the bidirectional SSL shutdown correctly but drops the line: 18.09.16.265 033FABF0 Winsock recv( 748, 0x13CED4, 4096, 0) = -1 [336] So you get error "500 Control connection closed - Connection aborted (#10053)" What FTP server is it? -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
