Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: LOG of succes download with replacement error code 426 to 110

OK, I'll see if more people ask for this hack.
buranded

LOG of succes download with replacement error code 426 to 110

log
buranded

Right, command connection was not losted.

I can repeat this test and logs with my replacement "426" to "110".
martin

Re: log

OK I see. WinSCP does not reconnect, because the FTP connection is actually not closed.
buranded

log

log
martin

Re: Buggy FTP server

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
buranded

Solution

Because our traffic going through our Debian 8 firewall, i can substitute text within TCP-sessions on the fly.
I just used nfqsed to change 426 error code to 110 "comment".

iptables -A INPUT -p tcp -s %BUGGY_FTP_IP% --sport 21 -j NFQUEUE --queue-num 0
/root/nfqsed/nfqsed -s /"426 Cannot RETR. EAccessViolation"/"110 Cannot RETR. EAccessViolation" > /dev/null 2>&1 &

According to:
1. devhub.io/repos/rgerganov-nfqsed
2. github.com/rgerganov/nfqsed
3. sysadmin.ru/articles/izmenyaem-soderzhimoe-tcp-paketov-na-letu

This is a very hacky unusual solution, but now WinSCP reconnects and resuming download quickly and quietly.

PLEASE ADD TO WINSCP ABILITY TO IGNORE 426 ERROR AND AUTORESUMING DOWNLOAD.
buranded

Buggy FTP server

We have one buggy FTP-server and no way to fix it.
Periodically its crashes on doenloading file and sent this error:

Another FTP-clients such as FileZilla reconnects quickly and quietly and resuming download,
but WinWSP stops fatal: