FTP to supportftp.broadcom.com gets RC=2028 EZA1721W/EZA1735I Error Code = 00009
search cancel

FTP to supportftp.broadcom.com gets RC=2028 EZA1721W/EZA1735I Error Code = 00009

book

Article ID: 405773

calendar_today

Updated On:

Products

ACF2 - z/OS ACF2 ACF2 - DB2 Option ACF2 - MISC

Issue/Introduction

Client FTPing to supportftp.broadcom.com port 21, job ends with RC=2028 and   EZA1721W/EZA1735I

 EZA1736I FTP supportftp.broadcom.com 21 (EXIT
 EZY2640I Using dd:SYSFTPD for local site configuration parameters.
 EZA1450I IBM FTP CS V2R5
 EZA1466I FTP: using TCPIP
 EZA1772I FTP: EXIT has been set.
 EZA1554I Connecting to: supportftp.broadcom.com 141.202.253.54 port: 21.
 220-Welcome to Broadcom Managed File Transfer - NODE 3 / SUMFT09
 220 CA Managed File Transfer Server Ready!
 EZA1701I >>> AUTH TLS
 EZA2589E Connection to server interrupted or timed out. Waiting for reply
 EZA1721W Server not responding, closing connection.
 EZA2897I Authentication negotiation failed
 EZA1457I You must first issue the 'OPEN' command
 EZA1735I Std Return Code = 10220, Error Code = 00009

Resolution

There was a firewall change on the client side that allows a few packets of data to flow (so the “banner” is received from the FTP server but the firewall then detects its FTP on port 21 and then drops packets after that.  Mostly likely in the middle of the SSL handshake the packets start getting dropped.