EZA2233I

The SOCKS server rejected the BIND to ip_address with reply_field
Explanation
 The FTP client tried to establish a data connection
to the FTP server through a SOCKS server.  The SOCKS server rejected
 a SOCKS BIND request from the client.  
 ip_address is
the address of the FTP server 
 reply_field is
a decimal value describing why the SOCKS server rejected the BIND
request. When SOCKS V4 protocols are in use, the value is the CD field,
or result code,  from  the BIND reply as defined in the document SOCKS:
A protocol for TCP proxy across firewall by Ying-Da Lee.  The
following excerpt is from that document listing the possible return
codes and explanations.  	 91
The request rejected or failed.
92
The request rejected because SOCKS server cannot connect to identd
on the client.
93
The request rejected because the client program and identd report
different user IDs.  

 When SOCKS V5 protocols are in use, the value
is the REP field, or reply value, from the BIND reply as defined in
RFC 1928. See Related protocol specifications for information about
accessing RFCs.

System action
 FTP stops trying to access the FTP server through
the SOCKS server.

Operator response
 Contact the system programmer with the error.

System programmer response
 You can get more information about
why the SOCKS server rejected the BIND request by using the dump and
debug subcommands while attempting the connection.  See the z/OS Communications Server: IP User's Guide and
Commands for information about the dump and debug
subcommands.
 SOCKS V4 or SOCKS V5 protocols are specified in
the file or data set indicated by the SOCKSCONFIGFILE statement in
FTP.DATA.
 For the SOCKS V5 protocol, the reply value is one
of the following:   2
The SOCKS server has been configured to reject connections to
the target IP address.  Follow the procedure for SOCKS V4 protocol
and CD field 91.
all other reply values
Contact the administrator of the SOCKS server with the error.

 For the SOCKS V4 protocol, the CD field is
one of the following:   91
A possible explanation is that the SOCKS server is configured
to reject connections to the target IP address. If you want to allow
the FTP client to connect to the target FTP server, either ask the
administrator of the configured SOCKS server to allow connections
to the FTP server, or change the FTP client SOCKS configuration. You
can configure the client to use a different SOCKS server, or you can
configure the client to connect to the FTP server without using a
SOCKS server. It is also possible that a general SOCKS server failure
occurred. Contact the administrator of the SOCKS server with the error.
92, 93
The SOCKS server requires inetd authentication but inetd authentication
is not supported by the FTP client.   Change the FTP client SOCKS
configuration to use a SOCKS server that does not require identd authentication,
or ask the administrator of the SOCKS server to allow the connection
without identd authentication.

 See the z/OS Communications Server: IP Configuration
Guide and the z/OS Communications Server: IP Configuration
Reference for information about configuring the FTP
client to use SOCKS servers. 

Module
 ezaftpsc

Procedure name
  bindV4(),
bindV5()