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: WinSCP client with passive FTPs and multiple outgoing NAT GWs is intermittently failing

Before you wrote that the problem is intermittent. But from your last post it looks like you cannot transfer at all via the roundrobinned GWs.
I wanted logs of successful and failed transfer over the same setup (roundrobinned GWs) – assuming the problem is intermittent.
Though if you cannot transfer using other clients either, then it does not seem like WinSCP issue.
bhuffman

Re: WinSCP client with passive FTPs and multiple outgoing NAT GWs is intermittently failing

a.b.c.d is the vendor's FTP server IP.

See attached logs with successful transfer (performed from a different location that has only a single outbound NAT GW) as well as the logs with issues.

I believe we were able to make this work with FileZilla in the past. But I'm unable to reproduce a successful transfer with FileZilla now.

Regards,
Brian
martin

Re: WinSCP client with passive FTPs and multiple outgoing NAT GWs is intermittently failing

Is the a.b.c.d FTP server's IP or NAT GWs' IP? Can you post complete log(s) that show both a successful transfer and a failed one? Do you have the problem with WinSCP only? Or with any FTP client?
bhuffman

WinSCP client with passive FTPs and multiple outgoing NAT GWs is intermittently failing

Hello,
We are using WinSCP to connect to a third-party FTPs (explicit TLS) server. Our connection to the internet is through redundant NAT GWs and the selection of the NAT GW is random (perhaps roundrobin?)

We're getting intermittent failures trying to download files from the third-party server. I'm not sure why, but I'm guessing that the FTPs server sees multiple connections from the different public IPs of the NAT GWs and is refusing the connections.

When it fails, we see this in the logs:
. 2023-02-13 09:52:10.767 Retrieving directory listing...
> 2023-02-13 09:52:10.767 TYPE A
< 2023-02-13 09:52:10.767 200 TYPE is now ASCII
> 2023-02-13 09:52:10.767 PASV
< 2023-02-13 09:52:10.767 227 Entering Passive Mode (a,b,c,d,218,200)
> 2023-02-13 09:52:10.767 MLSD
. 2023-02-13 09:52:10.767 Connecting to a.b.c.d:56008 ...
. 2023-02-13 09:52:10.767 Data connection closed
. 2023-02-13 09:52:10.767 <Empty directory listing>
. 2023-02-13 09:52:25.689 Timeout detected. (control connection)
. 2023-02-13 09:52:25.689 Could not retrieve directory listing
. 2023-02-13 09:52:25.689 Connection was lost, asking what to do.
. 2023-02-13 09:52:25.689 Asking user:
. 2023-02-13 09:52:25.689 **Lost connection.** ("Timeout detected. (control connection)","Could not retrieve directory listing")
< 2023-02-13 09:52:25.689 Script: Lost connection.
< 2023-02-13 09:52:25.689 Script: Timeout detected. (control connection)
< 2023-02-13 09:52:25.689 Could not retrieve directory listing

Are there any settings in WinSCP that would make it handle this situation?

Thank you!
Brian