On 2005.11.03 14:57, Ashley M. Kirchner - ashley@xxxxxxxxxx wrote:
Jim Laurino wrote:
...
I just got off the phone with the company and they made a small change in
our config. Now, all the kiosks have to do is connect via FTP to their
server and drop a file. That's it. Nothing comes back, no inbound
connections to the kiosks. Just going out.
So, just out of curiosity, I decided to try doing a manual FTP transfer
from a completely different machine on the network. One that CAN connect to
external ftp sites just fine and transfer files. And this is what I see:
- Open DOS window
- Connect to FTP server
- enter 'PUT file.xml' command
...and that's where it hangs.
....
Please remember that this is a machine onto which I CAN open an ftp
connection to anywhere in the world and be able to send and receive files
just fine. So then why is it not working when going to these people?
---- FIVE MINUTES LATER ----
I just tried directly from the firewall machine and found out they don't
allow PASSIVE mode ON... As soon as I turn passive mode off, the transfer,
FROM THE FIREWALL MACHINE, works. (firewall machine has an external IP)
So now I wonder, is it because of the passive mode setting they have?
Could that be why ftp transfers from within the firewall fails?
non-passive (active) FTP requires that
the outside ftp server be able to open
a secondary connection to the client.
That is why passive mode is so popular
when the ftp client is behind a firewall -
both of the connections are originated from the client,
and no ports have to be opened on the firewall
for the incoming secondary connection.
I was confused about this earlier,
and may have contributed to the confusion.
A clear explanation is here http://slacksite.com/other/ftp.html
So, it is possible that your firewall is not configured to allow
active mode ftp connections. (But it can be done).
HTH
--
Jim Laurino
nfcan.x.jimlaur@xxxxxxxx
Please reply to the list.
Only mail from the listserver reaches this address.
