11.4 Deployment Scenarios

Consider the example of a small organization that needs to set up multiple iFolder servers for data sharing and backup, and it has a limited number of IP addresses that are available for public use. The organization is not planning to expose all the iFolder servers to the external network even though firewall and traffic filters like ZoneAlarm* can be deployed. Also, the organization is not ready to bear the additional costs of deploying firewall and traffic filtering software.

The routers available in the market come with built-in traffic filtering and maintain a database of known attacks. This helps the organizations track and avoid security threats and attacks.

To configure an iFolder server with NAT, you must ensure that the users can access the iFolder server via the router even though the server has a NAT address. This also means that the Web Access and the Web Admin console must be able to work outside the NAT network, because the users might sometimes be in a public domain and might need access to their iFolder data. The iFolder server’s public URL must be set to the router's DNS address, so that Web Access, Web Admin, and the clients can access the iFolder server inside the NAT network from the external network.