06-09-2009 06:12 AM - edited 03-04-2019 05:02 AM
06-09-2009 06:56 AM
Hi there.
Could this be an issue with your connection being dropped due to no translation rule being in place? Do your logs show anything?
Does something like this fix it?
nat (outside) 0 192.168.2.96 255.255.255.224 outside
Paul
06-09-2009 12:39 PM
Definitely have something wrong with your no-nat statement...
access-list inside_nat0_outbound extended permit ip 192.168.1.0 255.255.255.0 192.168.2.96 255.255.255.224
Just looking at your config, I'm assuming it would need to be
access-list inside_nat0_outbound extended permit ip 192.168.1.0 255.255.255.0 192.168.2.0 255.255.255.0
If you're getting an IP, everything security-wise is okay.
Hope this helps, rate if it does.
JB
06-09-2009 01:11 PM
I changed it to reflect your comment but alas it did not change anything. I appreciate your input though.
06-09-2009 01:18 PM
Andrew
Your nonat acl was fine as your vpn pool handed out addresses that were in the range of 192.168.2.96 255.255.255.224.
Could you let us know which internal resources you are trying to connect to from the vpn client ?
Jon
06-09-2009 01:32 PM
I've had issues if my subnet doesn't match up with the DHCP Pool (PIX days) as the pool is a /24 and you're specifying a /27. Can you repost the latest config?
Thanks,
JB
06-09-2009 01:36 PM
06-09-2009 01:34 PM
I'm trying to hit the inside interface, 192.168.1.1 or anything on that subnet.
06-09-2009 01:43 PM
NAT (inside) 0 access-list inside_nat0_outbound
I don't think you need access-list inside_access_in extended permit icmp any any as the first line should cover it.
Hitting the inside interface of the firewall, I believe you would need to noNAT the outside interface to properly source the traffic. I think I've done it once and it was always easier to RDP to a box on the inside and bounce back out to the firewall.
Hope this helps, rate if it does.
JB
06-09-2009 01:49 PM
Not sure what you mean about no-natting the outside interface. Thanks for the help!
06-09-2009 01:54 PM
Again this is from my PIX days, but if you try and connect to the inside IP of the firewall, it attempts to send that traffic back out the interface. Might have gotten something goofed, or maybe it was a site to site VPN. It's been awhile. :)
Is everything operational then?
Hope this helps, rate if it does.
JB
06-09-2009 02:11 PM
06-09-2009 05:23 PM
Hi Andrew,
Can you please try this command and see if you can ping the inside interface when VPNed?
management-access inside
-Rakesh
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