ASA 5510 - cant ping remote site from CLI 1

[MandyDroid]

I have recently installed an ASA5510 and built a VPN to my main office. I am not sure what I am doing wrong. The VPN works fine I can ping from a host behind the ASA to a host on the remote site. I cannot ping the remote site from the CLI of the ASA. This is causing me to not be able to manage the device accross the VPN. It seems to me like the ASA does not know how to communicate with a subnet on the other side of the VPN - like it is missing a route or something. I will post a sanitized config and pray that someone here knows what is cauing my headaches. I am also including a copy of my routes.

01(config)# sho ru
: Saved
:
ASA Version 8.2(5)
!
hostname WH-ASA-01
enable password 123456 encrypted
passwd 123456 encrypted
names
name xx.xx.xx.107 Main-Office
name 192.168.1.0 Main-Office-subnet
!
interface Ethernet0/0
nameif outside
security-level 0
ip address xx.xx.xx.58 255.255.255.248
!
interface Ethernet0/1
shutdown
no nameif
no security-level
no ip address
!
interface Ethernet0/2
shutdown
no nameif
no security-level
no ip address
!
interface Ethernet0/3
description Lacal Area Network
nameif inside
security-level 100
ip address 192.168.0.1 255.255.255.0
!
interface Management0/0
nameif management
security-level 100
ip address 10.0.0.1 255.255.255.0
management-only
!
ftp mode passive
access-list outside_1_cryptomap extended permit ip 192.168.0.0 255.255.255.0 Mai
n-Office-subnet 255.255.255.0
access-list inside_nat0_outbound extended permit ip 192.168.0.0 255.255.255.0 Ma
in-Office-subnet 255.255.255.0
pager lines 24
logging asdm informational
mtu outside 1500
mtu inside 1500
mtu management 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_nat0_outbound
nat (inside) 1 0.0.0.0 0.0.0.0
route outside 0.0.0.0 0.0.0.0 xx.xx.xx.57 1
route outside Main-Office-subnet 255.255.255.0 xx.xx.xx.57 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
aaa authentication ssh console LOCAL
http server enable
http 192.168.0.0 255.255.255.0 inside
http 10.0.0.0 255.255.255.0 management
http Main-Office-subnet 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto ipsec transform-set ESP-DES-SHA esp-des esp-sha-hmac
crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto map outside_map 1 match address outside_1_cryptomap
crypto map outside_map 1 set pfs
crypto map outside_map 1 set peer xx.xx.xx.62
crypto map outside_map 1 set transform-set ESP-3DES-SHA
crypto map outside_map interface outside
crypto ca trustpoint _SmartCallHome_ServerCA
crl configure
crypto ca certificate chain _SmartCallHome_ServerCA
certificate ca 6ecc7aa5a7032009b8cebcf4e952d491
.................................
.................................
.................................
quit
crypto isakmp enable outside
crypto isakmp policy 10
authentication crack
encryption aes-256
hash sha
group 2
lifetime 86400
crypto isakmp policy 20
authentication rsa-sig
encryption aes-256
hash sha
group 2
lifetime 86400
crypto isakmp policy 30
authentication pre-share
encryption aes-256
hash sha
group 2
lifetime 86400
crypto isakmp policy 40
authentication crack
encryption aes-192
hash sha
group 2
lifetime 86400
crypto isakmp policy 50
authentication rsa-sig
encryption aes-192
hash sha
group 2
lifetime 86400
crypto isakmp policy 60
authentication pre-share
encryption aes-192
hash sha
group 2
lifetime 86400
crypto isakmp policy 70
authentication crack
encryption aes
hash sha
group 2
lifetime 86400
crypto isakmp policy 80
authentication rsa-sig
encryption aes
hash sha
group 2
lifetime 86400
crypto isakmp policy 90
authentication pre-share
encryption aes
hash sha
group 2
lifetime 86400
crypto isakmp policy 100
authentication crack
encryption 3des
hash sha
group 2
lifetime 86400
crypto isakmp policy 110
authentication rsa-sig
encryption 3des
hash sha
group 2
lifetime 86400
crypto isakmp policy 120
authentication pre-share
encryption 3des
hash sha
group 2
lifetime 86400
crypto isakmp policy 130
authentication crack
encryption des
hash sha
group 2
lifetime 86400
crypto isakmp policy 140
authentication rsa-sig
encryption des
hash sha
group 2
lifetime 86400
crypto isakmp policy 150
authentication pre-share
encryption des
hash sha
group 2
lifetime 86400
telnet 192.168.0.0 255.255.255.0 inside
telnet Main-Office-subnet 255.255.255.0 inside
telnet timeout 15
ssh 192.168.0.0 255.255.255.0 inside
ssh Main-Office-subnet 255.255.255.0 inside
ssh timeout 5
console timeout 0
dhcpd dns xx.xx.xx.15 xx.xx.xx.235
!
dhcpd address 192.168.0.100-192.168.0.200 inside
dhcpd dns xx.xx.xx.15 xx.xx.xx.235 interface inside
dhcpd enable inside
!
dhcpd address 10.0.0.100-10.0.0.200 management
dhcpd enable management
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
username user password 123456 encrypted
tunnel-group xx.xx.xx.62 type ipsec-l2l
tunnel-group xx.xx.xx.62 ipsec-attributes
pre-shared-key *****
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect ip-options
!
service-policy global_policy global
prompt hostname context
call-home reporting anonymous
Cryptochecksum:2177c0918d38dd1b2f5a2a6959b86bcb
: end



