nat ASA 5520 problem

Similar Questions

• Using Cisco Client to site VPN on a behind a NAT ASA 5520

  I apologize if this has been asked and we answered in the forums.  I looked, and while I found a large number of entries that were dancing all around this question, I never found nothing which addressed this specific issue.   We currently use an ASA 5520 as the head end of a relatively large customer to site IPSEC VPN (approximately 240 users, not consecutively).   This ASA is currently sitting behind a Checkpoint firewall with a real publicly addressable IP address on its public interface.  All of our customers use the legacy Cisco VPN (not the one anyconnect) client.  We plan to a few controllers F5 link set up between ISPS and firewalls.   For VPN connectivity F5 recommends that we NAT IP address (called a broad IP) to point back to a private IP address on the ASA and F5.  My question is, will this work?   I've always heard say that the head of line needed to have a public IP address on this subject because this is what will be placed in packages for the client to respond to.

  For further information, here's what we have now and what we are invited to attend.

  Current

  ISP - router - firewall-fire - ASA (public IP address as endpoint)

  Proposed

  ISP - router - F5 (public IP address as endpoint using a NAT to ASA) - Firewall - ASA (10.X.X.X as its external interface)

  Proposed alternative

  ISP - router - F5 (public IP address as endpoint using a NAT to ASA) - ASA (10.X.X.X as its external interface)

  All thoughts at this moment would be greatly appreciated.   Thank you!

  Hello

  If there is a static NAT one by one on F5 to the external interface of the ASA, then I don't think they would be any problems.
  Because when the client will attempt to connect to IKE to the translated public IP, F5 will redirect the request to ASA outside interface that is configured for the VPN.

  In addition, to ensure the udp500, 4500 and esp is allowed and then you should be good to go.

  HTH

  Concerning
  Mohit

• ASA 5520 problem

  Hello

  I bought an ASA5520, and I could not access to the console port. Another thing I think that is not normal is because the status light is amber as soon as turn on the switch.

  Is this a hardware problem?

  Thank you.

  Neirival (Brazil/Angola)

  Hello Neirival,

  When you say "could not access the console port" you don't say 'no response from the console port'?

  Simple things first:

  -is this console connection set up in the standard, IE, 8 data bits, etc, etc.?

  -the console connection works for Cisco devices?

  I must say, however, the amber looks like bad news. DOA?

  Kind regards

  theterranaut

• SSL VPN using ASA 5520 mode cluster - several problems

  I configured 2 ASA 5520 s in the load balancing cluster mode. I connect using anyconnect and I download the customer the first time and everything works well except outlook. I don't know why outlook does not work.

  The second problem is after the anyconnect client is installed on your machine, he remembers that ASA (say ASA2) he first connected and the GUI shows the address IP of ASA2 instead of the virtual IP address of the cluster. I want users always connect using the virtual IP address.

  The third problem I have is there is a default group of SSL VPN and I want all users to use this group. In the initial web page, there is a drop down menu which shows that this group, but I still want to disable this menu drop-down.

  Any suggestions?

  To disable the drop-down menu, you can turn it off with the command

  WebVPN

  no activation of tunnel-group-list

  This will take care of your last issue.

  ***************************

  You can create a profile of the Anyconnect client with the name of the server you want to connect with and that make the ASA that will solve your problem of virtual IP.

  **************************

  Regarding Outlook, do you use specific ports which allows inspection of the ASA. Take a look at the list of inspection on the SAA and perhaps try to disable inspection and see if it works.

  *****************************

• Problem connection ASA 5520 GANYMEDE

  I'm just confused at this point. This is the configuration I have so far for the configuration of Ganymede on ASA 5520. SH run

  ?

  1 2 3 4 5 6 7 8 9 10 11 12 13

  aaa-server TacServer protocol tacacs+aaa-server TacServer (LAN) host 172.19.0.226key ***** user-identity default-domain LOCALaaa authentication telnet console LOCALaaa authentication http console TacServer LOCAL aaa authentication ssh console TacServer LOCAL aaa authentication enable console TacServer LOCALaaa authorization command TacServer LOCAL route LAN 172.19.0.0 255.255.255.0 172.30.186.1 1

  After that I was done with the Setup, I was able to connect using my username tacacas and the password you + activate password.

  After that, I closed my GANYMEDE server + to try to the local database. It worked for the user name and password but my password enable does not work locally. Got to be something very simple and he had written down, I was connected via the cable from the console and also changed it was completely with the user name and password but still not able to go into enable mode.

  After that failed I returned and turned on on my server TACACAS. When to wait a few minutes and trying to connect via tacacas NO GO. He doesn't like my username and password.

  So now I'm locked out and have to do password recovery because I can not connect using tacacas, and when tacacas is off I can not go in the local mode.

  Very litle documentation cisco out there for this issue... Any thoughts what coukld be the cause? I know that GANYMEDE works very well since he works on 500 + devices, I'm just confused at this point.

  I need to check a few things before recovery of password:

  To activate question, try typing the login: follow-up of your user name and password.

  For Ganymede number:

  1.] error on the section of logging of the server Ganymede while accessing the credentials of Ganymede.

  2.] was there any problems reachbility during this time?

  3.] all services came fine?

  4.] should focus on debugs following:

  debugging Ganymede

  Debug aaa authentication

  I'm not sure if this can be replicated, but yes love to help out if possible.

  Jatin kone

  -Does the rate of useful messages-

• ASA 5520 IPSec NAT question

  I like more than 150 of VPN on my ASA 5520.  A specific customer, with that I'll put up a VPN has an overlap of two of the intellectual property, it must reach from its internal network.  It is NATing 10.251.11.177 internal network traffic to my ASA presents itself as 10.251.11.177 of the 10.251.11.176/29 network.  Now the two IP of its internal network, it must reach are 10.1.254.200 and 10.1.254.201.

  Thus, following the documentation on the site Web of Cisco I'm doing Policy Based Routing on the ASA 5520 (my thesis) so that its traffic will 1.1.1.1 and 1.1.1.2 instead of 10.1.254.200 and 10.1.254.201.  Once it reaches my ASA 5520 it gets back to these IP tranlated.

  I am using the following configuration, but when I try to add static entries, it won't let me add them.  I even tried "static 1.1.1.1 (exterior, Interior) POLICYNAT of the access list" with the ACL in reverse but no use.

  object-group, network VPN-map

  network-object host 1.1.1.1

  network-object host 1.1.1.2

  !

  POLICYNAT list extended access allowed host ip 10.1.254.200 10.251.11.176 255.255.255.248

  POLICYNAT list extended access allowed host ip 10.1.254.201 10.251.11.176 255.255.255.248

  !

  static (inside, outside) 1.1.1.1 access-list POLICYNAT

  public static (inside, outside) 1.1.1.2 - POLICYNAT access list

  Try breaking the IPs in two ACL

  POLICYNAT1 list extended access allowed host ip 10.1.254.200 10.251.11.176 255.255.255.248

  POLICYNAT2 list extended access allowed host ip 10.1.254.201 10.251.11.176 255.255.255.248

  !

  static (inside, outside) 1.1.1.1 access-list POLICYNAT1

  public static (inside, outside) 1.1.1.2 - POLICYNAT2 access list

  HTH

  GE

• ASA 5520 to Juniper ss505m vpn

  I'm having a problem with the vpn site to site between a asa 5520 and Juniper ss 505 m. The tunnel rises, but we seem unable to pass traffic through the vpn tunnel.  It appears on the remote side makes a connection to the ftp server on the Local Server, but is never prompt identification of connection information.

  April 19, 2016 13:27:13 SQL-B2B-01: % ASA-4-402116: IPSEC: received a package ESP x.x (SPI = 0xD167A5E8, sequence number = 0xD).

  241.90 (user = X.X.241.90) at X.X.167.230.  Inside the package décapsulés does not match policy negotiated in the SA.  The

  package specifies its destination as its Protocol TCP, its source such as X.X.2.68 and X.X.167.233.  SA specifies its loc

  proxy of Al X.X.167.233/255.255.255.255/tcp/5376 and his remote_proxy as X.X.2.68/255.255.255.255/tcp/5376.

  list of remote ip-group of objects allowed extended West Local Group object

  NAT static Local_Pub Local destination (indoor, outdoor) static source Remote

  Crypto ipsec ikev1 transform-set esp-aes-256 Remote esp-sha-hmac

  West-map 95 crypto card is the Remote address
  card crypto West-map 95 set peer X.X.241.90
  map West-map 95 set transform-set Remote ikev1 crypto
  card crypto West-map 95 defined security-association life seconds 28800

  Juniper-

  "Remote-ftp" X.X.167.233 255.255.255.255

  Gateway proposal P1 preshare "[email protected]/ * /" proposal "pre-g2-aes256-sha-28800.

  P2-proposal "no-pfs-esp-aes256-sha-28800" No. - pfs esp aes256 sha-1 second 28800

  ----------------------

  the top of the policy of "Trust" to "Untrust" "X.X.2.68/32" "Remote-ftp' 'ftp' vpn"Remote-vpn"tunnel log

  put on top of the "Untrust" policy to the "Trust" "Remote-ftp' 'X.X.2.68/32' 'ftp' vpn"SonoraQ-vpn"tunnel sign

  I do not know Juniper, but it seems that it is trying to negotiate the use of only 5376/tcp on the tunnel, when it should be negotiated just Protocol "ip".

• Upgrade to Cisco ASA 5520 8.2.5 to 9.1.7

  Hello

  I have an upgrade tonight for a customer to upgrade a StandAlone ASA 5520 in version 8.2.5 in 9.1.7. I have the same upgrade week next to the same client for a failover pair.

  I already have this kind of process of 8.2.x upgrade to 9.1.x so I know the entire process, since I have to take a first step 8.2.5 8.4.6 then 9.1.7. In addition this customer has no statement of Nat therefore normally an easy process.

  But today during my routine to prepare for the upgrade (I prefer to make a double or triple check before) I found this bug:

  https://BST.cloudapps.Cisco.com/bugsearch/bug/CSCuh19234;JSESSIONID=0A69...

  This bug is fixed in version 8.4.7, and 8.4.6.99. But it is not recommended by the upgrade process for a 8.2.5 to 8.4.7 jump and I can not find the 8.4.6.99 version.

  I don't want to have any problems during my upgrade with something I can avoid.

  As I said I already have this updated in the past without any problem and with a more complex configuration.

  Has anyone as a return to this process for the last months? Should I do an extra step? (before first 8.2.5 to 8.4.5 8.4.6 or 8.4.7)

  Thank you in advance for your answer.

  There are a few incidents reported for ASA 5520 8.2.5 hit this defect running.

  You can go for an extra for 8.4.x upgrade as you mentioned to avoid default we can't say for sure if you will encounter this situation or not.  8.4.6.99 can be a picture of development so be unavailable unless you want to call TAC and confirm or obtain any other image in 8.4.x train.
  Maybe add another upgrade code can't hurt as that hit the bug.

  Kind regards
  Dinesh Moudgil

  PS Please rate helpful messages.

• ASA 5520 8.0 (4) port depending on the ACLs vpn works not

  Hi all

  I have a problem with an ASA (5520 8.0 (4)) for lack of working with a port based acl for remote clients. I have a simple acl from a single line to split traffic, if I allowed the tunnel IP works fine, if I lock it up to TCP 3389 rdp will not work. I don't see anything in the logs and debug output, I did have a problem with a similar configuration (5510 8.0 (4) and I'm at a loss to explain it.)

  Everyone knows about this problem before? I have nat exclusions etc and as I said, the tunnel only works if the acl permits all IP traffic between client and server.

  THX in advance

  Split-tunnel list cannot IP, if you want to restrict which ports are are sent via the tunnel vpn for your clients vpn, you need to use VPN filters under Group Policy:

  http://www.Cisco.com/en/us/products/HW/vpndevc/ps2030/products_configuration_example09186a00808c9a87.shtml

• Routing with Cisco ASA 5520 VPN

  I have installed IPsec vpn remote users in the Cisco ASA 5520 using RADIUS in my main network. Works very well. I have a site to my Cisco ASA5520 tunnels going to other sites, some of the tunnels have Cisco ASA and some have SonicWalls. I wish that my users VPN remote IPSec to be able to navigate in these tunnels is a site to access remote subnets attached to these tunnels. Do I need to use a combination of routing and the ACL? Or can I just use ACL only? Or just use routing only?

  Thank you

  Carlos

  Hello

  The key to set up here is the two ACL of VPN L2L end points that determine the 'interesting' traffic to connect VPN L2L. You will also need to confirm that the connection of the VPN Client is configured so that traffic to the remote sites have sent to the connection of the VPN client. There are also other things that you should check on your ASA plant

  Here most of the things you usually have to confirm

  • Set up 'permit same-security-traffic intra-interface' if it is already present in your configuration
    • This setting will allow connections to form between the hosts that are connected to the same interface on the ASA. In this case, applies because the VPN client users are connected to the interface 'outside' of the ASA and also remote sites are connected to the ASA to "external". If the traffic between the remote VPN Client and VPN L2L sites will be to enter and exit the same interface
  • You will need to check how the customer if configured VPN connection. Split or full Tunnel tunnel
    • If the connection of the VPN Client is configured as Split Tunnel then you need to add all the networks from the remote to the Split Tunnel, so that the connections between the VPN Client is transmitted to the ASA and from there connections VPN L2L
    • If the connection of the VPN Client is configured as full Tunnel, then there no problem that all traffic is transferred to the Client VPN connection all its assets
  • Define the VPN pool in the ACL of VPN L2L
    • You should make sure that the pool network VPN Client is defined in the ACL that define 'interesting' traffic to connect VPN L2L. So, you need to add the pool VPN VPN L2L configurations on the sites of Central America and remote control
  • Configure NAT0 / NAT exempt for remote VPN Client to L2L VPN Site traffic at both ends of the VPN L2L
    • You must ensure that the NAT0 / exempt NAT rules exist for the VPN Client for Remote Site traffic. This will have to be configured on the SAA "outside" interface. Format of configuration varies naturally a bit on the ASA Central his software level.

  These should be the most common things to set up and confirm for traffic to flow between the VPN Client and Remote Sites

  Hope this helps please rate if yes or ask more if necessary.

  -Jouni

• IPSec VPN to asa 5520

  Hello

  First I must admit that I am not very versed in Cisco equipment or in general IPSEC connections so my apologies if I'm doing something really good obviously stupid, but I checked through any kind of things that I could find on the internet on the configuration of IPSEC VPN.

  The setup I have is an asa 5520 (o/s 8.2) firewall which, for now, is connected to a temporary connection beautiful style home broadband for testing purposes. The netopia router is configured to allow ipsec passthrough and redirect 62515 UDP, TCP 10000, 4500 UDP, UDP 500 ports in the asa 5520.

  I'm trying to connein out of a laptop with disabled windows firewall and vpn cisco 5.0.02.0090 client version.

  I ran several attempts through the ipsec configuration wizard options. most of the time that nothing comes in the newspaper to show that a connection was attempted, but there is a way I can set up product options the following on the firewall log:

  4. Sep 24 2010 | 13: 54:29 | 713903 | Group = VPNtest9, IP = 86.44.x.x, error: cannot delete PeerTblEntry

  5: Sep 24 2010 | 13: 54:29 | 713902 | Group = VPNtest9, IP = 86.44.x.x, drop table homologous counterpart does not, no match!

  6. Sep 24 2010 | 13: 54:21 | 713905 | Group VPNtest9, IP = 86.44.x.x, P1 = relay msg sent to AM WSF

  3: Sep 24 2010 | 13: 54:21 | 713201 | Group = VPNtest9, IP = 86.44.x.x, double-Phase 1 detected package. Retransmit the last packet.

  6. Sep 24 2010 | 13: 54:16 | 713905 | Group VPNtest9, IP = 86.44.x.x, P1 = relay msg sent to AM WSF

  3: Sep 24 2010 | 13: 54:16 | 713201 | Group = VPNtest9, IP = 86.44.x.x, double-Phase 1 detected package. Retransmit the last packet.

  6. Sep 24 2010 | 13: 54:11 | 713905 | Group VPNtest9, IP = 86.44.x.x, P1 = relay msg sent to AM WSF

  3: Sep 24 2010 | 13: 54:11 | 713201 | Group = VPNtest9, IP = 86.44.x.x, double-Phase 1 detected package. Retransmit the last packet.

  3: Sep 24 2010 | 13: 54:06 | 713257 | 1 failure to phase: incompatibility of types of attributes of class Group Description: RRs would be: Group 2 FCMS would: Group 1

  3: Sep 24 2010 | 13: 54:06 | 713257 | 1 failure to phase: incompatibility of types of attributes of class Group Description: RRs would be: Group 2 FCMS would: Group 1

  3: Sep 24 2010 | 13: 54:06 | 713257 | 1 failure to phase: incompatibility of types of attributes of class Group Description: RRs would be: Group 2 FCMS would: Group 1

  3: Sep 24 2010 | 13: 54:06 | 713257 | 1 failure to phase: incompatibility of types of attributes of class Group Description: RRs would be: Group 2 FCMS would: Group 1

  3: Sep 24 2010 | 13: 54:06 | 713257 | 1 failure to phase: incompatibility of types of attributes of class Group Description: RRs would be: Group 2 FCMS would: Group 1

  3: Sep 24 2010 | 13: 54:06 | 713257 | 1 failure to phase: incompatibility of types of attributes of class Group Description: RRs would be: Group 2 FCMS would: Group 1

  3: Sep 24 2010 | 13: 54:06 | 713257 | 1 failure to phase: incompatibility of types of attributes of class Group Description: RRs would be: Group 2 FCMS would: Group 1

  3: Sep 24 2010 | 13: 54:06 | 713257 | 1 failure to phase: incompatibility of types of attributes of class Group Description: RRs would be: Group 2 FCMS would: Group 1

  3: Sep 24 2010 | 13: 54:06 | 713257 | 1 failure to phase: incompatibility of types of attributes of class Group Description: RRs would be: Group 2 FCMS would: Group 1

  3: Sep 24 2010 | 13: 54:06 | 713257 | 1 failure to phase: incompatibility of types of attributes of class Group Description: RRs would be: Group 2 FCMS would: Group 1

  6. Sep 24 2010 | 13: 54:06 | 302015 | 86.44.x.x | 51905 | 192.168.0.27 | 500 | Built UDP inbound connection 7487 for Internet:86.44.x.x/51905 (86.44.x.x/51905) at identity:192.168.0.27/500 (192.168.0.27/500)

  and this, in the journal of customer:

  Cisco Systems VPN Client Version 5.0.02.0090

  Copyright (C) 1998-2007 Cisco Systems, Inc.. All rights reserved.

  Customer type: Windows, Windows NT

  Running: 5.1.2600 Service Pack 3

  24 13:54:08.250 24/09/10 Sev = Info/4 CM / 0 x 63100002

  Start the login process

  25 13:54:08.265 24/09/10 Sev = Info/4 CM / 0 x 63100004

  Establish a secure connection

  26 13:54:08.265 24/09/10 Sev = Info/4 CM / 0 x 63100024

  Attempt to connect with the server "213.94.x.x".

  27 13:54:08.437 24/09/10 Sev = Info/6 IKE/0x6300003B

  Attempts to establish a connection with 213.94.x.x.

  28 13:54:08.437 24/09/10 Sev = Info/4 IKE / 0 x 63000013

  SEND to > ISAKMP OAK AG (SA, KE, NO, ID, VID (Xauth), VID (dpd), VID (Frag), VID(Nat-T), VID (Unity)) at 213.94.x.x

  29 13:54:08.484 24/09/10 Sev = Info/4 IPSEC / 0 x 63700008

  IPSec driver started successfully

  30 13:54:08.484 24/09/10 Sev = Info/4 IPSEC / 0 x 63700014

  Remove all keys

  31 13:54:13.484 24/09/10 Sev = Info/4 IKE / 0 x 63000021

  Retransmit the last package!

  32 13:54:13.484 24/09/10 Sev = Info/4 IKE / 0 x 63000013

  SEND to > ISAKMP OAK AG (Retransmission) to 213.94.x.x

  33 13:54:18.484 24/09/10 Sev = Info/4 IKE / 0 x 63000021

  Retransmit the last package!

  34 13:54:18.484 24/09/10 Sev = Info/4 IKE / 0 x 63000013

  SEND to > ISAKMP OAK AG (Retransmission) to 213.94.x.x

  35 13:54:23.484 24/09/10 Sev = Info/4 IKE / 0 x 63000021

  Retransmit the last package!

  36 13:54:23.484 24/09/10 Sev = Info/4 IKE / 0 x 63000013

  SEND to > ISAKMP OAK AG (Retransmission) to 213.94.x.x

  37 13:54:28.484 24/09/10 Sev = Info/4 IKE / 0 x 63000017

  Marking of IKE SA delete (I_Cookie = 36C50ACCE984B0B0 R_Cookie = 0000000000000000) reason = DEL_REASON_PEER_NOT_RESPONDING

  38 13:54:28.984 24/09/10 Sev = Info/4 IKE/0x6300004B

  IKE negotiation to throw HIS (I_Cookie = 36C50ACCE984B0B0 R_Cookie = 0000000000000000) reason = DEL_REASON_PEER_NOT_RESPONDING

  39 13:54:28.984 24/09/10 Sev = Info/4 CM / 0 x 63100014

  Could not establish the Phase 1 SA with the server '213.94.x.x' due to the 'DEL_REASON_PEER_NOT_RESPONDING '.

  40 13:54:28.984 24/09/10 Sev = Info/5 CM / 0 x 63100025

  Initializing CVPNDrv

  41 13:54:28.984 24/09/10 Sev = Info/6 CM / 0 x 63100046

  Set indicator established tunnel to register to 0.

  42 13:54:28.984 24/09/10 Sev = Info/4 IKE / 0 x 63000001

  Signal received IKE to complete the VPN connection

  43 13:54:29.187 24/09/10 Sev = Info/4 IPSEC / 0 x 63700014

  Remove all keys

  44 13:54:29.187 24/09/10 Sev = Info/4 IPSEC / 0 x 63700014

  Remove all keys

  45 13:54:29.187 24/09/10 Sev = Info/4 IPSEC / 0 x 63700014

  Remove all keys

  46 13:54:29.187 24/09/10 Sev = Info/4 IPSEC/0x6370000A

  IPSec driver successfully stopped

  I have connectivity full http from the internet to a machine inside the asa 5520 so I think that the static routing and NAT'ing should be ok, but I am pleased to provide you with all the details.

  Can you see what I'm doing wrong?

  Thank you

  Sam

  Pls add the following policy:

  crypto ISAKMP policy 10

  preshared authentication

  the Encryption

  md5 hash

  Group 2

  You can also run debug on the ASA:

  debugging cry isa

  debugging ipsec cry

  and retrieve debug output after trying to connect.

• Tunnel VPN ASA 5520 (DMZ + INSIDE) destined for OUTSIDE

  I can't find any reference to anywhere else.

  We have an ASA 5520 to our site HQ (inside the network) with several regional subnets on the DMZ interface.

  We need connectivity VPN Site to Site between the INSIDE and a remote control on the OUTSIDE of the site, as well as between the DMZ subnets and even outside the site. The interface from the OUTSIDE of the SAA must be local VPN endpoint for all tunnels.

  I created a S2S VPN between the INSIDE and the OUTSIDE site and it works great.

  When I create a VPN S2S tunnel between a site of DMZ and even outside the site (using the same settings the and remote, but with a cryptomap different because the local subnet (DMZ) is different from the other inside the subnet, the traffic gets the mapping (show crypto isakmp his) to the same cryptomap that was created for the access to the tunnel from the OUTSIDE) , instead of to the new cryptomap, so remote endpoint deletes it, and traffic also causes SPI incorrect of for the remote endpoint, which makes the original INTERIOR outside OF THE VPN tunnel to fall from time to time.

  Is this a bug?

  I also did a local S2S VPN tunnel configuration test of networks as everything INSIDE and the DMZ. With the help of the wizard VPN S2S leads ASA only to create a NAT rule exempted for the subnet on the INSIDE interface. Can I manually create another tax-exempt NAT rule to the side of the DMZ and use this a S2S tunnel to connect sites inside and DMZ to the remote OFF-SITE in a connection profile?

  I'm building a Rube Goldberg?

  Thank you

  George

  Hi George,.

  It seems you have a situation overlapping it, are you sure that subnets inside did not overlap with the networks from the DMZ?  A package tracer could clarify wha that the ASA is actually sending.

  In addition, you can merge the two interfaces on the same card encryption if you wish, just make sure that the NAT is configured correctly.   For example; Source NAT (all, outside) static...

  It may be useful

  -Randy-

