Re^2: Net::FTP port inconsistencies

Hi Dave,

Thanks for your reply. We already use passive mode as indicated by the code below:

my $ftp = Net::FTP->new($self->{HOSTNAME},
                  "Firewall" => "",
                  "Port" => 21,
                  "Debug" => 0,
                  "Passive" => 1);
[download]

I just tried creating an FTP connection from the linux command line and I get the same problem, i.e. I can login and move to the relevant directory but the put command times out. Perhaps, this is a setting on the linux server??

rgds
Conor

Comment on Re^2: Net::FTP port inconsistencies Download Code

Replies are listed 'Best First'.
Re^3: Net::FTP port inconsistencies by dave_the_m (Monsignor) on Feb 18, 2005 at 18:51 UTC
In passive mode, the data connection is initiated by the cleint, so it is likely to be the firewall on the server which is too strict. I'm too sure about the `"Firewall" => ""`; I'm not sure whether a blank proxy name acts the same as no proxy; you might want to comment out that line and see if it makes any difference (but it probably won't). A final suggestion would be to use sftp if possible - it's a lot more firewall friendly! Dave.	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: Net::FTP port inconsistencies
by dave_the_m (Monsignor) on Feb 18, 2005 at 18:51 UTC

I'm too sure about the "Firewall" => ""; I'm not sure whether a blank proxy name acts the same as no proxy; you might want to comment out that line and see if it makes any difference (but it probably won't).

A final suggestion would be to use sftp if possible - it's a lot more firewall friendly!

Dave.

[reply]
[d/l]