VPN concentrator 3005 - problem of IP attribution

Similar Questions

• Connection VPN concentrator 3000 problem

  Hi all

  I hope that u all experts will be able to help me through this time thick. Our VPN 3000 Concentrator admin password has been changed by someone in order to reset the password using directly by serial cable, now the problem is it allows me to connect with admin console but not via the web administration or telnet interface. I have activated access telnet and http, but always without success. Concentrator uses the internal database so no AAA server is configured.

  Can someone help me please thanks to this?

  Kind regards

  The console password should be the same as the telnet and HTTP password.

  The problem doesn't seem to be on the password.

  Please check under: Administration--> access--> access control list--> and check if your IP is in the list. If this isn't the case, please add your IP address/subnet to the list for you HTTP access to the VPN concentrator.

• Cisco VPN concentrator 3005

  FW 4.1.7r

  I can't the https management work on the device.  The event logs tell something, of not being able to add the ssl certificate to the private interface.  I tried to turn on/off box https without success.  I also restarted the device.

  Anything else I can try?

  You can check if the self-signed certificate VPN concentrator has expired.

  It will be under the Administration--> Management of certificates

• problem of traffic flow with tunnel created the network with a tunnel to a VPN concentrator

  Hi, I worked with Cisco and the seller for 2 weeks on this.II am hoping that what we are witnessing will ring a Bell with someone.

  Some basic information:

  I work at a seller who needs from one site to the other tunnel.  There are currently 1 site to another with the seller using a Juniper SSG, which works without incident in my system.  I'm transitioning to routers Cisco 2811 and put in place a new tunnel with the seller for the 2800 uses a different public ip address in my address range.  So my network has 2 tunnels with the provider that uses a Cisco VPN concentrator.  The hosts behind the tunnel use 20x.x.x.x public IP addresses.

  My Cisco router will create a tunnel, but I can't not to hosts on the network of the provider through the Cisco 2811, but I can't get through the tunnel of Juniper.  The seller sees my packages and provider host meets them and sends them to the tunnel.  They never reach the external interface on my Cisco router.

  I'm from the external interface so that my endpoint and the peers are the same IP address.  (note, I tried to do a static NAT and have an address of tunnel and my different host to the same result.)  Cisco has confirmed that I do have 2 addresses different and this configuration was a success with the creation of another successful tunnels toa different network.)

  I tested this configuration on a network of transit area before moving the router to the production network and my Cisco 2811 has managed to create the tunnel and ping the inside host.  Once we moved the router at camp, we can no longer ping on the host behind the seller tunnel.   The seller assured me that the tunnel setting is exactly the same, and he sees his host to send traffic to the tunnel.  The seller seems well versed with the VPN concentrator and manages connections for many customers successfully.

  The seller has a second VPN concentrator on a separate network and I can connect to this VPN concentrator with success of the Cisco 2811 who is having problems with the hub, which has also a tunnel with Gin.

  Here is what we have done so far:

  (1) confirm the config with the help of Cisco 2811.  The tunnel is up.  SH cyrpto ipa wristwatch tunnel upward.
  (2) turn on Nat - T side of the tunnel VPN landscapers
  (3) confirm that the traffic flows properly a tunnel on another network (which would indicate that the Cisco config is ok)
  (4) successfully, tunnel and reach a different configuration hosting
  (5) to confirm all the settings of tunnel with the seller
  (6) the seller confirmed that his side host has no way and that it points to the default gateway
  (7) to rebuild the tunnel from scratch
  8) confirm with our ISP that no way divert traffic elsewhere.  My gateway lSP sees my directly connected external address.
  (9) confirm that the ACL matches with the seller
  (10) I can't get the Juniper because he is in production and in constant use

  Is there a known issue with the help of a VPN concentrator to connect to 2 tunnels on the same 28 network range?

  Options or ideas are welcome.  I had countless sessions with Cisco webex, but do not have access to the hub of the seller.  I can forward suggestions.

  Here's a code

  crypto ISAKMP policy 1
  BA 3des
  md5 hash
  preshared authentication
  Group 2
  !
  crypto ISAKMP policy 2
  BA 3des
  preshared authentication
  Group 2

  Crypto ipsec transform-set mytrans aes - esp esp-sha-hmac

  Crypto-map dynamic dynmap 30
  Set transform-set RIGHT

  ISAKMP crypto key address No.-xauth

  interface FastEthernet0/0
  Description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-FE $ 0/0
  IP 255.255.255.240
  IP access-group 107 to
  IP access-group out 106
  NAT outside IP
  IP virtual-reassembly
  route IP cache flow
  automatic duplex
  automatic speed
  crypto mymap map

  logging of access lists (applied outside to get an idea of what will happen.  No esp traffic happens, he has never hits)

  allowed access list 106 esp host host newspaper
  106 ip access list allow a whole
  allowed access list 107 esp host host Journal
  access-list 107 permit ip host host Journal

  access-list 107 permit ip host host Journal
  107 ip access list allow a whole

  Crypto isa HS her
  IPv4 Crypto ISAKMP Security Association
  status of DST CBC State conn-id slot
    QM_IDLE ASSETS 0 1010

  "Mymap" ipsec-isakmp crypto map 1
  Peer =.
  Extend the 116 IP access list
  access - list 116 permit ip host host (which is a public IP address))
  Current counterpart:
  Life safety association: 4608000 kilobytes / 2800 seconds
  PFS (Y/N): N
  Transform sets = {}
  myTrans,
  }

  OK - so I have messed around the lab for 20 minutes and came up with the below (ip are IP test:-)

  (4) ip nat pool crypto-nat 10.1.1.1 10.1.1.1 prefix length 30 <> it comes to the new address of NAT

  !
  (1) ip nat inside source list 102 interface FastEthernet0/0 overload <> it comes to the interface by default NAT

  !
  IP nat inside source map route overload of crypto-nat of crypto-nat pool <> it is the policy of the NAT function

  !

  (6) access-list 101 permit ip 172.16.1.0 0.0.0.255 172.16.2.0 0.0.0.255 <> defines the IP source and destination traffic

  !

  (2) access-list 102 deny ip 172.16.1.0 0.0.0.255 172.16.2.0 0.0.0.255 <> does not NAT the normal communication

  (3) access-list 102 deny ip 10.1.1.1 host 172.16.2.0 0.0.0.255 <> does not re - NAT NAT

  (1) access-list 102 permit ip 172.16.1.0 0.0.0.255 any <> allows everyone else to use the IP Address of the interface for NAT

  !

  (5) crypto-nat route-map permit 5 <> condition for the specific required NAT
  corresponds to the IP 101 <> game of traffic source and destination IP must be NAT'td

  (7) access list 103 permit ip 10.1.1.1 host 172.16.2.0 0.0.0.255 <> crypto acl

  Then, how the works above, when a package with the what IP 172.16.1.0/24 source wants to leave the router to connect to google, say the source will change to IP interface (1).  When 172.16.1.0/24 wants to talk to172.16.2.0/24, it does not get translated (2).  When the remote end traffic equaled the following clause of NAT - the already NAT'td IP will not be affected again (3) when a host 172.16.1.0/24 wants to communicate with 172.16.2.20/24 we need a NAT NAT specific pool is required (4).  We must define a method of specific traffic to apply the NAT with a roadmap (5) which applies only when the specific traffic (6), then simply define the interesting traffic to the VPN to initiate and enable comms (7) corresponding