• VPN site to site & outdoor on ASA 5520 VPN client

  Hi, I'm jonathan rivero.

  I have an ASA 5520 Version 8.0 (2), I configured the site-to-site VPN and works very well, in the other device, I configured the VPN Client for remote users and works very well, but I try to cofigure 2 VPNs on ASA 5520 on the same outside interface and I have the line "outside_map interface card crypto outdoors (for VPN client). , but when I set up the "crypto map VPNL2L outside interface, it replaces the command', and so I can have only a single connection.

  the executed show.

  ASA1 (config) # sh run

  : Saved

  :

  ASA Version 8.0 (2)

  !

  hostname ASA1

  activate 7esAUjZmKQSFDCZX encrypted password

  names of

  !

  interface Ethernet0/0

  nameif inside

  security-level 100

  address 172.16.3.2 IP 255.255.255.0

  !

  interface Ethernet0/1

  nameif outside

  security-level 0

  IP 200.20.20.1 255.255.255.0

  !

  interface Ethernet0/1.1

  VLAN 1

  nameif outside1

  security-level 0

  no ip address

  !

  interface Ethernet0/2

  Shutdown

  No nameif

  no level of security

  no ip address

  !

  interface Ethernet0/3

  Shutdown

  No nameif

  no level of security

  no ip address

  !

  interface Ethernet0/4

  Shutdown

  No nameif

  no level of security

  no ip address

  !

  interface Ethernet0/5

  Shutdown

  No nameif

  no level of security

  no ip address

  !

  2KFQnbNIdI.2KYOU encrypted passwd

  passive FTP mode

  object-group, net-LAN

  object-network 172.16.0.0 255.255.255.0

  object-network 172.16.1.0 255.255.255.0

  object-network 172.16.2.0 255.255.255.0

  object-network 172.16.3.0 255.255.255.0

  object-group, NET / remote

  object-network 172.16.100.0 255.255.255.0

  object-network 172.16.101.0 255.255.255.0

  object-network 172.16.102.0 255.255.255.0

  object-network 172.16.103.0 255.255.255.0

  object-group network net-poolvpn

  object-network 192.168.11.0 255.255.255.0

  access list outside nat extended permit ip net local group object all

  access-list extended sheep allowed ip local object-group net object-group net / remote

  access-list extended sheep allowed ip local object-group net net poolvpn object-group

  access-list splittun-vpngroup1 extended permitted ip local object-group net net poolvpn object-group

  pager lines 24

  Within 1500 MTU

  Outside 1500 MTU

  outside1 MTU 1500

  IP local pool ippool 192.168.11.1 - 192.168.11.100 mask 255.255.255.0

  no failover

  ICMP unreachable rate-limit 100 burst-size 10

  don't allow no asdm history

  ARP timeout 14400

  Global 1 interface (outside)

  NAT (inside) 0 access-list sheep

  NAT (inside) 1 access list outside nat

  Route outside 0.0.0.0 0.0.0.0 200.20.20.1 1

  Route inside 172.16.0.0 255.255.255.0 172.16.3.2 1

  Route inside 172.16.1.0 255.255.255.0 172.16.3.2 1

  Route inside 172.16.2.0 255.255.255.0 172.16.3.2 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, uauth 0:05:00 absolute

  dynamic-access-policy-registration DfltAccessPolicy

  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-3DES-MD5-esp-3des esp-md5-hmac

  Crypto ipsec transform-set esp-SHA-ESP-3DES-3des esp-sha-hmac

  86400 seconds, duration of life crypto ipsec security association

  Crypto ipsec kilobytes of life security-association 400000

  Crypto-map dynamic outside_dyn_map 20 the value transform-set ESP-3DES-SHA

  card crypto VPNL2L 1 match for sheep

  card crypto VPNL2L 1 set peer 200.30.30.1

  VPNL2L 1 transform-set ESP-3DES-MD5 crypto card game

  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 20

  preshared authentication

  3des encryption

  md5 hash

  Group 2

  life 86400

  crypto ISAKMP policy 30

  preshared authentication

  aes-256 encryption

  sha hash

  Group 2

  life 86400

  crypto ISAKMP policy 65535

  preshared authentication

  3des encryption

  sha hash

  Group 2

  life 86400

  Telnet timeout 5

  SSH timeout 5

  Console timeout 0

  a basic threat threat detection

  Statistics-list of access threat detection

  !

  !

  internal vpngroup1 group policy

  attributes of the strategy of group vpngroup1

  banner value +++ welcome to Cisco Systems 7.0. +++

  value of 192.168.0.1 DNS server 192.168.1.1

  Split-tunnel-policy tunnelspecified

  Split-tunnel-network-list value splittun-vpngroup1

  value by default-ad domain - domain.local

  Split-dns value ad - domain.local

  the address value ippool pools

  username password asa1 VRTlLlJ48/PoDKjS encrypted privilege 15

  tunnel-group 200.30.30.1 type ipsec-l2l

  IPSec-attributes tunnel-group 200.30.30.1

  pre-shared-key *.

  type tunnel-group vpngroup1 remote access

  tunnel-group vpngroup1 General-attributes

  ippool address pool

  Group Policy - by default-vpngroup1

  vpngroup1 group of tunnel ipsec-attributes

  pre-shared-key *.

  context of prompt hostname

  Cryptochecksum:00000000000000000000000000000000

  : end

  ASA2 (config) #sh run

  Crypto ipsec transform-set ESP-3DES-MD5-esp-3des esp-md5-hmac
  86400 seconds, duration of life crypto ipsec security association
  Crypto ipsec kilobytes of life security-association 400000
  card crypto VPNL2L 1 match for sheep
  card crypto VPNL2L 1 set peer 200.30.30.1
  VPNL2L 1 transform-set ESP-3DES-MD5 crypto card game
  VPNL2L interface card crypto outside
  crypto isakmp identity address
  crypto ISAKMP allow outside
  crypto ISAKMP policy 20
  preshared authentication
  3des encryption
  md5 hash
  Group 2
  life 86400

  tunnel-group 200.30.30.1 type ipsec-l2l
  IPSec-attributes tunnel-group 200.30.30.1
  pre-shared key cisco

  my topology:

  

  I try with the following links, but did not work

  http://www.Cisco.com/en/us/products/ps6120/products_configuration_example09186a0080912cfd.shtml

  http://www.Cisco.com/en/us/products/ps6120/products_tech_note09186a00807e0aca.shtml

  Best regards...

  "" I thing both the force of the SAA with the new road outside, why is that? ".

  without the road ASA pushes traffic inward, by default.

  In any case, this must have been a learning experience.

  Hopefully, this has been no help.

  Please rate, all the helful post.

  Thank you

  Rizwan Muhammed.

