We have already tested device connectivity from the remote computer and the ASA. Let's open the web browser once more, navigate to https://200.1.1.1, and hit Enter. The following will be presented; notice that the Anyconnect-VPN GROUP is now available. This group was created in the Configuring a client-based remote-access VPN section. This provides the option to connect using the clientless VPN profile or the client-based VPN profile:

1. Enter Alice's user account details and click Login:

2. Once successfully authenticated, you'll see that the ASA is pushing the Cisco AnyConnect Secure Mobility Client to your computer. Follow the instructions to install it. Java Runtime Environment and Adobe ActiveX may be required:

3. Once the Cisco AnyConnect Secure Mobility Client has been installed on the remote worker computer, open it. Enter the IP address ASA-1, 200.1.1.2, and click on Connect:

4. Since ASA-1 is using a self-signed certificate, the following security warning will appear. Click on Connect Anyway to continue:

5. The Cisco AnyConnect Secure Mobility Client will provide the following prompt, requesting that you provide authentication details to prove your identity. Enter Alice's user account details and click on OK:

6. The following window should be presented displaying the current status:

7. Finally, the VPN connection is successful; the remote worker computer has now established a VPN connection to the ASA:

8. If we click on the gear icon on the Cisco AnyConnect Secure Mobility Client, we can obtain statistical details about the connection. Notice the VPN client (computer) receives the first usable virtual IP address from the pool we created in step 6, 192.168.2.100:

9. Let's head over to the ASDM; navigate to Monitoring | VPN | VPN Statistics | Sessions. Notice that AnyConnect Client and SSL/TLS/DTLS is set to 1 and Active. Adjust the following filter to AnyConnect Client. We can see the active users who are using the Cisco AnyConnect Secure Mobility Client for the VPN connection:

10. Clicking on Details on the right will open a new window, providing more statistical information about the user's connection:

11. Let's use the command line to verify the VPN status. Using the show vpn-sessiondb command will provide the sessions database for the VPN sessions that are terminated on the ASA:

12. By specifying the show vpn-sessiondb anyconnect command, specific details about users/connections that are made by using the Cisco AnyConnect Secure Mobility Client to the ASA can be displayed in the following screenshot:

13. On the remote worker's computer, run the ipconfig/all command on the Windows Command Prompt. Notice the client IP information is the same as what we had configured during steps 6 and 7 from the previous section, Configuring a client-based remote-access VPN:

14. Finally, we ping a machine on the corporate network, 192.168.2.10, to ensure end-to-end connectivity through the VPN connection: