Sorry, quite right,
Main Topics
Browse All TopicsI've spent enough time on this, I need some other eyes to help me out. ASA 5510. VPN users can connect fine, but no access to internal IPs. On the VPN client and on the ASA log there is no RCX traffic. Thanks in advance for your help!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Your VPN pool of addresses is the same as your internal subnet. I would recommend changing it to something different. It's likely causing routing issues. It can't return traffic back to the VPN users since the subnet is directly connected on the inside. In addition to that I wouldn't recommend using 192.168.1.x as a VPN pool since most home setups use that subnet in most cases as well.
remove this line
route inside 192.168.5.0 255.255.255.0 192.168.1.1 1
this line is saying that if you need to find 192.168.5.0/24 your next hop is 192.168.1.1 which is not the case.
add this line
crypto dynamic-map outside_dyn_map 20 set reverse-route
this should take care of inserting static entries into the routing table pointing out of your outside interface for remote vpn clients establishing a vpn connection.
when the vpn is up do a show route to check the routing table
Thanks for your help. Made your recommended changes. Still no connection internally, VPN client and ASA show 0 RCV. Here is sh route:
Result of the command: "sh route"
S 0.0.0.0 0.0.0.0 [1/0] via XXX.XXX.28.74, outside
C 192.168.1.0 255.255.255.0 is directly connected, inside
S 192.168.5.10 255.255.255.255 [1/0] via XXX.XXX.28.74, outside
C XXX.XXX.28.72 255.255.255.252 is directly connected, outside
Additionally, when I try to ping any internal device from the CLI of the ASA I get ???? I can ping the inside int okay.
Business Accounts
Answer for Membership
by: mitrushiPosted on 2009-10-22 at 09:35:25ID: 25636115
it seems to me you have attached the wrong config file!!