About Shawn Barrick

Shawn Barrick · 09-14-2011

I'm having problems getting AnyConnect clients to reach a server (192.168.139.3) on the Inside interface of my ASA 5505. Ideally, this would be accessible from the DfltAccessPolicy or another dedicated policy, but right now I'm happy with any access...

Shawn Barrick · 08-04-2011

I'm trying to connect two ASA 5505s for a IPSec L2L VPN. They can connect, but not pass traffic from the AnyConnect subnet. I've added the config from ASA-2, with the LAN subnet of 192.168.138.0 and a subnet of 192.168.238.0 for AnyConnect client....

Shawn Barrick · 09-15-2011

Turns out it was a configuration issue with the device on the LAN. Nothing to do with the ASA at all.

Shawn Barrick · 09-15-2011

I've cut down the config, disabling the IPSEC tunnel to ease troubleshooting:: Saved : ASA Version 8.2(1) ! hostname asa-dal domain-name dtainc.us enable password LpOk82NJGblSbuos encrypted passwd 2KFQnbNIdI.2KYOU encrypted names name 192.168.239.0 ...

Shawn Barrick · 08-05-2011

Gustavo,The group policy change did it. Thanks so much for your assistance.

Shawn Barrick · 08-05-2011

Still no luck, even after a reconnect. I've attached the output you requested. Thanks again for your quick reponses.

Shawn Barrick · 08-05-2011

Thanks for your assistance. I made the changes but still no luck.I've attached both configs.

Member Since	‎04-22-2011 08:15 AM
Date Last Visited	‎08-29-2018 12:01 AM
Posts	8

User Statistics

User Activity

AnyConnect access to Inside IPs

AnyConnect access over L2L IPSec VPN

AnyConnect access to Inside IPs

AnyConnect access to Inside IPs

Re: AnyConnect access over L2L IPSec VPN

Re: AnyConnect access over L2L IPSec VPN

Re: AnyConnect access over L2L IPSec VPN