> From: Greg Pennefather <[EMAIL PROTECTED]> > If the FTP client is able to connect and issue commands but then doesn't get > any response, then using a passive ftp client and server is the answer. FTP > has always been a problem for firewalls and that's why passive mode clients > were introduced.
Thanks for the suggestions Rob and Greg, but we are already using passive ftp from both dedicated FTP clients and from within web browsers like Safari and they all fail to download the files off the server when the built-in firewall in Tiger Server is enabled despite supposedly enabling FTP in the firewall's "allow" list. As a test, instead of trying to set up an Advanced Rule along the lines of: "ALLOW If protocol is TCP and source port is 20,21 and destination port is 1024-65535" I just opened ports 1024-65535 to FTP and it all worked. However, that is a big swathe of ports to open without the "if ports 20,21 are the source" criteria so I'll keep looking. Apples docs at this detail are pretty poor :-( -Mart -------------------------------------- Martin Hill mailto:[EMAIL PROTECTED] homepages: http://mart.ozmac.com Mb: 0417-967-969 hm: (08)9314-5242
