Whe I got home yesterday I turned on the 'Allow Passive Transfers' option in the config file, but, I'm still having the same problem. I am not using a 'client' program to connect. Im just going to a command prompt on my $M box and doing ftp from the command line.
This may be a problem with my d-link firewall-router. When I enabled the virtual server ftp option on the d-link, it only opened port 21. In fact, it showed 'Private Port 21 - Public Port 21'. I another rule for 20 but no luck. I looked at the d-link help for their virtual server feature but it kept referring me to works by the noted Spanish author 'Manual'. I may have to check out his stuff this evening. Thanks, Mark. > I believe the "passive switch" that was referred to was in the ftp client > itself. Basically, the way a "normal FTP connection" works is like this: > > client -->ftp --> server > <-- ftp-data -- > > The client opens connections on port 20 and the server opens them back > to the client on port 21. Passive mode turns around that second > connection > so that the client makes both of them like this: > > client -->ftp --> server > -- ftp-data --> > > This works better when the _client_ is behind a firewall and the > server can't open a connection back to it. > > Cheers, > Tanner > > > -- > Tanner Lovelace > clubjuggler at gmail dot com > http://wtl.wayfarer.org/ > (fieldless) In fess two roundels in pale, a billet fesswise and an > increscent, all sable. > -- > TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug > TriLUG Organizational FAQ : http://trilug.org/faq/ > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ > -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
