FileZilla Forums

Hello,

I have noticed this error in my logs

(001667) 2/4/2019 4:45:24 AM - user_login (129.76.82.100)> 229 Entering Extended Passive Mode (|||52009|)
(001667) 2/4/2019 4:48:34 AM - user_login (129.76.82.100)> STOR filename.txt
(001667) 2/4/2019 4:48:34 AM - user_login (129.76.82.100)> 425 Can't open data connection for transfer of "\filename.txt"

Is this a client or server issue?

Thanks

Rob

That's weird, where is that backslash coming from?

The / appears on all the transfers I have checked. Here is an example of a successful transfer. This is the log snipet right after the failure.

Is there a setting on the Filezilla side to tell the client to re-transmit after an error?

(001667) 2/4/2019 4:48:34 AM - user_login (129.76.82.100)> EPSV
(001667) 2/4/2019 4:48:34 AM - user_login (129.76.82.100)> 229 Entering Extended Passive Mode (|||52270|)
(001667) 2/4/2019 4:48:34 AM - user_login (129.76.82.100)> STOR textfile.txt
(001667) 2/4/2019 4:48:34 AM - user_login (129.76.82.100)> 150 Opening data channel for file upload to server of "/textfile.txt"
(001667) 2/4/2019 4:48:36 AM - user_login (129.76.82.100)> 226 Successfully transferred "/textfile.txt"

Now it's a forward slash in the second log. Did you manually type in the first log or where else does the backslash come from?

Sorry, manually typed the first log entry, so they are all forward slashes /

I see. Details are incredibly important to diagnose issues. Modified logs can lead to wild goose chases. Please always post complete and unmodified logs obtained via copy&paste.

Could some of these ports be blocked by a firewall or not being forwarded in some NAT router the server sits behind?

After another error this morning I spoke with my firewall/networking person.

log sniped (copied)
(003862) 2/13/2019 4:14:10 AM - ftpuser (129.76.82.100)> 230 Logged on
(003862) 2/13/2019 4:14:10 AM - ftpuser (129.76.82.100)> SYST
(003862) 2/13/2019 4:14:10 AM - ftpuser (129.76.82.100)> 215 UNIX emulated by FileZilla
(003862) 2/13/2019 4:14:10 AM - ftpuser (129.76.82.100)> TYPE I
(003862) 2/13/2019 4:14:10 AM - ftpuser (129.76.82.100)> 200 Type set to I
(003862) 2/13/2019 4:14:11 AM - ftpuser (129.76.82.100)> SITE NAMEFMT 1
(003862) 2/13/2019 4:14:11 AM - ftpuser (129.76.82.100)> 200 Now using naming format "1"
(003862) 2/13/2019 4:14:11 AM - ftpuser (129.76.82.100)> EPSV
(003862) 2/13/2019 4:14:11 AM - ftpuser (129.76.82.100)> 229 Entering Extended Passive Mode (|||52356|)
(003862) 2/13/2019 4:14:22 AM - ftpuser (129.76.82.100)> STOR filename.txt
(003862) 2/13/2019 4:14:23 AM - ftpuser (129.76.82.100)> 425 Can't open data connection for transfer of "/filename.txt"
(003862) 2/13/2019 4:14:24 AM - ftpuser (129.76.82.100)> EPSV
(003862) 2/13/2019 4:14:24 AM - ftpuser (129.76.82.100)> 229 Entering Extended Passive Mode (|||52190|)
(003862) 2/13/2019 4:14:27 AM - ftpuser (129.76.82.100)> STOR filename1.txt
(003862) 2/13/2019 4:14:27 AM - ftpuser (129.76.82.100)> 150 Opening data channel for file upload to server of "/filename1.txt"

We don't have anything blocking access, he did see this in his log.

action = allowed
app = ftp
client_ip = 129.76.82.100
dest_ip = 10.16.136.130
dest_port = 52356
session_end_reason = tcp-rst-from-server
transport = tcp

(003862) 2/13/2019 4:14:11 AM - ftpuser (129.76.82.100)> SITE NAMEFMT 1

That is unusual. May I ask which client software you are using? I reckon something on Ye Olde IBM mainframe.

(003862) 2/13/2019 4:14:11 AM - ftpuser (129.76.82.100)> EPSV
(003862) 2/13/2019 4:14:11 AM - ftpuser (129.76.82.100)> 229 Entering Extended Passive Mode (|||52356|)
(003862) 2/13/2019 4:14:22 AM - ftpuser (129.76.82.100)> STOR filename.txt
(003862) 2/13/2019 4:14:23 AM - ftpuser (129.76.82.100)> 425 Can't open data connection for transfer of "/filename.txt"

This is odd, there should be almost no delay between these commands, and here it's over 10 seconds. Could you please use a network sniffer such as Wireshark to see what happens with the data connection?