• ASA &amp; concentrator 3005 VPN fails

  Hi guys,.

  I set up a VPN between an ASA 5510 running OS 7.2 (Base) and a concentrator 3005.

  VPN stands up perfectly if launched from the ASA, but fails the Phase2 when momentum since the (1.1.1.5) 3005. Failing that, the ASA through the following errors:

  Dec 07 00:54:20 [IKEv1]: Group = 1.1.1.15, IP = 1.1.1.15, PHASE 1 COMPLETED
  Dec 07 00:54:20 [IKEv1 DEBUG]: Group = 1.1.1.15, IP = 1.1.1.15, payload processing ID
  Dec 07 00:54:20 [IKEv1 DECODER]: Group = 1.1.1.15, IP = 1.1.1.15, ID_IPV4_ADDR_SUBNET ID received - 172.19.0.0 - 255.255.0.0
  Dec 07 00:54:20 [IKEv1]: Group = 1.1.1.15, IP = 1.1.1.15, data Proxy received in payload ID remote IP subnet: address 172.19.0.0, the mask 255.255.0.0, protocol 0, Port 0
  Dec 07 00:54:20 [IKEv1 DEBUG]: Group = 1.1.1.15, IP = 1.1.1.15, payload processing ID
  Dec 07 00:54:20 [IKEv1 DECODER]: Group = 1.1.1.15, IP = 1.1.1.15, ID_IPV4_ADDR_SUBNET ID received - 192.168.2.0 - 255.255.255.0
  Dec 07 00:54:20 [IKEv1]: Group = 1.1.1.15, IP = 1.1.1.15, received from the IP local subnet in payload ID Proxy data: address 192.168.2.0, mask 255.255.255.0, protocol 0, Port 0
  Dec 07 00:54:20 [IKEv1 DEBUG]: Group = 1.1.1.15, IP = 1.1.1.15, processing notify payload
  Dec 07 00:54:20 [IKEv1]: Group = 1.1.1.15, IP = 1.1.1.15, QM IsRekeyed its not found old addr
  Dec 07 00:54:20 [IKEv1]: Group = 1.1.1.15, IP = 1.1.1.15, static check card Crypto, check card = mymap, seq = 9...
  Dec 07 00:54:20 [IKEv1]: Group = 1.1.1.15, IP = 1.1.1.15, static check card Crypto Card = mymap, seq = 9, ACL does not proxy IDs src:172.19.0.0 dst: 192.168.2.0
  Dec 07 00:54:20 [IKEv1]: Group = 1.1.1.15, IP = 1.1.1.15, remote peer IKE configured crypto card: dynmap
  Dec 07 00:54:20 [IKEv1 DEBUG]: Group = 1.1.1.15, IP = 1.1.1.15, ITS processing IPSec payload
  Dec 07 00:54:20 [IKEv1]: Group = 1.1.1.15, IP = 1.1.1.15, all IPSec security association proposals found unacceptable.
  Dec 07 00:54:20 [IKEv1 DEBUG]: Group = 1.1.1.15, IP = 1.1.1.15, sending prevent message
  

  What I gather from the above output is that seq 9 Crypto mymap map does not correspond to the proposal offered by the 3005. And guess what, it's not - so no surprise - but Seq 12 matches. SO I guess that the ASA is not verified the 3005 against the whole proposal Card Crypto. Fair supported? And if yes, what someone know why not?

  TIA

  See you soon

  Scott

  Hi Scott,.

  We found it.

  The dynamic Crypto map must be attached to the static Crypto map only once all static entries have been configured.

  The best way is to attach the dynamic map to the last line of the static map which is line no 65535.

  So follow these steps and let me know how it goes

  
  

  No map mymap 10-isakmp ipsec crypto dynamic dynmap

  
  

  map mymap 65535-isakmp ipsec crypto dynamic dynmap

  Please indicate in the commands above in the ASA configuration prompt.

  See you soon,.

  Nash.

