For the past 2 days I've been trying to get ftp forwarding to work in
our company's network.
The configuration is such:
Firewall - runs ipmasquerading & ipmasqadm portfw.
Internal Machine with FTP server.
The firewall linux box binds to several Internet IP addresses (IP
Aliasing) and when a client FTP to one of those IPs, the ftp traffic
will be port forwarded to the internal machine's FTP server.
This configuration works well only when a Linux FTP client makes an
active connection to the ftp site. It will not work for passive mode
cos' the author for ipmasqadm told me that it is not supported yet.
Anyhow, the question is:
Why the hack Windows FTP client wouldn't be able to connect to the same
FTP server that's working for Linux FTP client?
I've tried CuteFTP, WSFTP, LeechFTP, FTPControl to no avail. These
client's allow you to setup passive connection but I'm not sure if
their default is active connection or not??? I'm saying this because
when I did a "netstat -M" on the firewall during the ftp session from
the Windows Client, there's not connection from the source ftp-data
port (20) to a high port on the firewall, which is what active
Any tips/ideas/suggestions on how I can achieve FTP forwarding is very
much appreciated! Thanks.
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.