"Jeremy" <jeremy___ninprodata.com> wrote in message
news:4536c876$1@newsgroups.borland.com...
> We changed our firewall, and now some clients can't connect.
> I need to know why.
Did you try turning it off, like I suggested? If that works, then you need
to find another firewall that actually works properly.
> Here's what filezilla is telling me. I think this is saying that our
> server is saying please connect on the following ip and port, right?
Yes.
> That's the correct IP number.
But, is it an IP that is reachable by your client machine under normal
conditions?
> Command: LIST
>
> Error: Transfer channel can't be opened. Reason: A connection attempt
failed
> because the connected party did not properly respond after a period of
time,
> or established connection failed because connected host has failed to
> respond.
When establishing a PASV connection, the FTP server opens another listening
socket that the FTP client then connects to for transferring the data. If
the firewall is blocking that connection, then the FTP server will
eventually timeout and close the passive socket, and then report an error
back to the FTP client for any command that needed that socket.
In Indy 9, List() will establish the secondary connection to the passive
socket before then sending the LIST command. It is hard to say whether
FileZilla is doing that or not. My guess is that it does not.
Gambit
