10-23-2012 01:43 AM
We are currently attempting to switch our VPN services from OpenVPN to Cisco VPN.
We have configured our ASA unit to accept connections and also configured our Windows 2008 RADIUS server on our Domain controller. We have a few test clients which have successfully connected to the network. They can access all network resources and Internet traffic is being forced through outrtonPort.
We are in a position now where we would like to lock down some of the settings to prevent out users bypassing our internet filtering system.
When the workstation it turned on, we have set CiscoVPN to auto launch at logon and then autoconnect to our profile. Meaning whenever they are logged in, they are on our network for tracking purposes.
However they can easily bypass this by simply disconnecting the connection, or closing the client, meaning they will then get unfiltered and unrestricted Internet access.
Can anyone advise how we can prvent this from happening or could anyone give any good examples of how we should be doing this.
Is it typical to enforce such restrictions and are there any tips or tricks that anyone can give us?
Thanks in advance.
10-23-2012 06:01 AM
Hi,
In order to make sure that the VPN client remains connected all the time, as long as the user is out your network, I would suggest the following feature:
Let me know if you have any questions.
Portu.
Please rate any helpful posts
10-23-2012 06:27 AM
Hi, thank you very much for your kind suggestion.
Using the AnyConnect software is our last resort. Do you know if there is something similar which will work specifically with the Cisco VPN Client?
Thanks again.
10-23-2012 06:56 AM
The IPsec client does not have a similar feature to force the client to remain connected.
HTH.
Portu.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide