This is a quick run-down of the Cisco VPN client and various configuration thereof.
Brief description:
******************
The Cisco VPN client is a software based product allowing mobile users to connect securely to their home/office via encrypted VPN tunnels.
Availability:
*************
The Cisco VPN clients support a variety of platforms including Windows, MAC OS, Linux and Solaris, more details are available at http://www.cisco.com/en/US/products/sw/secursw/ps2308/index.html. The Cisco VPN client is not free but does come bundled with some of the VPN Hardware such as VPN Concentrators (now end of life) or the Cisco ASA.
The current TESTED release of the Cisco VPN client by myself for a windows based system is:
- 5.0.00.0090-Beta client
(This client was primarily released to accommodate Windows Vista and having used this client for the past month or so am yet to confirm any issues.)
The current client available for Windows OS:
- vpnclient-win-is-5.0.00.0340-k9-bundle
The current client available for MAC:
- vpnclient-darwin-4.001.0080
The current client available for Linux:
- vpnclient-linux-4.8.00.0490-k9
The current client available for Solaris:
- vpnclient-solaris-4.6.02.0030-k9
Basic Configuration
*******************
The following simple configuration instructions are based on the current TESTED version of the Windows Client however from experience all of the client versions are configured in much the same way as long as the basic principles are understood.
Run the client (presented with the following screen)
This screen lists all the connection entries (Peers available), as it stands on this screenshot no peers have been configured as of yet.
* Click New along the top icon toolbar (presented with the following screen)
(Here we can set up a new entry for connecting to a remote peer)
- Connection entry
In here we can enter the name/purpose of the connection this can be a quick descriptive phrase (ie: Office - Leeds)
- Description (optional)
Any more description for the purpose behind this connection can be put here.
- Host
This is the important part. In this filed we need to specify the peer or VPN termination point (ie: The IP of the VPN concentrator/ASA at the Leeds office) This field requires the IP address.
- The four tabs Authentication|Transport|Backup Servers|Dialup
I am going to concentrate on only one of these tabs (Authentication). I have set-up many clients and cannot remember a single instance where I have needed to venture into any of the other tabs.
i) Group Authentication:
As the name suggest enter the group authentication details. (ASA refers to this as the pre-shared-key)
Click Save to store the newly configured connection and you should now see the connection entry in the main application window:
(NB: The IP in this example is fictitious to represent a public address)
Simply select the desired connection entry (only one available in this example) and click connect (or double click the entry).
Here we have per the user based authentication prompt, if you see this then you know group authentication has worked!!
After you have entered the correct details you should (depending on the admins point of view) see a notification which should be there for legal reasons:
(US laws require a notification else unauthorised users have the right to access)
After continuing you are now successfully connected. This is depicted in the toolbar with the padlock icon:
Entries (RSS)