05-26-2015 04:45 AM - edited 02-21-2020 08:14 PM
Hi,
We have several users that cannot connect to their "local ethernet network" when AnyConnect is installed.
Background:
- Users with Windows 7
- AnyConnect version 3.1.08009
- Authentication using certificates
- Always on policy - with the possibility for some users to disconnect
When the users connect at home (and have connection to the Internet) AnyConnect starts as it should and everything works.
But, when the same users (service engineers) needs to access a PLC using a small switch and "no connection to Internet" they run into problems.
The configure a local IP address (192.168.100.x), and then reboot the PC.
Now, when they try to ping they get a "general failure" error message.
After disabling the NIC, and then re-enabling it, they can ping for a few seconds - and then "general failure" again.
We have seen exactly the same behaviour on PC's in several different locations around the world.
All suggestions on how to solve it are appreciated.
05-26-2015 07:26 AM
Hello Stefan Strand,
Have you tried the following link configuration?
http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/70847-local-lan-pix-asa.html
05-26-2015 08:40 AM
I have seen that, and I think that works, but that is not really our problem.
The problem is that when "always on vpn" is in place, even if we in the Dynamic Access Policy allows some users to disconnect, when those users are on a LAN where there is no Internet connection, they cannot access local resources on that LAN.
05-26-2015 08:57 AM
Hello Stefan Strand,
I think that this is what you are looking for.
Configuring those policies will allow LAN access when there is not Internet connection while Always On is configured.
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