• VPN concentrator + PIX on LAN-&gt; customers can not reach local servers

  Hello

  I have a problem wrt. remote access clients coming via a VPN3000 concentrator and trying to access local servers.

  For the topology:

  The internal network is 10.0.1.0/24. It connects with the outside world, as well as via a PIX DMZ; the PIX has 10.0.1.1 in the internal network.

  On the same LAN (internal), I have the VPN concentrator for the inside address 10.0.1.5. It assigns addresses in the 10.0.100.0/24 range to the

  VPN client-PCs.

  I can sucessfully connect using the VPN client SW to the hub, i.e. remote access clients out addresses

  the 10.0.100.0/24 range.

  The problem: access from VPN clients to internal network is * not * possible; for example, a customer with 10.0.100.1 cannot connect to

  internal to the 10.0.1.28 server.

  To my knowledge, this is a routing problem because the server (10.0.1.28) has no idea on how to reach customers in

  10.0.100.0/24. The only thing that the server is a default static route pointing to the PIX, i.e. 10.0.1.1.

  So I set up a static route on the PIX for 10.0.100.0 pointing to the hub-VPN, that is

  Mylan route 10.0.100.0 255.255.255.0 10.0.1.5 1

  This does not solve my problem though.

  In the PIX logs, I see the entries as follows:

  % 3 PIX-106011: deny entering (no xlate) tcp src trainee: 10.0.1.28 (atlas) / 445 intern dst: 10.0.100.1 (pending) 1064

  The PIX seems to abandon return packages, i.e. traffic from the server back to the client

  To my knowledge, the problem seems to be:

  Short traffic VPN - client-> Concentrator VPN-> Server-> PIX - where it gets moved.

  My reasoning: the PIX only sees the package back, i.e. the package back from the server to the client - and therefore decreasing the

  package because he has not seen the package from the client to the server.

  So here are my questions:

  (o) how do I configure the PIX that I be connectivity between my remote VPN clients (10.0.100.0/24) and

  computers servers on the local network (10.0.1.0/24)?

  (o) someone else you have something like this going?

  PS: Please note that the first obvious idea, installation of static routes on all machines on the local network is not an option here.

  Thank you very much in advance for your help,.

  -ewald

  Hello, PIX the because can not route traffic on the same interface (prior to version 7.0 anyway), I suggest you two places your hub to the outside with the inside of the legs on a zone demilitarized or (if you can not do a makeover of the network) you remove your pool with 10.0.100.0 - addresses and create a pool with 10.0.1.0 - addresses which is a part of the address space. No, NOT all. A little book that it is not used inside.

  Best regards

  Robert Maras

