D.1 BorderManager 3.6 and 3.7

Performance

If you are using a BorderManager® proxy server to redirect requests to your iFolder server, be advised that uploads to the iFolder server are very slow.

To alleviate this problem, enter the following at the BorderManager server console:

set tcp delayed ack=off

iFolder Still Connects When Authenticated Proxy Fails

If the proxy settings of the iFolder client fail, the iFolder client tries to connect directly (bypassing the proxy).

When using authenticated proxy, Internal (private) users might still gain access without providing authentication credentials if IP forwarding is enabled. To avoid this, simply make sure that IP forwarding is disabled on the proxy server.

Port Conflict

When proxy authentication is enabled, the default listening port is 443. If iFolder 2.1 and BorderManager are running on the same server and proxy authentication is enabled, either iFolder or BorderManager will need to listen on a different port.

NAT Loopback/Boomerang

If iFolder is running on a private segment and public access is allowed (via NAT), a public access address is specified in the iFolder server configuration. All requests to the private address will be forwarded to this public address. When trying to access iFolder from the private segment, the user will encounter the NAT loopback problem and the connection will fail.

The workaround is to use a DNS name as the user access address in the iFolder server configuration, and resolve this name to the public address for public users and to the private address for internal users.