Opened 8 years ago

Closed 6 years ago

#7975 closed Bug report (outdated)

intermittent issue - Connection closed; transfer aborted.

Reported by: attila galuska Owned by:
Priority: normal Component: FileZilla Server
Keywords: 426 Connection closed, transfer aborted Cc: attila.galuska@…
Component version: Operating system type: Windows
Operating system version: Win2003 Enterprise SP2

Description

We have an intermittent issue on our FileZilla Server version 0.9.40.

In about 3% of the transfers we have this error:
"426 Connection closed; transfer aborted." after the "150 Opening data channel for file transfer.".
I included the FZ log and he mainframe log as well.

Our client (a z/OS mainframe) trasfers files to our FZ server running on a Win2003 server.
In the FZ logs and in the mainframe logs (both included on the bottom) I can see that the authentication negotiation succeeded and control connection is established.
We are using ACTIVE-MODE (client sends us the PORT cmd)and I made sure that the certificate chain is in place.

FileZilla log:
Connected, sending welcome message...
220 FileZilla Server version 0.9.40 beta Welcome to our-FTPS-Server on 123.123.123.123
AUTH TLS
234 Using authentication type TLS
SSL connection established
PBSZ 0
200 PBSZ=0
PROT P
200 Protection level set to P
USER xyz
331 Password required for xyz
PASS
230 Logged on
SITE FIXrecfm 80 LRECL=80 RECFM=FB BLKSIZE=27920
504 Command not implemented for that parameter
PORT 161,128,157,7,67,209
200 Port command successful
STOR file.TXT
150 Opening data channel for file transfer.
426 Connection closed; transfer aborted.
QUIT
221 Goodbye
disconnected.

Mainframe Log:
.EZA1736I FTP -d -x -r TLS (EXIT
...
.EZA1450I IBM FTP CS V1R12
.EZA1466I FTP: using TCPIP
.EZA1772I FTP: EXIT has been set.
.EZA1456I Connect to ?
.EZA1736I 123.123.123.123
...
.EZA1554I Connecting to: 123.123.123.123 port: 21.
.220 FileZilla Server version 0.9.40 beta Welcome to CCC FTPS Server on 123.123.123.123
.GU4945 ftpSetApplData: entered
.EZA1701I >>> AUTH TLS
.234 Using authentication type TLS
.EZA2895I Authentication negotiation succeeded
.EZA1701I >>> PBSZ 0
.200 PBSZ=0
.EZA1701I >>> PROT P
.200 Protection level set to P
.EZA2906I Data connection protection is private
.GU4945 ftpSetApplData: entered
.CZ1465 rnetrc:(2) file DD:NETRC does not exist
.EZA1459I NAME (123.123.123.123:DPPBCF0):
.EZA1701I >>> USER xyz
.331 Password required for xyz
.EZA1701I >>> PASS
.230 Logged on
...
...
.EZA1701I >>> STOR file.TXT
.150 Opening data channel for file transfer.
.SC1831 accDsConnection: entered
.GU4945 ftpSetApplData: entered
.FU0388 protDataConn: secure_socket_init() failed with rc = 406 (Error while reading or writing data)
.FC1354 endSecureConn: gsk_secure_socket_shutdown() returned 5 - Handle is in the incorrect state
.CP3671 SETCEC code = 17
.EZA2870I TLS security mechanism negotiation failed - data connection closed
.MF0732 seq_close_file: file closed
.GV0170 releaseFile: release ddname - SYS00034
.SC2632 dataClose: entered
.426 Connection closed; transfer aborted.
.CX0373 main: RC=-0001 cmd_in_progress=27
.CX0376 main: last_reply= 426 err=17
.PC0915 setClientRC: entered
.PC0985 setClientRC: std_rc=27426, rc_type=STD, rc=27426
.EZA1735I Std Return Code = 27426, Error Code = 00017
.CZ1196 ftpQuit: entered
.CZ1268 ftpClose: entered
...
...

Any help would be greatly appreciated.
Thanks,
Attila

Change History (2)

comment:1 by Tim Kosse, 6 years ago

Status: newmoreinfo

There have been a number of FTP over TLS fixes. Do you still experience this issue in the latest version of FileZilla Server?

comment:2 by Alexander Schuch, 6 years ago

Resolution: outdated
Status: moreinfoclosed

No reply for more than 28 days.

Note: See TracTickets for help on using tickets.