• VPN issues - 3005 to ASA5510

  We are moving from a concentrator 3005 to an ASA5510 and I have a few questions.

  In the 3005, you can disable and enable easy VPN tunnels. You go into politics and check or uncheck the box for enable. What is the method to temporarily disable a tunnel on the SAA? Through the ASDM of preference, for ease of management.

  Also, I want my remote access sessions to timeout after 8 hours. It shows in the tunnel policy in the ASDM its value for 8 (28800) hours, but I don't see this value in the config at all. I can't quite see a value of 86400 for the isakmp policy. If it is set in the ASDM like 8 hours, why doesn't it appear in the config? Has priority on the time-out, the policy of tunnel or isakmp policy?

  Thank you!

  Ryan,

  For your remote access to the vpn session users max connection time can be specified in attributes of tunnel group policy. Go to your group of tunnel in ASDM > general develop several obtions and uncheck maximum connect time here, you can specify minutes the vpn session will end when it reaches the time in minutes.

  example to specify 90 minutes you can also do this through cli, note it's not a time out that this will decrease the session in 90 minutes for all members of the Group of tunnel.

  group-policy attributes

  vpn-session-timeout 90

  You can disable it as:

  group-policy attributes

  no vpn-session-timeout

  as I don't know how to disable vpn L2L sessions support there is no option to turn on/off as in the vpn concentrators, this is a nice feature in the hub, but I haven't seen yet a feature of ASA like that or not aware of an Im.

  HTH

  Rgds

  Jorge

• 501 to 3000 PIX VPN concentrator

  I know that a lot of these configs have been covered here and have read a few today. Here's my dilemma.

  We have a VPN concentrator in our GOING to Florida. We set up a remote site of contract in another State. The customer is what allows us to place our PIX 501 on their (private) network and out to the internet to return to our VPN concentrator. According to the staff of the company, you have to cross a their corporate firewall. We have assigned a private to our internal ethernet IP address and has assigned a private one for us to use on our external interface on the PIX. The two private investigation periods are in the 192.168.129.x/24 (our inside) and 192.168.96.x/26 (on the outside provided by customer)

  Initially, they were to provide a public IP address peer with against our public IP hub. Now, they are unable to do so.

  They provided a possible PAT range of public IP addresses to go against, but there is no way of knowing what particular IP peer against. Is it possible to be able to point the VPN concentrator for a range of public IP addresses and hope a peers. I can ping from the PIX coming out to our public address of VPN concentrators. Any help would be appreciated.

  We configure ezvpn, however, the problem is that the vpn tunnel can only be activated from the pix not starting from the hub.

