02-09-2011 09:20 AM - edited 02-21-2020 05:09 PM
Hi Sorry for the post but seem to hit a snag which I may be completely missing.
I will post the config here however some names have being changed and IP's
I have just sentp Anyconnect on the ASA for VPN
The problem I have is this -
I can connect through anyconnect using an SSL Cert from the ASA,
I authenticate through the Domain contoller fine.
I get a IP address from the pool 192.168.100.1, gateway always seems to be 192.168.100.2
Then I can't access anything on the network I want to get to 170.62.0.0/16
I have attached the Config file
If anyone can tell me what I may be missing it or have done wrong.
Solved! Go to Solution.
02-09-2011 10:03 AM
Hi ,
In your firewall you route 170.62.0.0/16 through 170.62.4.11 gateway, in this other router 170.62.4.11 could you check if you have a route back for your VPN pool network 192.168.100.0/24, if not add a route back pointing to your asa inside interface ip 170.62.4.22 and try conecting again.
Regards
02-09-2011 10:03 AM
Hi ,
In your firewall you route 170.62.0.0/16 through 170.62.4.11 gateway, in this other router 170.62.4.11 could you check if you have a route back for your VPN pool network 192.168.100.0/24, if not add a route back pointing to your asa inside interface ip 170.62.4.22 and try conecting again.
Regards
02-10-2011 06:59 AM
Hi - Yes when I stepped back and looked at this and the comments from Cisco saying about the IP Pool in different subnets - I changed it to the Internal LAN with a new IP Pool
I can now ping/connect to all Internal resources.
Thanks
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