mb0ne
Here's the situation:
1. I log into a site, succesfully
2. I transfer a file in PASV mode, succesfully
3. SmartFTP issues the next PASV command, SEEMINGLY succesful
4. SmartFTP issues the STOR command, and then waits for the timeout interval to pass and closes the connection.
This problem sub-sides temporarily if I hit the "STOP" button prior to the timeout, and re-initiate the transfer. (PASV is issued again, and the STOR starts transferring) Once that transfer completes, I have to hit stop again and restart the transfer such that the PASV command is issued again otherwise the connection will timeout.
(** See the log snippet below for sample problem. **)
This says to me that something is happening too quickly. (ports aren't available as quickly as SmartFTP thinks they are on the client and/or the server?)
A possible solution to this problem would be a COMMAND TIMEOUT interval which is shorter than the CONNECTION TIMEOUT interval such that a command can be retried X number of times before it is determined as "failed" and proceeds to the next item in the que or fails entirely.
This peticular solution would increase SmartFTP's connection reliability substantially for people who do alot of content transfers to and from quota based ftp sites which require connection persistance via the session que.
--------------------------------------------------
227 Entering Passive Mode (xxx,xxx,200,148,64,16).
Opening data connection to 24.26.200.148 Port: 16400
STOR xxx.xxx
150 Data connection accepted from xxx.xxx.40.177:58741; transfer starting for xxx.xxx
226-Using U/D Ratio 2/1. Current credit 6 MBytes, counting bytes per session.
5485842 bytes transferred. (73.6 KB/s) (00:01:12)
226 File received ok.
SIZE xxx2.xxx
213 5485842
Remote file exist check: 'xxx2.xxx'.
SIZE xxx2.xxx
550 No such file or directory.
PASV
227 Entering Passive Mode (xxx,xxx,200,148,199,172).
Opening data connection to xxx.xxx.200.148 Port: 51116
STOR xxx2.xxx
Timeout (120s).
Active Help: https://www.smartftp.com/support/kb/45
Client closed the connection.
1. I log into a site, succesfully
2. I transfer a file in PASV mode, succesfully
3. SmartFTP issues the next PASV command, SEEMINGLY succesful
4. SmartFTP issues the STOR command, and then waits for the timeout interval to pass and closes the connection.
This problem sub-sides temporarily if I hit the "STOP" button prior to the timeout, and re-initiate the transfer. (PASV is issued again, and the STOR starts transferring) Once that transfer completes, I have to hit stop again and restart the transfer such that the PASV command is issued again otherwise the connection will timeout.
(** See the log snippet below for sample problem. **)
This says to me that something is happening too quickly. (ports aren't available as quickly as SmartFTP thinks they are on the client and/or the server?)
A possible solution to this problem would be a COMMAND TIMEOUT interval which is shorter than the CONNECTION TIMEOUT interval such that a command can be retried X number of times before it is determined as "failed" and proceeds to the next item in the que or fails entirely.
This peticular solution would increase SmartFTP's connection reliability substantially for people who do alot of content transfers to and from quota based ftp sites which require connection persistance via the session que.
--------------------------------------------------
227 Entering Passive Mode (xxx,xxx,200,148,64,16).
Opening data connection to 24.26.200.148 Port: 16400
STOR xxx.xxx
150 Data connection accepted from xxx.xxx.40.177:58741; transfer starting for xxx.xxx
226-Using U/D Ratio 2/1. Current credit 6 MBytes, counting bytes per session.
5485842 bytes transferred. (73.6 KB/s) (00:01:12)
226 File received ok.
SIZE xxx2.xxx
213 5485842
Remote file exist check: 'xxx2.xxx'.
SIZE xxx2.xxx
550 No such file or directory.
PASV
227 Entering Passive Mode (xxx,xxx,200,148,199,172).
Opening data connection to xxx.xxx.200.148 Port: 51116
STOR xxx2.xxx
Timeout (120s).
Active Help: https://www.smartftp.com/support/kb/45
Client closed the connection.