Transfer channel can't be opened

Need help with FileZilla Server? Something does not work as expected? In this forum you may find an answer.

Moderator: Project members

Post Reply
Message
Author
crashc2121
504 Command not implemented
Posts: 8
Joined: 2017-05-09 17:33

Transfer channel can't be opened

#1 Post by crashc2121 » 2019-03-04 20:59

I am trying to get a new client onto the server. he keeps getting the message:
transfer channel can't be opened. no connection could be made

my settings and config havent changed and they work for 10 other clients

Is there someone else I need to do?

User avatar
botg
Site Admin
Posts: 32213
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: Transfer channel can't be opened

#2 Post by botg » 2019-03-05 08:32

Please post a complete log of an attempt, ideally both server-side and client-side logs.

crashc2121
504 Command not implemented
Posts: 8
Joined: 2017-05-09 17:33

Re: Transfer channel can't be opened

#3 Post by crashc2121 » 2019-04-05 13:04

so i have ten clients able to get in but one still can't and hes getting this

this is his log:

COMMAND PWD
RESPONSE 257 "/" IS CURRENT DIRECTORY
COMMAND TYPE l
RESPONSE 200 TYPE SET TO l
COMMAND PASV
RESPONSE 227 ENTERING PASSIVE MODE (47,19,28,78,207,11)
COMMAND MLSD
ERROR THE DATA CONNECTION CANNOT BE ESTABLISHED: ECONNREFUSED - CONNECTOON REFUSED BY SERVER
RESPONSE 425 CAN'T OPEN DATA CONNECTION
ERROR FAILED TO RETRIEVE DIRECTORY LISTING
STATUS CONNECTION CLOSED BY SERVER

crashc2121
504 Command not implemented
Posts: 8
Joined: 2017-05-09 17:33

Re: Transfer channel can't be opened

#4 Post by crashc2121 » 2019-04-05 19:34

TO ADD ON I HAD THEM TRY AGAIN
HERES THE LOG:

001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> 230 Logged on
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> SYST
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> 215 UNIX emulated by FileZilla
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> FEAT
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> 211-Features:
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> MDTM
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> REST STREAM
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> SIZE
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> MLST type*;size*;modify*;
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> MLSD
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> AUTH SSL
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> AUTH TLS
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> UTF8
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> CLNT
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> MFMT
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> 211 End
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> PBSZ 0
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> 200 PBSZ=0
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> PROT P
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> 200 Protection level set to P
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> PWD
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> 257 "/" is current directory.
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> TYPE I
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> 200 Type set to I
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> PASV
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> 227 Entering Passive Mode (47,19,28,78,207,30)
(001038)4/5/2019 15:30:54 PM - ftpcal (208.78.25.221)> MLSD
(001038)4/5/2019 15:31:05 PM - ftpcal (208.78.25.221)> 425 Can't open data connection.

User avatar
botg
Site Admin
Posts: 32213
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: Transfer channel can't be opened

#5 Post by botg » 2019-04-06 19:16

Good chance that a firewall or NAT router is interfering with the connection. Please test your server on https://ftptest.net/

crashc2121
504 Command not implemented
Posts: 8
Joined: 2017-05-09 17:33

Re: Transfer channel can't be opened

#6 Post by crashc2121 » 2019-04-08 13:12

i have ten other clients able to get in and out. just this one can't get in

Post Reply