Tutorial: Configure Network Settings with the Admin Web UI⁠

Define the dynamic IP address network⁠

By default, Access Server assigns an IP address from a default subnetwork to users that connect to the VPN. You can change this subnetwork:

1. Sign in to the Admin Web UI.

2. Click Configuration > VPN Settings.

3. Under VPN IP Network > Dynamic IP Address Network, the value in the field, Network Address defines a host IP address, which you can change to your preferred network address.

4. The field, # of Netmask bits defines the number of netmask bits, which you can change if desired.

5. Select Save Settings and Update Running Server.

Define the static IP address network⁠

To assign a static IP address to a user profile, you must first define the network of IP addresses that users can be assigned by Access Server. Defining this network follows essentially the same process as defining the dynamic IP address network:

1. Sign in to the Admin Web UI.

2. Click Configuration > VPN Settings.

3. Under VPN IP Network > Static IP Address Network, enter a value in the Network Address field for the subnet to use for static IP addresses.

4. Enter a value in the # of Netmask bits field for the subnet.

5. Select Save Settings and Update Running Server.

Configure routing for private subnets within the server⁠

1. Sign in to the Admin Web UI.

2. Click Configuration > VPN Settings.

3. By default, Access Server uses NAT for the setting, Should VPN clients have access to private subnets (non-public networks on the server side)? When NAT or routing is enabled, you can enter subnets in the field, Specify the private subnets to which all clients should be given access (one per line).

   1. Choosing Yes, using NAT enables one-directional traffic to the specified private subnets. Traffic from the client is sent to the subnet but doesn't route back to the client.

   2. Choosing Yes, using Routing enables both the client and private subnets to send traffic to each other. With this setting enabled, you can choose if you want to allow private subnets access to all VPN clients' IP addresses and subnets by setting Allow access from these private subnets to all VPN client IP addresses and subnets to Yes.

4. Select Save Settings and Update Running Server.

Other VPN routing configurations⁠

The remaining routing configurations are simple toggle button options. These are settings that don't necessarily require specifications for any subnets within the server.

• To allow internet traffic through the VPN, set Should client internet traffic be routed through the VPN? to Yes.

• To enable client access to network services via a VPN gateway, set Should clients be allowed to access network services on the VPN gateway IP address? to Yes.

• Select Save Settings and Update Running Server.

Allow inter-client communication⁠

You can enable communication between clients:

1. Sign in to the Admin Web UI.

2. Click Configuration > Advanced VPN.

3. Under Inter-Client Communication, set Should clients be able to communicate with each other on the VPN IP Network? to Yes.

4. Select Save Settings and Update Running Server.

If you want only administrators to have access to VPN clients:

1. Sign in to the Admin Web UI.

2. Click Configuration > Advanced VPN.

3. Under Inter-Client Communication, set Allow VPN users with Administrator privilege to access all VPN client IP addresses to Yes.

4. Select Save Settings and Update Running Server.