This article explains the purpose of the proxy settings in the Access Commander.

It describes what a proxy is, when (and when not) to configure it, and what each field in the proxy configuration means.

It’s meant to help to understand the settings — not to set up own proxy server. 

Requirements

• 2N Access Commander 3.4.2 or newer

Proxy Settings

Some organizations use proxies to control access, add security, or monitor usage. A proxy server is a server that sits between software and the internet. 

If you are using a normal home or office internet connection, you usually don’t need to change these settings.

You only need to enter proxy details if:

• Your IT department or network administrator has given you proxy settings.

• You are on a managed or restricted network that requires all traffic to go through a proxy.

If you are unsure, just leave these fields empty. 2N Access Commander will connect directly without a proxy.

Settings explanation

1. HTTP proxy – For standard web traffic (http://) from 2N Access Commander to internet.

2. HTTPS proxy – For secure web traffic (https://) from 2N Access Commander to internet
3. FTP proxy – For file transfers using FTP.
4. Don’t use proxy for – enter Domains or IP addresses that should connect directly, without using the proxy. Localhost and 127.0.0.1 never use a proxy automatically. 

   Example: .example.com (all addresses under domain example.com)

   Example: 192.168.1.0/24 (local network range) - if you need to not use proxy for connection between 2N Access Commander and 2N OS devices fill in the local network which 2N OS devices belongs to. 

   Example: 192.168.1.10 (direct IP address) - if you need to not use proxy for connection between 2N Access Commander and 2N OS device fill in the IP address of that 2N OS device. 

 If you haven’t been told by your IT administrators to enter anything here, you can safely leave the fields empty.