Tutorial: Configure Network Settings with the Admin Web UI
Access Server's Admin Web UI simplifies VPN network management with an intuitive, web-based administration interface.
Overview
One of the primary benefits of using Access Server is that it provides a convenient Admin Web UI, making network configuration easier. This page provides an overview of standard network settings that you can change from the Admin Web UI.
An installed Access Server.
Admin Web UI access.
Define the dynamic IP address network
By default, Access Server assigns an IP address from a default subnetwork to users who connect to the VPN. You can define this subnetwork:
Sign in to the Admin Web UI.
Click VPN Server.
Click the Subnets tab.
Enter your preferred Dynamic subnet for the Default VPN client address pool.
Click Save and Restart.
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:
Sign in to the Admin Web UI.
Click VPN Server.
Click the Subnets tab.
Enter your preferred Static subnet in the Static IP address pool.
Click Save and Restart.
You can configure the settings for how VPN clients communicate with private subnets within the server and whether or not internet traffic is routed through the VPN (split tunnel). You can also grant access to network services to clients connecting to the server via a gateway client.
Configure routing for private subnets within the server
Sign in to the Admin Web UI.
Click Access Controls.
Click the Global Access Rules tab.
By default, Access Server uses NAT when you specify Subnets on this tab.
NAT (Network Address Translation): Enables one-way traffic from VPN clients to private subnets. While VPN clients can send traffic to resources in the private subnet, responses are sent back to Access Server, which then routes the traffic to the correct client. Traffic from the private subnet doesn't directly return to the VPN clients.
Routing: Allows two-way traffic between VPN clients and private subnets. With routing enabled, both the VPN clients and the private network can send traffic to each other. You can optionally configure Access Server to allow private subnets to access all VPN clients' IP addresses and subnets by enabling Route and then specifying the private subnets.
Click Save and Restart.
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.
Full-tunnel or split-tunnel VPN: Route all or only specific traffic across the VPN by setting this up.
Click Access Controls.
Click the Internet Access and DNS tab.
Set your preference for Internet gateway between Full-tunnel and Split-tunnel.
Click Save and Restart.
VPN gateway: Enable client access to network services via a VPN gateway.
Click Access Controls.
Click the InterClient Communication tab.
Turn Access to the internal gateway address to On.
Slick Save and Restart.
Allow inter-client communication
You can enable communication between clients:
Sign in to the Admin Web UI.
Click Access Controls.
Click the InterClient Communication tab.
Under Global InterClient Communication, select Allow user-to-user connections.
Click Save and Restart.
If you want only administrators to have access to VPN clients:
Sign in to the Admin Web UI.
Click Access Controls.
Click the InterClient Communication tab.
Under Global InterClient Communication, select Admins can access all users.
Click Save and Restart.