Hi Amy, The SecureNAT client does not support secondary connections without the aid of an application filter. If the AS/400 app supports SOCKS4, you can use the SOCKS filter and configure the AS/400 app to use that to manage the secondary connections. Otherwise, the SecureNAT client just can't support the secondary connections without a customer app filter. And the real problem with putting secure FTP behind a firewall is the issue of how the firewall will be able to access the encrypted information in the application layer headers to manage the connections? There would have to be some form of "secure FTP bridging" where the client establishes a secure link with the firewall, the firewall decrypts the packet to read the app layer data so that it can manage the connection, then the firewall reencrypts the packet and forwards it to the destination. A very large PIA, and typical of EDS :-) I'd like to see the swiss cheeze filters configured on the pix to allow this to work. I suspect the entire range of ephemeral ports must be opened. But I'd be glad to be educated if there was actually a secure way to configure a pix to allow this. I hope the app supports SOCKS 4, that should solve all your problems. HTH< Tom Thomas W Shinder www.isaserver.org/shinder ISA Server and Beyond: http://tinyurl.com/1jq1 Configuring ISA Server: http://tinyurl.com/1llp -----Original Message----- From: Amy Babinchak [mailto:Amy@xxxxxxxxxxxxxxxxxxxxxxxxxx] Sent: Tuesday, September 16, 2003 1:27 PM To: [ISAserver.org Discussion List] Subject: [isalist] ftps http://www.ISAserver.org Let me first say that I've read the article on the isaserver.org website on the complexities of ftp and the portion near the bottom where it gives the gloomy news about ftps, secureNat clients and ISA server. This is exactly where I'm at. I have an AS400 that needs to transmit information to and from EDS and another company using FTPS. The AS400 can't run the Firewall client so I created a client address set for it and the appropriate protocol rule, protocol definitions and matching packets filters for the required ports (990, 2015, 1969 and 1970; all in and out) and I disabled the FTP application filter and FTP packet filters that were in ISA by default so that they wouldn't get in the way. Attempts by the as400 to connect timeout. Not much is logged by the firewall - it shows 10.0.0.99 anonymous (this is the as400) connecting to the server in the log and all else are dashes. I went to all of this effort simply because in the article it isn't clear to me why non-firewall client computer can't access ftps. Can someone explain why not or give some advice on making it work? If I can't come up with a workable solution with the ISA server then it is going to be replaced by a Cisco Pix; this is the recommended hardware from EDS. I'd hate to see that happen. Amy ------------------------------------------------------ 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 ------------------------------------------------------ Other Internet Software Marketing Sites: Leading Network Software Directory: http://www.serverfiles.com No.1 Exchange Server Resource Site: http://www.msexchange.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ 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')