Hi Greg, That is an exception. The reason for this is that FTP requires secondary connections and you can't make the external clients firewall clients. Therefore, you need an application filter to handle the incoming requests. The FTP Access application filter is built to handle FTP sites using standard port numbers. Using the Firewall client and the wspcfg.ini setup on the publishing server allows you to get around the application filter requirement (to a certain extent). HTH, Tom Thomas W Shinder www.isaserver.org/shinder <http://www.isaserver.org/shinder> ISA Server and Beyond: http://tinyurl.com/1jq1 <http://tinyurl.com/1jq1> Configuring ISA Server: http://tinyurl.com/1llp <http://tinyurl.com/1llp> -----Original Message----- From: Greg Mulholland [mailto:greg_mul@xxxxxxxxxxxxxxx] Sent: Friday, January 31, 2003 1:01 AM To: [ISAserver.org Discussion List] Subject: [isalist] RE: Exchange 2000 and Firewall client http://www.ISAserver.org What happens if the server is also an ftp server running on an unstandard port, don't we use the firewall client for that or am I wrong. Greg Mulholland ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Exchange Server Resource Site: http://www.msexchange.org/ Windows Security Resource Site: http://www.windowsecurity.com/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: tshinder@xxxxxxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')
