Errors in transfer of file - passive mode with error "Copying files to remote side failed"

Advertisement

sloland
Joined:
Posts:
1
Location:
Norway

Errors in transfer of file - passive mode with error "Copying files to remote side failed"

Hi,

We are using winscp and have created a script for sending files, it works fine - except for one receiver where we in the log file always get this error

WinSCP Version 5.17.7 (Build 10640) (OS 10.0.17763 - Windows Server 2019 Standard)
 
2021-02-24 11:56:30.891 Starting upload of \\some_path\Workdir\24_02_2021_1156.CSV
> 2021-02-24 11:56:30.891 TYPE I
< 2021-02-24 11:56:30.895 200 Type set to I.
> 2021-02-24 11:56:30.895 PASV
< 2021-02-24 11:56:30.899 227 Entering Passive Mode (195,69,26,19,19,152).
> 2021-02-24 11:56:30.900 STOR 24_02_2021_1156.CSV
. 2021-02-24 11:56:30.900 Connecting to some_ip_adress:5016 ...
< 2021-02-24 11:56:30.904 150 Opening BINARY mode data connection.
. 2021-02-24 11:56:46.634 Timeout detected. (data connection)
. 2021-02-24 11:56:46.634 Copying files to remote side failed.
. 2021-02-24 11:56:46.635 Connection was lost, asking what to do.
. 2021-02-24 11:56:46.635 Asking user:
. 2021-02-24 11:56:46.635 **Lost connection.** ("Timeout detected. (data connection)","Copying files to remote side failed.")
< 2021-02-24 11:56:46.635 Script: Lost connection.
< 2021-02-24 11:56:46.636 Script: Timeout detected. (data connection)
open ftpes://username:password@site/ -rawsettings FtpForcePasvIp2=0
The receiver of the files states:
If you look at the client port and server port, you will see that you send all commands through port 21, instead of using a new local port and connecting to the server port on the given port in range

Any ideas how we can achieve this using our script?

Regards
Simen

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
36,025
Location:
Prague, Czechia

Re: Errors in transfer of file - passive mode with error "Copying files to remote side failed"

sloland wrote:

The receiver of the files states:
If you look at the client port and server port, you will see that you send all commands through port 21, instead of using a new local port and connecting to the server port on the given port in range
They are completely wrong. WinSCP does exactly, what they recommend:
. 2021-02-24 11:56:30.900 Connecting to some_ip_adress:5016 ...
You have mostly likely a firewall or NAT problem. Something on the way between you and the server blocks the port 5016. It can be local problem in your network or their problem (or problem somewhere in between, though that's unlikely).
See also https://winscp.net/eng/docs/ftp_modes

Reply with quote

Advertisement

You can post new topics in this forum