• With an ASA 5520 port forwarding

  Hi all

  I recently bought a Cisco ASA 5520 on eBay for study and I decided to only use it as a firewall between my home LAN and Internet. Wow, what a learning curve! I managed to add my internal networks as objects and create a rule (thanks to youtube) NAT to PAT my internal devices out of the Internet with ASSISTANT Deputy Ministers, but I am really struggling to do the following:-

  -allow all incoming traffic that hits the outside interface for port 38921 and nat at 10.1.10.101:38921

  -allow all incoming traffic that hits the outside interface for port 30392 and nat at 10.1.10.101:30392

  Can someone guide me on how to do it, because I have a couple of services that run behind these ports on a server I want to get when I'm not at home? My (rather messy) config is as follows:-

  hostname FW1

  activate the encrypted password

  encrypted passwd

  names of

  !

  interface GigabitEthernet0/0

  Description * externally facing Internet *.

  nameif outside

  security-level 0

  IP address dhcp setroute

  !

  interface GigabitEthernet0/1

  Description * internal face to 3750 *.

  nameif inside

  security-level 100

  IP 10.1.10.2 255.255.255.0

  !

  interface GigabitEthernet0/2

  Shutdown

  No nameif

  no level of security

  no ip address

  !

  interface GigabitEthernet0/3

  Shutdown

  No nameif

  no level of security

  no ip address

  !

  interface Management0/0

  nameif management

  security-level 100

  IP 192.168.1.1 255.255.255.0

  !

  passive FTP mode

  the VLAN1 object network

  subnet 192.168.1.0 255.255.255.0

  Legacy description

  network of the WiredLAN object

  10.1.10.0 subnet 255.255.255.0

  Wired LAN description

  network of the CorporateWifi object

  10.1.160.0 subnet 255.255.255.0

  Company Description 160 of VLAN wireless

  network of the GuestWifi object

  10.1.165.0 subnet 255.255.255.0

  Description Wireless VLAN 165 comments

  network of the LegacyLAN object

  subnet 192.168.1.0 255.255.255.0

  Description Legacy LAN in place until the change on

  the file server object network

  Home 10.1.10.101

  Description File Server

  service object Service1

  tcp source eq eq 38921 38921 destination service

  1 service Description

  the All_Inside_Networks object-group network

  network-object VLAN1

  network-object, object WiredLAN

  network-object, object CorporateWifi

  network-object, object GuestWifi

  network-object, object LegacyLAN

  object-group service Service2 tcp - udp

  port-object eq 30392

  object-group service DM_INLINE_TCPUDP_1 tcp - udp

  port-object eq 30392

  Group-object Service2

  object-group Protocol TCPUDP

  object-protocol udp

  object-tcp protocol

  Outside_access_in list extended access allowed object-group TCPUDP any inactive FileServer object-group DM_INLINE_TCPUDP_1 object

  Outside_access_in list extended access allowed object Service1 any inactive FileServer object

  pager lines 24

  Enable logging

  asdm of logging of information

  Outside 1500 MTU

  MTU 1500 internal

  management of MTU 1500

  no failover

  ICMP unreachable rate-limit 1 burst-size 1

  ASDM image disk0: / asdm - 714.bin

  don't allow no asdm history

  ARP timeout 14400

  service interface NAT (inside, outside) dynamic source FileServer Service1 inactive Service1

  NAT (all, outside) interface dynamic source All_Inside_Networks

  Access-group Outside_access_in in interface outside

  Internal route 10.1.160.0 255.255.255.0 10.1.10.1 1

  Internal route 10.1.165.0 255.255.255.0 10.1.10.1 1

  Internal route 192.168.1.0 255.255.255.0 10.1.10.1 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

  identity of the user by default-domain LOCAL

  Enable http server

  http 10.1.160.15 255.255.255.255 internal

  No snmp server location

  No snmp Server contact

  Server enable SNMP traps snmp authentication linkup, linkdown warmstart of cold start

  Telnet 10.1.160.15 255.255.255.255 internal

  Telnet timeout 5

  SSH timeout 5

  Console timeout 0

  interface ID client DHCP-client to the outside

  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

  username privilege of encrypted password of Barry 15

  !

  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:19be38edefe8c3fd05e720aedee62c8e

  : end

  1. This is just one example of configuration and another option with to reason and avoid to send us the complete configuration of NAT:

  network of the 10.1.10.101 object

  Home 10.1.10.101

  service object 38921

  tcp source eq 38921 service

  service object 30392

  tcp source eq 30392 service

  NAT (inside, outside) 1 static source 10.1.10.101 38921 38921 service interface

  NAT (inside, outside) 1 static source 10.1.10.101 30392 30392 service interface

  Let me know if it works

• How many group Supportepar ASA 5520 vpn for remote access

  Hello

  Howmany vpn group is supported on asa 5520 with configuraion vpn remote access.

  Concerning

  1 if nat-control is disabled and you do not have any other order NAT in your config file, you do not have it. Try to remove the existing "NAT 0" command and "clear xlate."

  2. you must ensure that your network inside know they can go by ASA to access remote vpn client IP. You have any device layer 3 behind the ASA that does the routing. If so, please verify that this is the routing table.