Once I am in VPN tunnel, I can't Ping or Telnet to the ASA using Inside interface IP.
Below is the partial configuration:
telnet 10.17.70.0 255.255.255.0 Outside
telnet 172.17.0.0 255.255.0.0 Inside
telnet timeout 10
ssh 172.17.0.0 255.255.0.0 Inside
ssh timeout 60
ssh version 1
console timeout 0
do you have AAA server group LOCAL configured? if so add this statement.
aaa authentication telnet console LOCAL
make sure you do not have in your config any icmp deny acl towards inside interface, for example icmp deny any inside will block pings on inside interface, check that.
once you vpn try telnet to asa, if not success please post sanitized config.
sorry for late reply..
your ra vpn network is consider inside not outside, you will not be able to telnet or icmp to asa inside while in vpn and this statement pointing to oustide interface. please correct this and post your results.
remove this statement
no telnet 10.17.70.0 255.255.255.0 Outside
and replace it with
telnet 10.17.70.0 255.255.255.0 inside
The log file does not have any info on ICMP, we have also tried "debug icmp" still no sign ICMP packets. Besides issue with Telnet, we can't get to websites that are on our business partner "lacounty" interface.
are the websites under the 192.168.1.0 network ? f so can you reach 0.0.0.1 next hop router from the asa? when you say you cannot reach websites via lacounty interface is it through vpn or anyone behind asa.
The unreachable websites are in 10.2.0.0 which resides beyond "lacounty" interface and we have this problem only when we're in VPN.
We found 2 issues with the config that prevent us from Telnet to the ASA.
1- Typo on nonatdmz access-list, should have
been 10.17.70.0 instead of 10.16.70.0
2- Splittunel acess-list did not include
10.0.0.2 "Inside" interface
You help is greatly appreciated,