• 837 routers not reconnected to VPN concentrator

  When our grave 3015 VPN concentrator fails and restarts all non-837 routers connect again in a minute or 2, but the 837 hours or need a manual reset (clear isakmp). There are a number of different versions of IOS, and I presume some sort timeout setting must be configured. Despite scouring the forum, I can not know where I am going wrong. Any help appreciated.

  There is nothing in the specification IKE/ISAKMP who treats each detectig peer the other peer has declined, because of this, you can get data to enter a black hole when one side always considers that the tunnel is up and the other side has crashed/restarted and is attempting to build a new tunnel.

  To work around this problem we came with ISAKMP KeepAlive, or dead-Peer Detection (DPD). This sends a packet keepalive above the tunnel of PHase 1 every x seconds (configurable). If one end dies then the other end knows consolidated it fairly quickly and will lower its tunnels also.

  On the side of the router configuration is the following:

  ISAKMP crypto keepalive

  Make sure that you have configured in your 837. There was also some problems in the code very early with these KeepAlive, so if you do not have this command, but all your 837 seem to be code running earlier than the other routers, I would say that their transition to the last code that will insert itself into their memory/flash, which should solve your problem.

• aid required for the image backup vpn concentrator

  Hi, I am unable to download the vpn concentrator ios image to the tftp server. is someone can pls tell me what is the procedure for that. I can't find good documentation on it. pls help someone.

  concerning

  Assane

  Assane,

  You try to save the image of the hub to the VPN concentrator. Like the 4.7.2.D or the version E or F of the code. If this is the case, it is not possible to copy the image file from the hub to the tftp server.

  You must download the CEC file.

  He had an answer to your question earlier, but it pointed you on how to make a backup of your CONFIGURATION file.

  If this answers your question, feel free to write it down.

• Configuration file for the VPN concentrator

  Hello

  I have a text-based VPN concentrator configuration file, and I want to know if there is a configuration guide of Concentrator VPN that I can use to refer to this file. The configuration on cisco.com guide is currently for the GUI based configuration.

  Furthermore, if there is a tool/utility that will read the configuration file in the format GUI without physical access to the device, which will also help.

  Thanks in advance for any assistance.

  There is a "XML export screen" in the management section of the files on the VPN concentrator. You can export the current configuration of the concentrator in a XML format, which provides the labels and values for the fields in the configuration file.

  http://www.Cisco.com/en/us/docs/security/vpn3000/vpn3000_47/Administration/Guide/Fileman.html#wpxref53361

• Cisco VPN Client behind PIX 515E,-&gt; VPN concentrator

  I'm trying to configure a client as follows:

  The user is running Cisco VPN Client 4.0. They are behind a 6.1 PIX 515E (4), and I need to connect to a VPN concentrator located outside of our network. We use PAT for address translation. As far as I know, to allow ipsec through Firewall 1 tunnel, I need to upgrade the pix to 6.3 and activate "fixup protocol esp-ike.

  Is there another way to do this? I am also curious to know how much more easy/better this will work if we were dealing with pptp.

  You don't necessarily need to fixup protocol esp-ike active. The remote Hub there encapsulation NAT - T enabled so that clients behind the NAT can run?

• 3015 VPN concentrator Version help

  The 3015 comes not only as no redundant hw together? If not, how do I know which version I have?

  I don't have the CD of VPN client supplied with the appliance, can it be downloaded or bought?

  Thanks for any help.

  Jeff

  The 3015 comes with no card encryption HW (SEPs). This is the same chassis as the 3030, 3060 and 3080, the only difference between the models is the memoy in the box and how many MS and feeds they included. The 3015 allows you to upgrade to a more powerful area by simple addition of MS, but as is, it's basically empty.

  The client code and the VPN concentrator here are downloadable from EAC:

  http://www.Cisco.com/Kobayashi/SW-Center/SW-VPN.shtml

  You will need a CCO login that has access to this page.

• BW policy on VPN concentrator

  I've got a 3030 VPN concentrator with 4.0.1 B. I OS release have implemented a policy of BW for the VPN site - to many. Is it possible to check/see if the policy is applied (for example, deleted if traffic over the limit)?

  Thank you, Meg

  Monitoring - statistics - bandwidth Mgmt should give you some details.

• Download the firmware from the 3030 VPN concentrator?

  Hello

  I would like to download a newer firmware our vpn concentrator but wish to download a copy of the old firmware. Is this possible and how can I do? It seems that the only option is to download, as well as a fall on a document that indicate how to go back but still doesn't explain not how can I get a copy of the old firmware. Thank you

  I think that Cisco pulls some of the older minor revisions out of the web for major versions when the image becomes a bit old. 3.5 (3), you should be fine with 3.6 (which is available for download). You cannot copy the picture from the hub as far as I know.