SOCKS jvm or client owns active ftp protocol logistics

[RonVanCleave]

Hello,

We have a secure ftp client written in
java that must traverse to external/remote
servers via a SOCKS server or framework.

Under a passive mode the ftp client functions
correctly, while when used in a active ftp
mode the client fails.

The conclusion for the failure is that the
jvm is not binding to the SOCKS via a PORT
command with the SOCKS server which will
result in the SOCKS server acting as the
listener for the data connection that under
a active ftp session is established from the
remote server back to the original client
that started the ftp session.

I could provide more details on the ftp
protocol here, but will wait to see if any
responses are posted.

The basic question is what Java component
when evaluating a SOCKS scenario is
responsible for handling the special data
port connection logistics necessary to
complete a successful active ftp session.

Two possible answers or maybe hybrid answer,
- The client has the responsibility and must
be aware of the SOCKS being used.
- The jvm is responsible for understanding
what protocol is being executed and thus
handle 100% of the connectivity logistics
- Both the jvm and the client share
responsibility for the SOCKS logistics
- Where the jvm would blindly redirect all
connections through the SOCKS
- Then the client must take on the
responsibility for any protocol specific
requirements as is the case with an active
ftp session

Thanks for any help in advance.