<div>
is there a permissive ACL rule in place for the following?<br />
<br />
source: 192.168.0.0<br />
destination: VPN pool<br />
interface: inside<br />
<br />
also, is there a NAT exempt in place for the same traffic?
</div>


is there a permissive ACL rule in place for the following?

source: 192.168.0.0
destination: VPN pool
interface: inside

also, is there a NAT exempt in place for the same traffic?

<div>
i have attached the configuration with my post i don't know if you have seen it. In any case i have this rule:<br />
<br />
access-list inside_nat0_outbound extended permit ip 192.168.0.0 255.255.255.0 VPN_POOL2 255.255.255.0 <br />
nat (inside) 0 access-list inside_nat0_outbound<br />
<br />
However still it doesnt work..i dont know if i m missing something else..
</div>


i have attached the configuration with my post i don't know if you have seen it. In any case i have this rule:

access-list inside_nat0_outbound extended permit ip 192.168.0.0 255.255.255.0 VPN_POOL2 255.255.255.0
nat (inside) 0 access-list inside_nat0_outbound

However still it doesnt work..i dont know if i m missing something else..

<div>
<div class="content wysiwyg-content">
Hello<br />
<br />
The question is pretty simple. I can successfully connect to my ASA 5505 &nbsp;firewall via cisco vpn client 64 bit , i can ping any ip address on the LAN behind ASA but none of the LAN computers can see or ping the IP Address which is assigned to my vpn client from the ASA VPN Pool.<br />
<br />
The LAN behind ASA is 192.168.0.0 and the VPN Pool for the cisco vpn client is 192.168.30.0<br />
<br />
I would appreciate some help pls :) <br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2014/02_w08/834847/asa1.txt" target="_blank" class="file-inline" title="ASA 5505 config (6 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>asa1.txt</a><br />
<br />
Regards<br />
George
</div>
</div>


asa1.txt

Hello

The question is pretty simple. I can successfully connect to my ASA 5505  firewall via cisco vpn client 64 bit , i can ping any ip address on the LAN behind ASA but none of the LAN computers can see or ping the IP Address which is assigned to my vpn client from the ASA VPN Pool.

The LAN behind ASA is 192.168.0.0 and the VPN Pool for the cisco vpn client is 192.168.30.0

I would appreciate some help pls :) 



Regards
George

CISCO ASA 5505 VPN CLIENT CONNECTION

Cisco PIX is a dedicated hardware firewall appliance; the Cisco Adaptive Security Appliance (ASA) is a firewall and anti-malware security appliance that provides unified threat management and protection the PIX does not. Other Cisco devices and systems include routers, switches, storage networking, wireless and the software and hardware for PIX Firewall Manager (PFM), PIX Device Manager (PDM) and Adaptive Security Device Manager (ASDM).

Cisco

A virtual private network (VPN) is a network that uses a public telecommunication infrastructure, such as the Internet, to provide remote offices or travelling users access to a central organizational network securely. VPNs encapsulate data transfers using secure cryptographic methods and other security mechanisms to ensure that only authorized users can access the network and that the data cannot be intercepted.

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.