PIX - ASA, allow RA VPN clients to access servers at remote sites
I got L2L tunnels set up for a couple of remote sites (PIX) for several months now. We have a VPN concentrator, which will go EOL soon, so I'm working on moving our existing customers of RA our ASA. I have a problem, allowing RA clients access to a server to one of our remote sites. PIX and ASA (main site) relevant config is shown below. The error I get on the remote PIX when you try a ping on the VPN client is:
Group = 204.14. *. *, IP = 204.14. *. * cheque card static Crypto Card = outside_map, seq = 40, ACL does not proxy IDs src:172.16.200.0 dst: 172.16.26.0
The config:
Hand ASA config
access extensive list ip 172.16.0.0 inside_nat0_outbound allow 255.255.255.0 172.16.26.0 255.255.255.0
access extensive list ip 172.16.1.0 inside_nat0_outbound allow 255.255.255.0 172.16.26.0 255.255.255.0
access extensive list ip 172.16.22.0 inside_nat0_outbound allow 255.255.255.0 172.16.26.0 255.255.255.0
access extensive list ip 172.16.200.0 inside_nat0_outbound allow 255.255.255.0 172.16.26.0 255.255.255.0
access extensive list ip 172.16.0.0 inside_nat0_outbound allow 255.255.255.0 172.16.200.0 255.255.255.0
access extensive list ip 172.16.0.0 outside_cryptomap_60 allow 255.255.255.0 172.16.26.0 255.255.255.0
access extensive list ip 172.16.1.0 outside_cryptomap_60 allow 255.255.255.0 172.16.26.0 255.255.255.0
access extensive list ip 172.16.22.0 outside_cryptomap_60 allow 255.255.255.0 172.16.26.0 255.255.255.0
access extensive list ip 172.16.200.0 outside_cryptomap_60 allow 255.255.255.0 172.16.26.0 255.255.255.0
card crypto outside_map 60 match address outside_cryptomap_60
outside_map 60 set crypto map peer 24.97. *. *
card crypto outside_map 60 the transform-set ESP-3DES-MD5 value
map outside_map 65535-isakmp ipsec crypto dynamic outside_dyn_map
outside_map interface card crypto outside
=========================================
Remote config PIX
access extensive list ip 172.16.26.0 inside_nat0_outbound allow 255.255.255.0 172.16.0.0 255.255.255.0
access extensive list ip 172.16.26.0 inside_nat0_outbound allow 255.255.255.0 172.16.1.0 255.255.255.0
access extensive list ip 172.16.26.0 inside_nat0_outbound allow 255.255.255.0 172.16.22.0 255.255.255.0
access extensive list ip 172.16.26.0 inside_nat0_outbound allow 255.255.255.0 172.16.200.0 255.255.255.0
access extensive list ip 172.16.26.0 outside_cryptomap_60 allow 255.255.255.0 172.16.0.0 255.255.255.0
access extensive list ip 172.16.26.0 outside_cryptomap_60 allow 255.255.255.0 172.16.1.0 255.255.255.0
access extensive list ip 172.16.26.0 outside_cryptomap_60 allow 255.255.255.0 172.16.22.0 255.255.255.0
access extensive list ip 172.16.26.0 outside_cryptomap_60 allow 255.255.255.0 172.16.200.0 255.255.255.0
card crypto outside_map 60 match address outside_cryptomap_60
peer set card crypto outside_map 60 204.14. *. *
card crypto outside_map 60 the transform-set ESP-3DES-MD5 value
outside_map interface card crypto outside
EDIT: Guess, I might add, remote site is 172.16.26.0/24 VLAN VPN is 172.16.200.0/24...
What you want to do is 'tunnelall', which is not split tunneling. This will still allow customers to join the main and remote site, but not allow them to access internet... unless you have expressly authorized to make a 'nat (outside)"or something. Your journey on the client will be, Secured route 0.0.0.0 0.0.0.0
attributes of group policy
Split-tunnel-policy tunnelall
Who is your current config, I don't see where the acl of walton is attributed to what to split tunnel?
Tags: Cisco Security
Similar Questions
-
Filtering of VPN and local access to the remote site
Hello
I set up vpn, filtering on all my VPN l2l. I have limited access to remote resources at the local level to the specified ports. It works perfectly.
But I want to have as full access from local to remote networks (but still retain the remote access to the local level). VPN filter now works as I have two-way with a simple ACL. So is it possible to open all the traffic from the local to remote and all by limiting the remote to the local traffic?
ASA 5520 8.4 (3)
Thanks in advance
Tomasz Mowinski
Hello
Well let's say you have a filtering ACL rule when you allow http local network traffic to the remote host
LAN: 10.10.10.0/24
remote host: 192.168.10.10/32
The filter ACL rule is the following:
FILTER-ACL access-list permit tcp host 192.168.10.10 eq 80 10.10.10.0 255.255.255.0
I think that this ACL rule would mean also that until the remote host has been using source port TCP/80, it may access any port on any host tcp in your local network as long as it uses the source TCP/80 port.
I guess you could add a few ranges of ports or even service groups of objects to the ACL rules so that not all well-known ports would be accessible on the LAN. But I guess that could complicate the configurations.
We are usually management customer and completely different in ASA L2L VPN that allows us to all traffic on another filtering device and do not work in this kind of problems. But of course there are some of the situations/networks where this is not only possible and it is not a feasible option for some because of the costs of having an ASA extra.
Please indicate if you have found any useful information
-Jouni
-
The VPN Clients cannot access any internal address
Without a doubt need help from an expert on this one...
Attempting to define a client access on an ASA 5520 VPN that was used only as a
Firewall so far. The ASA has been recently updated to Version 7.2 (4).
Problem: Once connected, VPN client cannot access anything whatsoever. Client VPN cannot
ping any address on internal networks, or even the inside interface of the ASA.
(I hope) Relevant details:
(1) the tunnel seems to be upward. Customers are the authenticated by the SAA and
are able to connect.
(2) by many other related posts, I ran a ' sh crypto ipsec her "to see the output: it
appears that the packets are décapsulés and decrypted, but NOT encapsulated or
encrypted (see the output of "sh crypto ipsec his ' home).
(3) by the other related posts, we've added commands associated with inversion of NAT (crypto
ISAKMP nat-traversal 20
crypto ISAKMP ipsec-over-port tcp 10000). These were in fact absent from our
Configuration.
(4) we tried encapsulation TCP and UDP encapsulation with experimental client
profiles: same result in both cases.
(5) if I (attempt) ping to an internal IP address of the connected customer, the
real-time log entries ASA show the installation and dismantling of the ICMP requests to the
the inner target customer.
(6) the capture of packets to the internal address (one that we try to do a ping of the)
VPN client) shows that the ICMP request has been received and answered. (See attachment
shooting).
(7) our goal is to create about 10 VPN client of different profiles, each with
different combinations of access to the internal VLAN or DMZ VLAN. We do not have
preferences for the type of encryption or method, as long as it is safe and it works: that
said, do not hesitate to recommend a different approach altogether.
We have tried everything we can think of, so any help or advice would be greatly
Sanitized the ASA configuration is also attached.
appreciated!
Thank you!
It should be the last step :)
on 6509
IP route 172.16.100.0 255.255.255.0 172.16.20.2
and ASA
no road inside 172.16.40.0 255.255.255.0 172.16.20.2
-
The VPN Clients need access to the subnet on another router
Hello
We have a pix 515e PIX Version 8.0 (2)
We have two subnet 10.1.x.x/16 and 10.2.x.x/16
The firewall is on 10.1.x.x and vpn clients can access this subnet.
The firewall can ping 10.2.x.y where x is a server in the other subnet.
On the 10.2.x.x customers out the firewall.
The problem is that vpn clients cannot access the server of 10.2.x.y even if the pix can ping 10.2.x.y and the road for him.
What I need to check that the vpn rules are correct in the pix 515e?
I think it is a rule of exemption nat or something like that not exactly sure.
Everything would be a great help.
Thank you
Hello
For clients VPN access to these subnets, check the following:
1 NAT exemption include these subnets (if not using NAT)... it's the NAT0 ACL command
2. these subnets is included in the split tunneling
3. these subnets have a route to the PIX to send traffic to the VPN client pool.
4. There are no ACLs not applied to the inside interface of the PIX deny this communication.
Federico.
-
How to configure ASA as EZ - vpn client?
How can I configure ASA as Ez - vpn client?
Only ASA 5505 can be configured as a client VPN EZ.
Here's a few example configuration:
http://www.Cisco.com/en/us/docs/security/ASA/asa80/configuration/guide/ezvpn505.html
Hope that helps.
-
VPN clients cannot access to the vlan
Hello
I just changed my flat lan to a virtual LAN environment multi, but now I need help to get to my VPN back working again as the VPN user can access servers that are not on the vlan 'door '. I've read enough to know that it is probably associated with NAT, but I'm not sure where to put this information.
Does go in the NAT, associated with the E0 interface (outgoing internet gateway), to the vlan10 (vlan router is actually on) or can I create a new one and apply it to the crypto ipsec and isakmp side of things that use VPN users?
My network is configured as such...
VPN client - Router1811 - split trunk - C3550 - 12G - shared - resources multiple C3550s - servers/Wstns
The router subnet 192.168.10.0 as all switches, VLAN is set up through the 12 G and all other switches as vtp "vtp clients", including the router. The user can get to the 10 subnet and any server on it, but not to the"farm" on the subnet 192.168.11.0.
I noticed Federico has been working on something very similar to this... but any help would be appreciated.
Thank you, Don
Hi Don,
Please mark this discussion as resolved if there is no other problem with this VPN.
See you soon,.
Nash.
-
VPN clients hairpining through a tunnel from site to site
I have a 8.2 (5) ASA 5510 in Site1 and a 8.2 (1) ASA 5505 Site2 they are configured with a tunnel from site to site.
Each site has VPN clients that connect and I would like to allow customers to access on both sides across the site-to-site tunnel servers.
I enabled same-security-traffic permit intra-interface I also added the remote networks to access list who made the split tunneling.
I think I'm doing something wrong with nat, but I don't know, any help would be greatly appreciated.
Site1 Clients1 (172.17.2.0/24) (10.0.254.0/24)
ASA Version 8.2 (5)
!
hostname site1
names of
DNS-guard
!
interface Ethernet0/0
nameif outside
security-level 0
IP address site1 255.255.255.240
!
interface Ethernet0/1
nameif inside
security-level 100
IP 172.17.2.1 255.255.255.0
!
interface Ethernet0/2
Shutdown
nameif DMZ
security-level 0
IP 10.10.10.1 255.255.255.0
!
interface Ethernet0/3
Shutdown
No nameif
no level of security
no ip address
!
interface Management0/0
nameif management
security-level 0
IP 192.168.1.1 255.255.255.0
management only
!
passive FTP mode
permit same-security-traffic intra-interface
VPN - UK wide ip 172.17.2.0 access list allow 255.255.255.0 172.18.2.0 255.255.255.0
access extensive list ip 172.17.2.0 inside_nat0_outbound allow 255.255.255.0 192.168.123.0 255.255.255.0
access extensive list ip 172.17.2.0 inside_nat0_outbound allow 255.255.255.0 172.18.2.0 255.255.255.0
access extensive list ip 172.17.2.0 inside_nat0_outbound allow 255.255.255.0 10.0.254.0 255.255.255.0
Notice of inside_nat0_outbound access-list us Client Server UK
access extensive list ip 10.0.254.0 inside_nat0_outbound allow 255.255.255.0 172.18.2.0 255.255.255.0
access extensive list ip 192.168.123.0 inside_nat0_outbound allow 255.255.255.0 10.0.254.0 255.255.255.0
access extensive list ip 172.18.2.0 inside_nat0_outbound allow 255.255.255.0 10.0.254.0 255.255.255.0
Standard access list Split_Tunnel_List allow 172.17.2.0 255.255.255.0
Standard access list Split_Tunnel_List allow 172.18.2.0 255.255.255.0
Split_Tunnel_List list standard access allowed 192.168.123.0 255.255.255.0
Split_Tunnel_List of access note list UK VPN Client pool
Standard access list Split_Tunnel_List allow 172.255.2.0 255.255.255.0
outside-2 extended access list permit tcp any any eq smtp
outside-2 extended access list permit tcp any any eq 82
outside-2 extended access list permit tcp any any eq 81
outside-2 extended access list permit tcp everything any https eq
outside-2 extended access list permit tcp any any eq imap4
outside-2 extended access list permit tcp any any eq ldaps
outside-2 extended access list permit tcp any any eq pop3
outside-2 extended access list permit tcp any any eq www
outside-2 extended access list permit tcp any any eq 5963
outside-2 extended access list permit tcp any any eq ftp
outside-2 allowed extended access list tcp any any eq ftp - data
outside-2 extended access list permit tcp any any eq 3389
list of access outside-2 extended tcp refuse any any newspaper
2-outside access list extended deny ip any any newspaper
outside-2 extended access list deny udp any any newspaper
allow VPN CLIENTS to access extended list ip 172.17.2.0 255.255.255.0 10.0.254.0 255.255.255.0
allow VPN CLIENTS to access extended list ip 172.18.2.0 255.255.255.0 10.0.254.0 255.255.255.0
allow VPN CLIENTS to access extended list 192.168.123.0 ip 255.255.255.0 10.0.254.0 255.255.255.0
Standard access list VPNClient_splittunnel allow 172.17.2.0 255.255.255.0
Standard access list VPNClient_splittunnel allow 172.18.2.0 255.255.255.0
VPNClient_splittunnel list standard access allowed 192.168.123.0 255.255.255.0
VPNClient_splittunnel of access note list UK VPN Client pool
Standard access list VPNClient_splittunnel allow 172.255.2.0 255.255.255.0
VPN-Northwoods extended ip 172.17.2.0 access list allow 255.255.255.0 192.168.123.0 255.255.255.0
Note to outside_nat0_outbound to access list AD 01/05/13
access extensive list ip 10.0.254.0 outside_nat0_outbound allow 255.255.255.0 172.18.2.0 255.255.255.0
pager lines 24
Enable logging
debug logging in buffered memory
asdm of logging of information
Outside 1500 MTU
Within 1500 MTU
MTU 1500 DMZ
management of MTU 1500
mask 10.0.254.25 - 10.0.254.45 255.255.255.0 IP local pool VPNUserPool
ICMP unreachable rate-limit 1 burst-size 1
don't allow no asdm history
ARP timeout 14400
NAT-control
Global 1 interface (outside)
NAT (outside) 0-list of access outside_nat0_outbound
NAT (inside) 0-list of access inside_nat0_outbound
NAT (inside) 1 172.17.2.0 255.255.255.0
public static tcp (indoor, outdoor) interface smtp 172.17.2.200 smtp netmask 255.255.255.255
public static tcp (indoor, outdoor) interface 82 172.17.2.253 82 netmask 255.255.255.255
public static tcp (indoor, outdoor) interface 81 192.168.123.253 81 netmask 255.255.255.255
public static tcp (indoor, outdoor) interface https 172.17.2.10 https netmask 255.255.255.255
public static tcp (indoor, outdoor) interface 172.17.2.10 imap4 imap4 netmask 255.255.255.255
public static tcp (indoor, outdoor) interface ldaps 172.17.2.10 ldaps netmask 255.255.255.255
public static tcp (indoor, outdoor) interface 172.17.2.10 pop3 pop3 netmask 255.255.255.255
public static tcp (indoor, outdoor) interface www 172.17.2.19 www netmask 255.255.255.255
public static tcp (indoor, outdoor) interface 5963 172.17.2.108 5963 netmask 255.255.255.255
public static tcp (indoor, outdoor) interface ftp 172.17.2.7 ftp netmask 255.255.255.255
public static tcp (indoor, outdoor) interface ftp - data 172.17.2.7 ftp - data netmask 255.255.255.255
static (inside, outside) tcp 3389 172.17.2.29 interface 3389 netmask 255.255.255.255
Access-group 2-outside-inside in external interface
Route outside 0.0.0.0 0.0.0.0 74.213.51.129 1
Timeout xlate 03:00
Timeout conn 01:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00
Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-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
Floating conn timeout 0:00:00
dynamic-access-policy-registration DfltAccessPolicy
RADIUS protocol AAA-server DCSI_Auth
AAA-server host 172.17.2.29 DCSI_Auth (inside)
key *.
AAA-server protocol nt AD
AAA-server AD (inside) host 172.16.1.211
AAA-server AD (inside) host 172.17.2.29
the ssh LOCAL console AAA authentication
No snmp server location
No snmp Server contact
Server enable SNMP traps snmp authentication linkup, linkdown cold start
Crypto ipsec transform-set esp - esp-sha-hmac trans_set
Crypto ipsec transform-set VPN-Client-esp-3des esp-sha-hmac
life crypto ipsec security association seconds 28800
Crypto ipsec kilobytes of life - safety 4608000 association
Crypto dynamic-map DYN_MAP 20 the value reverse-road
Crypto-map dynamic outside_dyn_map 20 game of transformation-VPN-Client
address for correspondence outside_map 20 card crypto VPN - UK
card crypto outside_map 20 peers set site2
card crypto outside_map 20 transform-set trans_set
address for correspondence outside_map 30 card crypto VPN-Northwoods
card crypto outside_map 30 peers set othersite
trans_set outside_map 30 transform-set card crypto
map outside_map 65535-isakmp ipsec crypto dynamic outside_dyn_map
outside_map interface card crypto outside
Crypto ca trustpoint _SmartCallHome_ServerCA
Configure CRL
crypto isakmp identity address
crypto ISAKMP allow outside
crypto ISAKMP policy 10
preshared authentication
the Encryption
sha hash
Group 2
lifetime 28800
crypto ISAKMP policy 20
preshared authentication
the Encryption
md5 hash
Group 2
lifetime 28800
Telnet timeout 5
SSH timeout 60
Console timeout 0
management of 192.168.1.2 - dhcpd address 192.168.1.254
enable dhcpd management
!
a basic threat threat detection
Statistics-list of access threat detection
no statistical threat detection tcp-interception
WebVPN
internal Clients_vpn group strategy
attributes of strategy of group Clients_vpn
value of server DNS 10.0.1.30
Protocol-tunnel-VPN IPSec
Split-tunnel-policy tunnelspecified
value of Split-tunnel-network-list VPNClient_splittunnel
domain.local value by default-field
the authentication of the user activation
tunnel-group VPNclient type remote access
tunnel-group VPNclient-global attributes
address pool VPNUserPool
authentication-server-group DCSI_Auth
strategy - by default-group Clients_vpn
tunnel-group VPNclient ipsec-attributes
pre-shared key *.
tunnel-group othersite type ipsec-l2l
othersite group tunnel ipsec-attributes
pre-shared key *.
tunnel-group site2 type ipsec-l2l
tunnel-group ipsec-attributes site2
pre-shared key *.
!
class-map inspection_default
match default-inspection-traffic
class-map imblock
match any
class-map p2p
game port tcp eq www
class-map P2P
game port tcp eq www
!
!
type of policy-card inspect dns preset_dns_map
parameters
maximum message length automatic of customer
message-length maximum 512
type of policy-map inspect im bine
parameters
msn - im yahoo im Protocol game
drop connection
Policy-map global_policy
class inspection_default
inspect the preset_dns_map dns
inspect the ftp
inspect h323 h225
inspect the h323 ras
inspect the rsh
inspect the rtsp
inspect esmtp
inspect sqlnet
inspect the skinny
inspect sunrpc
inspect xdmcp
inspect the sip
inspect the netbios
inspect the tftp
Review the ip options
inspect the pptp
type of policy-card inspect http P2P_HTTP
parameters
matches the query uri regex _default_gator
Journal of the drop connection
football match request uri regex _default_x-kazaa-network
Journal of the drop connection
Policy-map IM_P2P
class imblock
inspect the im bine
class P2P
inspect the http P2P_HTTP
!
global service-policy global_policy
IM_P2P service-policy inside interface
context of prompt hostname
no remote anonymous reporting call
Cryptochecksum:7717a11f5f2dce11af0f35cee7b4c893
: end
Site2 Clients1 (172.18.2.0/24) (172.255.2.0/24)
ASA Version 8.2 (1)
!
names of
name 172.18.2.2 UKserver
!
interface Vlan1
nameif inside
security-level 100
IP 172.18.2.1 255.255.255.0
!
interface Vlan2
nameif GuestWiFi
security-level 0
IP 192.168.2.1 255.255.255.0
!
interface Vlan3
nameif outside
security-level 0
IP address site2 255.255.255.252
!
interface Ethernet0/0
switchport access vlan 3
!
interface Ethernet0/1
!
interface Ethernet0/2
switchport trunk allowed vlan 1-2
switchport vlan trunk native 2
switchport mode trunk
Speed 100
full duplex
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
!
interface Ethernet0/6
!
interface Ethernet0/7
!
passive FTP mode
permit same-security-traffic intra-interface
Access extensive list ip 172.18.2.0 USER_VPN allow 255.255.255.0 172.255.2.0 255.255.255.0
Access extensive list ip 172.17.2.0 USER_VPN allow 255.255.255.0 172.255.2.0 255.255.255.0
Standard access list VPNClient_splittunnel allow 172.18.2.0 255.255.255.0
Standard access list VPNClient_splittunnel allow 172.17.2.0 255.255.255.0
Standard access list VPNClient_splittunnel allow 172.255.2.0 255.255.255.0
Outside_2_Inside list extended access permit tcp any host otherhost eq smtp
Outside_2_Inside list extended access permit tcp any host otherhost eq pop3
Outside_2_Inside list extended access permit tcp any host otherhost eq imap4
Outside_2_Inside list extended access permit tcp any host otherhost eq www
Outside_2_Inside list extended access permit tcp any host otherhost eq https
Outside_2_Inside list extended access permit tcp any host otherhost eq ldap
Outside_2_Inside list extended access permit tcp any host otherhost eq ldaps
Outside_2_Inside list extended access permit tcp any host otherhost eq nntp
Outside_2_Inside list extended access permit tcp any host otherhost eq 135
Outside_2_Inside list extended access permit tcp any host otherhost eq 102
Outside_2_Inside list extended access permit tcp any host otherhost eq 390
Outside_2_Inside list extended access permit tcp any host otherhost eq 3268
Outside_2_Inside list extended access permit tcp any host otherhost eq 3269
Outside_2_Inside list extended access permit tcp any host otherhost eq 993
Outside_2_Inside list extended access permit tcp any host otherhost eq 995
Outside_2_Inside list extended access permit tcp any host otherhost eq 563
Outside_2_Inside list extended access permit tcp any host otherhost eq 465
Outside_2_Inside list extended access permit tcp any host otherhost eq 691
Outside_2_Inside list extended access permit tcp any host otherhost eq 6667
Outside_2_Inside list extended access permit tcp any host otherhost eq 994
Outside_2_Inside access list extended icmp permitted an echo
Outside_2_Inside list extended access permit icmp any any echo response
Outside_2_Inside list extended access permit tcp any host site2 eq smtp
Outside_2_Inside list extended access permit tcp any host site2 eq pop3
Outside_2_Inside list extended access permit tcp any host site2 eq imap4
Outside_2_Inside list extended access permit tcp any host site2 eq www
Outside_2_Inside list extended access permit tcp any host site2 eq https
Outside_2_Inside list extended access permit tcp any host site2 eq ldap
Outside_2_Inside list extended access permit tcp any host site2 eq ldaps
Outside_2_Inside list extended access permit tcp any host site2 eq nntp
Outside_2_Inside list extended access permit tcp any host site2 eq 135
Outside_2_Inside list extended access permit tcp any host site2 eq 102
Outside_2_Inside list extended access permit tcp any host site2 eq 390
Outside_2_Inside list extended access permit tcp any host site2 eq 3268
Outside_2_Inside list extended access permit tcp any host site2 eq 3269
Outside_2_Inside list extended access permit tcp any host site2 eq 993
Outside_2_Inside list extended access permit tcp any host site2 eq 995
Outside_2_Inside list extended access permit tcp any host site2 eq 563
Outside_2_Inside list extended access permit tcp any host site2 eq 465
Outside_2_Inside list extended access permit tcp any host site2 eq 691
Outside_2_Inside list extended access permit tcp any host site2 eq 6667
Outside_2_Inside list extended access permit tcp any host site2 eq 994
Outside_2_Inside list extended access permit tcp any SIP EQ host site2
Outside_2_Inside list extended access permit tcp any range of 8000-8005 host site2
Outside_2_Inside list extended access permit udp any range of 8000-8005 host site2
Outside_2_Inside list extended access udp allowed any SIP EQ host site2
Outside_2_Inside tcp extended access list deny any any newspaper
Outside_2_Inside list extended access deny udp any any newspaper
VPN - USA 172.255.2.0 ip extended access list allow 255.255.255.0 172.17.2.0 255.255.255.0
access extensive list ip 172.18.2.0 inside_nat0_outbound allow 255.255.255.0 172.17.2.0 255.255.255.0
access extensive list ip 172.18.2.0 inside_nat0_outbound allow 255.255.255.0 172.255.2.0 255.255.255.0
access extensive list ip 172.255.2.0 inside_nat0_outbound allow 255.255.255.0 172.17.2.0 255.255.255.0
Comment by Split_Tunnel_List-list of access networks to allow via VPN
Standard access list Split_Tunnel_List allow 172.18.2.0 255.255.255.0
Standard access list Split_Tunnel_List allow 172.17.2.0 255.255.255.0
Standard access list Split_Tunnel_List allow 172.255.2.0 255.255.255.0
Standard access list Split_Tunnel_List allow 10.0.254.0 255.255.255.0
pager lines 20
Enable logging
monitor debug logging
debug logging in buffered memory
asdm of logging of information
Debugging trace record
Within 1500 MTU
MTU 1500 GuestWiFi
Outside 1500 MTU
IP pool local ClientVPN 172.255.2.100 - 172.255.2.124
no failover
ICMP unreachable rate-limit 1 burst-size 1
ASDM image disk0: / asdm - 621.bin
don't allow no asdm history
ARP timeout 14400
NAT-control
Global 1 interface (outside)
NAT (inside) 0-list of access inside_nat0_outbound
NAT (inside) 1 172.18.2.0 255.255.255.0
NAT (GuestWiFi) 2 192.168.2.0 255.255.255.0
public static tcp (indoor, outdoor) interface smtp smtp UKserver netmask 255.255.255.255
public static tcp (indoor, outdoor) UKserver netmask 255.255.255.255 pop3 pop3 interface
public static tcp (indoor, outdoor) interface imap4 imap4 netmask 255.255.255.255 UKserver
public static tcp (indoor, outdoor) interface www UKserver www netmask 255.255.255.255
public static tcp (indoor, outdoor) https UKserver netmask 255.255.255.255 https interface
public static tcp (indoor, outdoor) interface ldap UKserver ldap netmask 255.255.255.255
public static tcp (indoor, outdoor) interface ldaps ldaps netmask 255.255.255.255 UKserver
public static tcp (indoor, outdoor) interface nntp nntp netmask 255.255.255.255 UKserver
public static 135 135 UKserver netmask 255.255.255.255 interface tcp (indoor, outdoor)
public static 102 102 UKserver netmask 255.255.255.255 interface tcp (indoor, outdoor)
public static 390 390 UKserver netmask 255.255.255.255 interface tcp (indoor, outdoor)
public static 3268 3268 UKserver netmask 255.255.255.255 interface tcp (indoor, outdoor)
public static 3269 3269 UKserver netmask 255.255.255.255 interface tcp (indoor, outdoor)
public static UKserver netmask 255.255.255.255 993 993 interface tcp (indoor, outdoor)
public static UKserver 995 netmask 255.255.255.255 995 interface tcp (indoor, outdoor)
public static 563 563 UKserver netmask 255.255.255.255 interface tcp (indoor, outdoor)
public static 465 465 UKserver netmask 255.255.255.255 interface tcp (indoor, outdoor)
public static 691 691 UKserver netmask 255.255.255.255 interface tcp (indoor, outdoor)
public static 6667 UKserver 6667 netmask 255.255.255.255 interface tcp (indoor, outdoor)
public static 994 994 UKserver netmask 255.255.255.255 interface tcp (indoor, outdoor)
Access-group Outside_2_Inside in interface outside
Route outside 0.0.0.0 0.0.0.0 87.224.93.53 1
Timeout xlate 03:00
Timeout conn 01:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00
Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-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
dynamic-access-policy-registration DfltAccessPolicy
Ray of AAA-server vpn Protocol
AAA-server vpn (inside) host UKserver
key DCSI_vpn_Key07
the ssh LOCAL console AAA authentication
Enable http server
No snmp server location
No snmp Server contact
Server enable SNMP traps snmp authentication linkup, linkdown cold start
Crypto ipsec transform-set esp - esp-sha-hmac trans_set
life crypto ipsec security association seconds 28800
Crypto ipsec kilobytes of life - safety 4608000 association
Crypto-map dynamic outside_dyn_map 20 transform-set trans_set
Crypto dynamic-map DYN_MAP 20 the value reverse-road
address for correspondence outside_map 20 card crypto VPN - USA
card crypto outside_map 20 peers set othersite2 site1
card crypto outside_map 20 transform-set trans_set
map outside_map 65535-isakmp ipsec crypto dynamic outside_dyn_map
outside_map interface card crypto outside
crypto isakmp identity address
crypto ISAKMP allow outside
crypto ISAKMP policy 10
preshared authentication
the Encryption
sha hash
Group 2
lifetime 28800
crypto ISAKMP policy 20
preshared authentication
the Encryption
md5 hash
Group 2
lifetime 28800
Telnet timeout 5
SSH timeout 25
Console timeout 0
dhcpd dns 8.8.8.8 UKserver
!
dhcpd address 172.18.2.100 - 172.18.2.149 inside
dhcpd allow inside
!
dhcpd address 192.168.2.50 - 192.168.2.74 GuestWiFi
enable GuestWiFi dhcpd
!
no basic threat threat detection
no statistical access list - a threat detection
no statistical threat detection tcp-interception
WebVPN
internal USER_VPN group policy
USER_VPN group policy attributes
Protocol-tunnel-VPN IPSec
Split-tunnel-policy tunnelspecified
value of Split-tunnel-network-list Split_Tunnel_List
the authentication of the user activation
tunnel-group othersite2 type ipsec-l2l
othersite2 group of tunnel ipsec-attributes
pre-shared-key *.
type tunnel-group USER_VPN remote access
attributes global-tunnel-group USER_VPN
address pool ClientVPN
Authentication-server group (external vpn)
Group Policy - by default-USER_VPN
IPSec-attributes tunnel-group USER_VPN
pre-shared-key *.
tunnel-group site1 type ipsec-l2l
tunnel-group ipsec-attributes site1
pre-shared-key *.
!
class-map inspection_default
match default-inspection-traffic
!
!
type of policy-card inspect dns preset_dns_map
parameters
message-length maximum 512
Policy-map global_policy
class inspection_default
inspect the preset_dns_map dns
inspect the ftp
inspect the rsh
inspect the rtsp
inspect sqlnet
inspect the skinny
inspect sunrpc
inspect xdmcp
inspect the tftp
!
global service-policy global_policy
context of prompt hostname
Cryptochecksum:d000c75c8864547dfabaf3652d81be71
: end
Hello
The output seems to say that traffic is indeed transmitted to connect VPN L2L
Can you PING from hosts on the network 172.18.2.0/24 to the hosts on the network 172.17.2.0/24?
Have you tried several different target hosts on the network you are trying to ping while might exclude us actual devices are not just meeting the specifications these PINGs?
-Jouni
-
VPN clients cannot access remote sites - PIX, routing problem?
I have a problem with routing to remote from our company websites when users connect via their VPN client remotely (i.e. for home workers)
Our headquarters contains a PIX 515E firewall. A number of remote sites to connect (via ADSL) to head office using IPSEC tunnels, ending the PIX.
Behind the PIX is a router 7206 with connections to the seat of LANs and connections to a number of ISDN connected remote sites. The default route on 7206 points to the PIX from traffic firewall which sits to ADSL connected remote sites through the PIX. Internal traffic for LAN and ISDN connected sites is done via the 7206.
Very good and works very well.
When a user connects remotely using their VPN client (connection is interrupted on the PIX) so that they get an IP address from the pool configured on the PIX and they can access resources located on local networks to the office with no problems.
However, the problem arises when a remote user wants access to a server located in one of the remote sites ADSL connected - it is impossible to access all these sites.
On the remote site routers, I configured the access lists to allow access from the pool of IP addresses used by the PIX. But it made no difference. I think that the problem may be the routes configured on the PIX itself, but I don't know what is necessary to solve this problem.
Does anyone have suggestions on what needs to be done to allow access to remote sites for users connected remotely via VPN?
(Note: I suggested a workaround, users can use a server on LAN headquarters as a "jump point" to connect to remote servers from there)
with pix v6, no traffic is allowed to redirect to the same interface.
for example, a remote user initiates an rdp session for one of the barns adsl. PIX decrypts the packet coming from the external interface and looks at the destination. because the destination is one of adsl sites, pix will have to return traffic to the external interface. Unfortunately, pix v6.x has a limitation that would force the pix to drop the packet.
with the v7, this restriction has been removed with the "same-security-traffic control intra-interface permits".
-
Why my VPN clients cannot access network drives and resources?
I have a cisco asa 5505 configured to be a VPN gateway. I can dial using the anyconnect VPN client. The remote user is assigned an IP address to my specifications. However... The remote user cannot access network such as disks in network resources or the fax server. I've done everything I can to set the right settings NAT and ACLs, but in vain. I write my config... If someone can track down the problem. It would be appreciated!
: Saved
:
ASA Version 8.2 (5)
!
ciscoasa hostname
Cisco domain name
activate the password xxxxxxxxxxxxx
passwd xxxxxxxxxxxxxxxxx
names of
name 68.191.xxx.xxx outdoors
!
interface Ethernet0/0
switchport access vlan 2
!
interface Ethernet0/1
!
interface Ethernet0/2
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
!
interface Ethernet0/6
!
interface Ethernet0/7
!
interface Vlan1
nameif inside
security-level 100
IP 192.168.201.200 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
IP address outside 255.255.255.0
!
passive FTP mode
DNS domain-lookup outside
DNS lookup field inside
DNS server-group DefaultDNS
192.168.201.1 server name
Cisco domain name
permit same-security-traffic inter-interface
permit same-security-traffic intra-interface
object-group Protocol TCPUDP
object-protocol udp
object-tcp protocol
object-group network obj - 192.168.201.0
FREE access-list extended ip 192.168.201.0 NAT allow 255.255.255.0 192.168.201.0 255.255.255.0
NAT-FREE 192.168.202.0 permits all ip extended access list 255.255.255.0
FREE access-list extended ip 192.168.202.0 NAT allow 255.255.255.0 any
Extended access list-NAT-FREE enabled a whole icmp
allow any scope to an entire ip access list
allow any scope to the object-group TCPUDP an entire access list
allow any scope to an entire icmp access list
inside_access_in of access allowed any ip an extended list
inside_access_in list extended access allow TCPUDP of object-group a
inside_access_in list extended access permit icmp any one
outside_access_in of access allowed any ip an extended list
outside_access_in list extended access allow TCPUDP of object-group a
outside_access_in list extended access permit icmp any one
Standard access list DefaultRAGroup_splitTunnelAcl allow 192.168.201.0 255.255.255.0
access extensive list ip 192.168.202.0 inside_nat0_outbound allow 255.255.255.0 192.168.201.0 255.255.255.0
inside_nat0_outbound list extended access permit icmp any one
inside_nat0_outbound_1 of access allowed any ip an extended list
pager lines 24
Enable logging
asdm of logging of information
Outside 1500 MTU
Within 1500 MTU
mask 192.168.202.1 - 192.168.202.50 255.255.255.0 IP local pool KunduVPN
ICMP unreachable rate-limit 1 burst-size 1
don't allow no asdm history
ARP timeout 14400
NAT-control
Global 1 interface (outside)
NAT (inside) 0 inside_nat0_outbound_1 list of outdoor access
NAT (inside) 1 192.168.201.0 255.255.255.0
Access-group outside_access_in in interface outside
inside_access_in access to the interface inside group
Route inside 0.0.0.0 0.0.0.0 192.168.201.1 1
Route inside 0.0.0.0 255.255.255.255 outdoor 1
Timeout xlate 03:00
Timeout conn 01:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00
Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-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
Floating conn timeout 0:00:00
dynamic-access-policy-registration DfltAccessPolicy
Enable http server
http 192.168.201.0 255.255.255.0 inside
http 0.0.0.0 0.0.0.0 outdoors
No snmp server location
No snmp Server contact
Server enable SNMP traps snmp authentication linkup, linkdown cold start
Crypto ipsec transform-set esp-3des esp-sha-hmac TRANS_ESP_3DES_SHA
Crypto ipsec transform-set transit mode TRANS_ESP_3DES_SHA
Crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
Crypto ipsec transform-set ESP-DES-SHA esp - esp-sha-hmac
Crypto ipsec transform-set esp-SHA-ESP-3DES-3des esp-sha-hmac
Crypto ipsec transform-set ESP-DES-MD5 esp - esp-md5-hmac
Crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
Crypto ipsec transform-set ESP-3DES-MD5-esp-3des esp-md5-hmac
Crypto ipsec transform-set ESP-AES-256-SHA 256 - aes - esp esp-sha-hmac
Crypto ipsec transform-set ESP-AES-128-SHA aes - esp esp-sha-hmac
Crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
Crypto ipsec transform-set ESP-AES-128-MD5-esp - aes esp-md5-hmac
life crypto ipsec security association seconds 28800
Crypto ipsec kilobytes of life - safety 4608000 association
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 pfs Group1 set
Crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 value transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA MD5-ESP-3DES ESP-DES-SHA ESP-DES-MD5
outside_map card crypto 65535-isakmp dynamic ipsec SYSTEM_DEFAULT_CRYPTO_MAP
outside_map interface card crypto outside
Crypto ca trustpoint ASDM_TrustPoint0
registration auto
name of the object CN = ciscoasa
Keypairs xxx
Proxy-loc-transmitter
Configure CRL
XXXXXXXXXXXXXXXXXXXXXXXX
quit smoking
crypto ISAKMP allow outside
crypto ISAKMP allow inside
crypto ISAKMP policy 10
authentication crack
aes-256 encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 20
authentication rsa - sig
aes-256 encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 30
preshared authentication
aes-256 encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 40
authentication crack
aes-192 encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 50
authentication rsa - sig
aes-192 encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 60
preshared authentication
aes-192 encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 70
authentication crack
aes encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 80
authentication rsa - sig
aes encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 90
preshared authentication
aes encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 100
authentication crack
3des encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 110
authentication rsa - sig
3des encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 120
preshared authentication
3des encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 130
authentication crack
the Encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 140
authentication rsa - sig
the Encryption
sha hash
Group 2
life 86400
crypto ISAKMP policy 150
preshared authentication
the Encryption
sha hash
Group 2
life 86400
Telnet timeout 5
SSH timeout 5
Console timeout 0
dhcpd outside auto_config
!
a basic threat threat detection
Statistics-list of access threat detection
no statistical threat detection tcp-interception
SSL-trust outside ASDM_TrustPoint0 point
WebVPN
allow outside
allow inside
SVC disk0:/anyconnect-win-2.5.2014-k9.pkg 1 image
enable SVC
tunnel-group-list activate
internal DefaultRAGroup group strategy
attributes of Group Policy DefaultRAGroup
value of 192.168.201.1 DNS server
VPN-tunnel-Protocol svc webvpn
Split-tunnel-policy tunnelspecified
value of Split-tunnel-network-list DefaultRAGroup_splitTunnelAcl
Cisco by default field value
attributes of Group Policy DfltGrpPolicy
Protocol-tunnel-VPN IPSec l2tp ipsec svc webvpn
WebVPN
SVC request enable
internal KunduVPN group strategy
attributes of Group Policy KunduVPN
WINS server no
value of 192.168.201.1 DNS server
VPN-tunnel-Protocol svc webvpn
Cisco by default field value
username xxxx
username xxxxx
VPN-group-policy DfltGrpPolicy
attributes global-tunnel-group DefaultRAGroup
address VPNIP pool
Group Policy - by default-DefaultRAGroup
IPSec-attributes tunnel-group DefaultRAGroup
pre-shared key *.
tunnel-group DefaultRAGroup ppp-attributes
ms-chap-v2 authentication
type tunnel-group KunduVPN remote access
attributes global-tunnel-group KunduVPN
address (inside) VPNIP pool
address pool KunduVPN
authentication-server-group (inside) LOCAL
Group Policy - by default-KunduVPN
tunnel-group KunduVPN webvpn-attributes
enable KunduVPN group-alias
allow group-url https://68.191.xxx.xxx/KunduVPN
!
class-map inspection_default
match default-inspection-traffic
!
!
type of policy-card inspect dns preset_dns_map
parameters
maximum message length automatic of customer
message-length maximum 512
Policy-map global_policy
class inspection_default
inspect the preset_dns_map dns
inspect the ftp
inspect h323 h225
inspect the h323 ras
inspect the rsh
inspect the rtsp
inspect esmtp
inspect sqlnet
inspect the skinny
inspect sunrpc
inspect xdmcp
inspect the sip
inspect the netbios
inspect the tftp
Review the ip options
!
global service-policy global_policy
context of prompt hostname
no remote anonymous reporting call
Cryptochecksum:c0e4540d4a07f2c544f0eddb653627cc
: end
don't allow no asdm history
Hello
What is the IP address of the hosts/servers LAN Gateway?
If this is not the ASA 'inside' interface IP address then I assume that the problem with VPN is simply routing.
For example, if your hosts/servers LAN wireless LAN gateway router then the following would happen to your Clients VPN connections.
- Forms of customers login VPN users through configuring wireless routers static PAT (Port Forward) to interface "inside" ASA
- Client VPN sends traffic through the VPN to ASA and again the host of the server or LAN.
- Host/server LAN sees the connection from a network other than the LAN (192.168.202.0/24) and therefore to forward traffic to the default gateway that would likely be the wireless router.
- Wireless router has no route to the network 192.168.202.0/24 (VPN Pool) and therefore uses its default route to the external network to forward traffic.
- Client VPN host never received the traffic back as transmitted sound on the external network and abandoned by the ISP
So if the above assumption is correct, then you would at least need a configuration of the road on the wireless router that tells the device to transfer traffic to the network 192.168.202.0/24 to the 192.168.201.200 gateway IP address (which is the SAA)
I would like to know if the installation is as described above.
-Jouni
-
Allowing the VPN Clients to the management network - nat woes
Try to allow the VPNClient IPSEC access to the management network. packet trace stops on the vpn encrypt even through phase 7 States it's NAT EXEMPT, he said his tent still NAT by a static. The only thing I can think to put a rule of nat exempted for the subnet on the external interface.
Please notify. Thank you.
Phase: 1
Type: ACCESS-LIST
Subtype:
Result: ALLOW
Config:
Implicit rule
Additional information:
MAC access listPhase: 2
Type: FLOW-SEARCH
Subtype:
Result: ALLOW
Config:
Additional information:
Not found no corresponding stream, creating a new streamPhase: 3
Type:-ROUTE SEARCH
Subtype: entry
Result: ALLOW
Config:
Additional information:
in 0.0.0.0 0.0.0.0 outdoorsPhase: 4
Type: ACCESS-LIST
Subtype: Journal
Result: ALLOW
Config:
Access-group MANAGEMENT-IN in the management interface
access-list MANAGEMENT-IN-scope ip allowed any one
Additional information:Phase: 5
Type: IP-OPTIONS
Subtype:
Result: ALLOW
Config:
Additional information:Phase: 6
Type: FOVER
Subtype: Eve-updated
Result: ALLOW
Config:
Additional information:Phase: 7
Type: NAT-FREE
Subtype:
Result: ALLOW
Config:
match ip MANAGEMENT 10.10.10.0 255.255.255.0 outside 172.18.0.32 255.255.255.240
Exempt from NAT
translate_hits = 3, untranslate_hits = 33
Additional information:Phase: 8
Type: NAT
Subtype:
Result: ALLOW
Config:
static (MANAGEMENT, outside) 203.23.23.75 10.10.10.10 netmask 255.255.255.255
MANAGEMENT ip 10.10.10.10 host game OUTSIDE of any
static translation at 203.23.176.75
translate_hits = 0, untranslate_hits = 1
Additional information:Phase: 9
Type: NAT
Subtype: host-limits
Result: ALLOW
Config:
static (MANAGEMENT, outside) 203.23.23.75 10.10.10.10 netmask 255.255.255.255
MANAGEMENT ip 10.10.10.10 host game OUTSIDE of any
static translation at 203.23.23.75
translate_hits = 0, untranslate_hits = 1
Additional information:Phase: 10
Type: VPN
Subtype: encrypt
Result: DECLINE
Config:
Additional information:Result:
input interface: MANAGEMENT
entry status: to the top
entry-line-status: to the top
output interface: OUTSIDE
the status of the output: to the top
output-line-status: to the top
Action: drop
Drop-reason: flow (acl-drop) is denied by the configured rule-EXCERPT FROM CONFIG-
CorpVPN to access extended list ip 10.10.10.0 allow 255.255.255.0 172.18.0.32 255.255.255.240
Access extensive list ip 172.18.0.32 CorpVPN allow 255.255.255.240 10.10.10.0 255.255.255.0mask 172.18.0.33 - 172.18.0.46 255.255.255.240 IP local pool CorpVPN
access-list MANAGEMENT-extended permitted tcp 172.18.0.32 255.255.255.240 host 10.10.10.11 eq ssh
access-list MANAGEMENT-extended permitted tcp 172.18.0.32 255.255.255.240 host 10.10.10.10 eq ssh
access-list MANAGEMENT-extended permitted tcp 172.18.0.32 255.255.255.240 host 10.10.10.13 eq 3389access-list 101 extended allow ip 10.10.10.0 255.255.255.0 172.18.0.32 255.255.255.240
NAT 0 access-list (MANAGEMENT) No.-NAT-DU-MGMT
access-list no.-NAT-DU-MGMT scope ip 10.10.10.0 allow 255.255.255.0 172.18.0.32 255.255.255.240CorpVPN to access extended list ip 10.10.10.0 allow 255.255.255.0 172.18.0.32 255.255.255.240
Access extensive list ip 172.18.0.32 CorpVPN allow 255.255.255.240 allinternal CorpVPN group strategy
attributes of Group Policy CorpVPN
value of server DNS 203.23.23.23
VPN - connections 8
VPN-idle-timeout 720
Protocol-tunnel-VPN IPSec l2tp ipsec
Split-tunnel-policy tunnelspecified
value of Split-tunnel-network-list CorpVPN
the address value CorpVPN poolstype tunnel-group CorpVPN remote access
attributes global-tunnel-group CorpVPN
address pool CorpVPN
Group Policy - by default-CorpVPN
IPSec-attributes tunnel-group CorpVPN
pre-shared keyFirst of all, there is overlap crypto ACL with the VPN static L2L:
crypto ASA1MAP 10 card matches the address 101
access-list 101 extended allow ip 10.10.10.0 255.255.255.0 172.18.0.32 255.255.255.240
access-list 101 extended allow ip 172.18.0.32 255.255.255.240 10.10.10.0 255.255.255.0I would remove the 2 lines of ACL 101 above because it is incorrect.
Secondly, from the output of ' cry ipsec to show his ", you seem to be getting the ip address of the"jdv1.australis.net.au", not"CorpVPN"pool pool. Therefore, the No. NAT ACL on the management interface is incorrect. I would just add a greater variety of education no. NAT so that it covers all your ip pool:
access-list no.-NAT-DU-MGMT scope ip 10.10.10.0 allow 255.255.255.0 172.18.0.0 255.255.255.0
Thirdly, even with your dynamic ACL 'OUTSIDE_cryptomap_65535.65535' crypto map, it only covers the 172.18.0.32/28, so I just want to add a wider range since it seems you get the ip address of the different pool:
OUTSIDE_cryptomap_65535.65535 list of allowed ip extended access all 172.18.0.0 255.255.255.0
Then I would disable the following group of access for purposes of test first:
no access-group MANAGEMENT - OUT Interface MANAGEMENT
Finally, please clear all the SA on your ASA and xlate, then reconnect to your vpn client and test it again:
delete the ipsec cry his
clear the isa cry his
clear xlate
Please let us know how it goes after the changes. If it still doesn't work, please please send again the last configuration and also to send the output of the following:
See the isa scream his
See the ipsec scream his
and a screenshot of the page of statistics on your vpn client. Thank you.
-
Remote administration of a PIX running as a VPN client
Hello
I have a setup where a PIX501 works as a VPN client upward against my central VPN3000 concentrator (LAN-2-LAN with NAT - T mode).
External interface of the pix is behind a firewall managed by ISP to the remote end, and get it via DHCP IP address.
So far so good. This configuration works hotel.
The problem is that I can't ssh/telnet to the external interface of the PIX due to this configuration.
Would it not possible to ssh/telnet to the remote pix _inside_ interface?
I guess stuff NAT Bennett, but I can't make it work.
Any ideas?
(: O) Mikkle
This is possible by commands:
management-access inside
It works very well as I have used both inside interface is included in all the crypto config
Sam
-
Win 7 VPN client cannot access remote resources beyond the VPN server
I have a Win 7 laptop with work and customer Win 7 VPN set up, and through it that I can access everything allowed resources on the remote network.
I built a new computer, set up the Win 7 client with the exact same parameters everywhere, connected to the VPN with success, but can not access any of the resources on the remote network that I can on my laptop.
Win 7 64 bit SP 1
I did research online and suggestions have already had reason of my new set up. In addition, I have a second computer that I've set up the VPN client, and I'm having the same problem. VPN connects successfully, but is unable to access the resources.
Tested with firewall off the coast.
Troubleshooting Diagnostic reports: your computer seems to be configured correctly, distance resources detected, but not answered do not.
I created another VPN client on the new computer to another remote network and everything works perfectly.
Remember the old VPN connection to the remote network that does not work on the new computer works perfectly on Win 7 64 bit laptop computer.
So, what do I find also different between identical configurations "should be" where we work and two new machines is not?
It must be something stupid.
Hello
This question is more suited for a TechNet audience. I suggest you send the query to the Microsoft TechNet forum. See the link below to do so:
https://social.technet.Microsoft.com/forums/Windows/en-us/home?Forum=w7itpronetworkingPlease let us know if you have more queries on Windows.
-
Allow Cisco VPN Client through the firewall?
Hello
How can I allow a cisco VPN client work from the inside of our network to an external IP address?
We have customers who wish to make use of their Cisco VPN Client companies but our ASA blocks I think?
Also (sorry to ask) a friend in South America is having the same problem but I am not hink they use Cisco, is there a default port used by the client to Cisco? then I can send this info?
Thank you
Generally, the ASA will allow the IPSEC from the inside to outside traffic. This is when you want it came outside and connect to you - this is where it gets creative. You restrict outgoing traffic at all? You deny all ip/tcp/udp outgoing?
But may depend on if the remote end is compaitable NAT - T, and if they have configured. Another question would be how they allow VPN traffic go?
-
Connected to the ASA via the "VPN Client" software, but cannot ping devices.
I have a network that looks like this:
I successfully connected inside the ASA via a software "Client VPN" tunnel network and got an IP address of 10.45.99.100/16.
I am trying to ping the 10.45.99.100 outside 10.45.7.2, but the ping fails (request timed out).
On the SAA, including the "logging console notifications" value, I notice the following message is displayed:
"% 305013-5-ASA: rules asymmetrical NAT matched for flows forward and backward; "Connection for icmp src, dst outside: 10.45.99.100 inside: 10.45.7.2 (type 8, code 0) rejected due to the failure of reverse path of NAT.
I have a vague feeling that I'm missing a NAT rule of course, but not all. What did I miss?
Here is my configuration of ASA: http://pastebin.com/raw.php?i=ad6p1Zac
Hello
You seem to have a configured ACL NAT0 but is not actually in use with a command "nat"
You would probably need
NAT (inside) 0-list of access inside_nat0_outside
He must manage the NAT0
Personally, I would avoid using large subnets/networks. You probably won't ever have host behind ASA who would fill / 16 subnet mask.
I would also keep the pool VPN as a separate network from LANs behind ASA. The LAN 10.45.0.0/16 and 10.45.99.100 - 200 are on the same network.
-Jouni
-
How do I allow IPSec VPN client-to-client
Can someone briefly describe the steps on an ASA to allow both IPSec VPN clients talking to each other. They are in the same pool of addresses. I already have two same-security-traffic permit for inter and intra interface statements. Thank you!
Sent by Cisco Support technique iPhone App
try to including this traffic in the States of sheep you have
Alos, you may need to make changes to the acl split rules
Maybe you are looking for
-
When you try to view a news article it says that I need Adobe Flash 10.0. I hit to save the file so that it can start loading. He gives four boxes of instructions. 1, click here to save the file, 2, double-click to load the file, don't you remember 3
-
If XP officially no longer supported? Is there a date?
If XP officially no longer supported? Is there a date? Someone knows something about Vista? I don't think it will expand like XP did. Win7 has a life different from Vista. I looked at these two sites. The support is complete. But I just got a few upd
-
Cannot open applications. All open them with Notepad
Most of my programs on windows xp opens as a Notepad. I tried to do a system restore, but a Notepad window appears. How can I get my computer back to normal?
-
My Zune software does not recognize my Zune is connected, how to fix this?
I want to sync my Zune. It is plugged in, but my program does not recognize that it is. There is nothing wrong with the cable, I have several and none of them bring a different result. I have an another Zune which also does not appear. I tried to res
-
How to pass a product code using liquid/Web App
I want to do is have a user to enter a code - say "12345" in a text box and click a "submit" button. It then takes them to another page showing results or error message.I have created a web application with the following fields:ProductCodeNameDetail