FTP > Configuration > General
You can have IWSS act as an FTP proxy server. If you need to protect FTP uploads on multiple servers, install one instance of the IWSS FTP module for each server.
Use stand-alone mode: Choose this option if IWSS is installed as the only FTP proxy on the network.
Use FTP Proxy: Choose this option if IWSS is installed on a network with an existing FTP proxy; IWSS may be on the same machine as the FTP proxy or a different one, which will affect the values you enter for the following fields:
Proxy server: Specify the host name or IP address of the FTP proxy that IWSS receives FTP traffic from; If IWSS FTP scanning is installed on the same machine as the FTP server, use "localhost"
Port: Indicates the port number that the FTP proxy uses to deliver FTP traffic to IWSS, typically, port 21.
Because most firewalls are configured to reject unsolicited port requests from outside the LAN, IWSS supports both Active and Passive file transfers. Passive transfers are usually necessary if there is a firewall on the LAN, or if you have experienced failed data channels when trying to setup Active FTP.
Passive FTP—choose this option if IWSS is running inside a firewall that allows only Passive FTP. MORE>>
In Passive FTP (or PASV mode), the FTP client initiates contact with the FTP server. The FTP server tells the client what port to connect to for data transfer and the client opens another connection to the server on this port.
Active FTP—choose this option if IWSS was installed as a Stand-alone, is running inside a firewall that allows Active FTP, or if it was installed to be running outside the firewall (not recommended). MORE>>
In Active FTP, the FTP client initiates contact with the FTP server and then negotiates a mutual data transfer port (Port 22020 is usually used in IWSS). The server connects back to the client using the negotiated port.
Note: Your firewall must be able to open this port dynamically and let the FTP server communicate with the client, or you must open the port yourself.
Note: The maximum number of client requests and number of worker threads to create can be manually configured by editing the intscan.ini file.