######### routes #####################################################################################################

01(config)# sh route

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route

Gateway of last resort is xx.xx.xx.57 to network 0.0.0.0

C xx.xx.xx.56 255.255.255.248 is directly connected, outside
C 192.168.0.0 255.255.255.0 is directly connected, inside
S* 0.0.0.0 0.0.0.0 [1/0] via xx.xx.xx.57, outside

Avaya, Panasonic, Polycom, APC, MCP, A+
##################################
"When I was a child, I spoke like a child, I thought like a child, I reasoned like a child.
When I became a man, I gave up childish ways.

 

[unclerico]

try sourcing your icmp traffic from the inside. you need to generate the traffic from the ranges that have been deemed interesting by your crypto acl which is why your pings work from a host on the inside to another host on the opposite end of the tunnel.

 

[njjimbo]

Try the following:
config t
management-access inside
end
ping inside x.x.x.x

With Management-access, you can ping the ASA over the VPN, as well as SSH/Telnet/ASDM over to it assuming the appropriate telnet/ssh/http lines are in the config.

In order to ping over the VPN tunnel, you will then need to use ping inside to specify the source interface for the traffic, as your tunnel is set for the inside addresses, not the WAN IP of the ASA.

 

[MandyDroid]

Thank you both unclerico and njjimbo! sourcing the ping request from the inside interface has helped me greatly. I now feel like this network thing is going to work. I had hit a roadblocknot being able to manage this device3 from accross the VPN (where I sit).

Adding the management-access inside has enabled me to use ASDM accross my tunnel. Also sourcing the ping request from the inside interface does now allow PING to work accross the tunnel.

Avaya, Panasonic, Polycom, APC, MCP, A+, CCENT
##################################
"When I was a child, I spoke like a child, I thought like a child, I reasoned like a child.
When I became a man, I gave up childish ways.

 

[handle2110]

Hello

I have two locations with on both sides a Cisco ASA with a ipsec tunnel

Now we created a SSL VPN Login Page with bookmarks to our terminal servers.
On Location A where the asa has an SSL Portal we can connect to this server with remotedesktop over the SSL Connection.
We also want in the same portal connect to the other terminal sever witch is behind the second asa but we don't get any connection.
Between the asa's is an ipsec tunnel and internal is this working fine.

What we want:
RDP with the ssl vpn portal to the server 192.168.46.2