VPN via Pix 515

Similar Questions

• VPN for PIX 515 allowing access to a single host

  I have already setup on my PIX 515 a VPN connection, which allows the user to connect to our network via a cisco VPN client to access network resources.

  I want to configure now is an another VPN connection that external users can use but would only allow access to a host.

  E.g. I would like to VPN in my site but would be allowed to access the 10.1.1.1 on my network.

  How can I do this? What I have to install VPNGROUP another and somehow an access list to allow only traffic to a host of configuration. Can anyone help with the correct syntax for the PIX.

  Thank you

  Scott

  You will now have a bunch of commands "vpngroup" in your PIX, simply go into config mode and add more commands 'vpngroup' but with a different groupname. The VPN client then uses this group name to connect to the PIX.

  Another way to allow only access to a host for this PIX is to split tunnelling on this group, as well as in the tunnel of split ACL set only as a host.

• VPN to pix 515

  Good day to all,

  I'm trying to configure the client VPN to a PIX 515.  Once VPN'ed in, the traffic is going no where, but on THIS subnet. The Vlan that we are trying to achieve is a 10.111.250.x/23.  Once VPN'ed in the allocation of an IP address is 10.111.250.33 - 10.111.250.63. We can VPN in and get VPN IP assigned, but we cannot get anywhere inside VLANs.  I was sure that it could be done in a layer 2.  You can view the assigned addresses VPN arped entries and the inside address Vlan on the Pix.

  Keep in mind, my first thought was to change the VPN address assigned, but we do not want to carry on this Vlan especially because access is very limited.

  Is it possible to make this work?  If I have to redo attributes and policy, I.

  Thank you

  Dwane

  The output shows that the PIX is decrypt packets, but not encryption.

  So there is a good chance that packets are sent within the network but not to return.

  Check the following:

  management-access within the--> this command should allow ping to the IP of the VPN PIX inside (make sure you that if you can TEST this IP address when connected)

  Verify that the default gateway within the network (behind the PIX) is the current inside the property intellectual of the PIX.

  After these tests, post again "sh cry ips its"

  Federico.

• Accounting customer VPN on PIX 515 worm problem. 6.3

  Hello everyone! Is it possible to configure PIX 515 worm. 6.3 to send logs to the RADIUS to break when a VPN Client user loggs in and outside loggs? I can't find any aaa accounting command which allows this.

  Hello

  Accounting of VPN was added in PIX 7.x. It is not available with 6.x

  Kind regards

  Vivek

• Cisco ASA 5510 VPN with PIX 515

  Hello

  I have VPN between Cisco ASA and Cisco PIX.

  I saw in my syslog server this error that appears once a day, more or less:

  Received a package encrypted with any HIS correspondent, drop

  I ve seen issue in another post, but in none of then the solution.

  Here are my files from the firewall configuration:

  Output from the command: 'show running-config '.

  : Saved
  :
  ASA Version 8.2 (1)
  Crypto ipsec transform-set ESP-DES-MD5 esp - esp-md5-hmac
  life crypto ipsec security association seconds 28800
  Crypto ipsec kilobytes of life - safety 4608000 association
  card crypto WAN_map2 2 corresponds to the address WAN_cryptomap_1
  card crypto WAN_map2 2 set pfs
  card crypto WAN_map2 2 peer 62.80.XX game. XX
  map WAN_map2 2 game of transformation-ESP-DES-MD5 crypto
  card crypto WAN_map2 2 defined security-association 2700 seconds life
  card crypto WAN_map2 2 set nat-t-disable
  card crypto WAN_map2 WAN interface
  enable LAN crypto ISAKMP
  ISAKMP crypto enable WAN
  crypto ISAKMP policy 1
  preshared authentication
  the Encryption
  md5 hash
  Group 5
  lifetime 28800
  No encryption isakmp nat-traversal
  tunnel-group 62.80.XX. XX type ipsec-l2l
  tunnel-group 62.80.XX. IPSec-attributes of XX
  pre-shared-key *.
  

  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

  8.0 (4) version PIX
  !
  Crypto ipsec transform-set ESP-DES-MD5 esp - esp-md5-hmac
  life crypto ipsec security association seconds 28800
  Crypto ipsec kilobytes of life - safety 4608000 association
  card encryption VPN_map2 3 corresponds to the address VPN_cryptomap_2
  card encryption VPN_map2 3 set pfs
  card crypto VPN_map2 3 peer 194.30.XX game. XX
  VPN_map2 3 transform-set ESP-DES-MD5 crypto card game
  card encryption VPN_map2 3 defined security-association life seconds 2700
  card encryption VPN_map2 3 set security-association kilobytes of life 4608000
  card VPN_map2 3 set nat-t-disable encryption
  VPN crypto map VPN_map2 interface
  crypto ISAKMP enable VPN
  crypto ISAKMP allow inside
  crypto ISAKMP policy 30
  preshared authentication
  the Encryption
  md5 hash
  Group 5
  lifetime 28800
  No encryption isakmp nat-traversal
  ISAKMP crypto am - disable
  attributes of Group Policy DfltGrpPolicy
  Protocol-tunnel-VPN IPSec
  tunnel-group 194.30.XX. XX type ipsec-l2l
  tunnel-group 194.30.XX. IPSec-attributes of XX
  pre-shared-key *.
  

  If you need more information dedailed ask me questions.

  Thanks in advance for your help.

  Javi

  Hi Javi,

  Please after the release of "see broadcasting DfltGrpPolicy of any political group." See if you have the "vpn-idle-timoeout" command configured in that. If so, please change to "vpn-idle-timeout no" and see if that stops at these popping up error messages.

  http://www.Cisco.com/en/us/docs/security/ASA/asa80/command/reference/uz.html#wp1571426

  Thank you and best regards,

  Assia

• VPN to PIX access problem.

  I set up PPTP VPN on PIX 515 access with unrestricted license for Windows-based computers. I can connect but I'm unable to access all the resources on the network. I suspect this has something to access the list, but I don't know where to start. Here's the relevant part of the PIX config:

  access-list all-traffic ip to allow a whole

  access-list 100 permit icmp any any echo response

  access-list 100 permit icmp any one time exceed

  access-list 100 permit everything all unreachable icmp

  .

  IP address outside x.x.x.130 255.255.255.252

  IP address inside 192.168.254.1 255.255.255.0

  IP address x.x.x.97 255.255.255.224 DMZ1

  address IP DMZ2 192.168.251.1 255.255.255.0

  alarm action IP verification of information

  alarm action attack IP audit

  IP local pool vpnpool 192.168.254.201 - 192.168.254.254

  .

  Global (outside) 1 x.x.x.65 - x.x.x.93 netmask 255.255.255.224

  Global (outside) 1 x.x.x.94 netmask 255.255.255.224

  NAT (inside) 1 access-list all-traffic 0 0

  (DMZ1) 1 access-list all-traffic NAT 0 0

  Access-group 100 in external interface

  Route outside 0.0.0.0 0.0.0.0 x.x.x.129 1

  .

  Sysopt connection permit-pptp

  Telnet 192.168.254.0 255.255.255.0 inside

  Telnet timeout 5

  SSH timeout 5

  Console timeout 0

  VPDN Group 1 accept dialin pptp

  PAP VPDN Group 1 ppp authentication

  VPDN Group 1 chap for ppp authentication

  VPDN Group 1 ppp authentication mschap

  VPDN group ppp 1 encryption mppe auto

  VPDN Group 1 client configuration address local vpnpool

  VPDN Group 1 pptp echo 60

  VPDN Group 1 client authentication local

  VPDN username * password *.

  VPDN allow outside

  dhcpd address 192.168.254.100 - 192.168.254.200 inside

  dhcpd dns x.x.x.131 x.x.x.200

  dhcpd rental 86400

  dhcpd ping_timeout 750

  dhcpd allow inside

  Looks like you forgot to add a "nat 0" defines that there are no PAT beween your local inside network and the PPTP DHCP pool.

  PPTP pool must be different from the inside pool otherwise it is not routable correctly.

  no ip local pool vpnpool 192.168.254.201 - 192.168.254.254

  # Choose a new network PPTP pool that is not in use

  example of dansMon # is 192.168.1.0/24

  IP local pool vpnpool 192.168.1.1 - 192.168.1.254

  access-list 101 permit ip 192.168.254.0 255.255.255.0 192.168.1.0 255.255.255.0

  (Inside) NAT 0-list of access 101

  See this site for more information:

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

  http://www.Cisco.com/pcgi-bin/support/browse/psp_view.pl?p=hardware:PIX & s = Software_Configuration

  see PPTP

  sincerely

  Patrick

• Cisco Pix 515 VPN problems

  Hi all

  Here's my problem, I have 2 PIX 515 firewall...

  I'm trying to implement a VPN site-to site between 2 of our websites...

  Two of these firewalls currently run another site to site VPN so I know who works...

  I can't do the second site to the site to launch the VPN... when looking on the syslogs I get refused packages...

  Protected networks are:

  172.16.48.0/24 and 172.16.4.0/22

  If I try to ping from the Cisco (172.16.48.4) to 172.16.4.5, I get the following syslog:

  2 sep 02 2008 08:59:47 106001 172.16.48.4 172.16.4.5 incoming TCP connection doesn't deny from 172.16.48.4/1231 to 172.16.4.5/135 SYN flags on the interface inside

  It seems that the tunnel is trying to initiate, but something is blocking the internal traffic to penetrate through the VPN.

  Don't know what that might be, the other VPN are working properly.

  Any help would be great...

  I enclose a copy of one of the configs...

  Let me know if you need another...

  no road inside 172.16.4.0 255.255.252.0 172.16.48.1 1

  Remove this path should you get. Please rate if it does. Similarly, if you have a road similar to the other end, it should be deleted as well.

• termination of VPN client 4.0 on pix 515

  I am trying to connect the cisco 4.0 vpn client to a worm of pix 515 6.1 and receive as a result of errors that I guess are the related hashing algorithm but am not sure. Only DES is not enabled 3DES. Config output Cisco post interprets but apparently no error in config.

  Journal of VPN client:

  Cisco Systems VPN Client Version 4.0 (Rel)

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

  Customer type: Windows, Windows NT

  Running: 5.0.2195

  1 10:58:34.890 25/09/03 Sev = Info/4 CM / 0 x 63100002

  Start the login process

  2 10:58:34.906 25/09/03 Sev = Info/4 CVPND/0xE3400001

  Microsoft's IPSec Policy Agent service stopped successfully

  3 10:58:34.906 25/09/03 Sev = Info/4 CM / 0 x 63100004

  Establish a connection using Ethernet

  4 10:58:34.906 25/09/03 Sev = Info/4 CM / 0 x 63100024

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

  5 10:58:35.953 25/09/03 Sev = Info/6 IKE/0x6300003B

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

  6 10:58:36.000 25/09/03 Sev = Info/4 IKE / 0 x 63000013

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

  7 10:58:36.000 25/09/03 Sev = Info/4 IPSEC / 0 x 63700008

  IPSec driver started successfully

  8 10:58:36.000 25/09/03 Sev = Info/4 IPSEC / 0 x 63700014

  Remove all keys

  9 10:58:41.093 25/09/03 Sev = Info/4 IKE / 0 x 63000021

  Retransmit the last package!

  10 10:58:41.093 25/09/03 Sev = Info/4 IKE / 0 x 63000013

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

  11 10:58:46.093 25/09/03 Sev = Info/4 IKE / 0 x 63000021

  Retransmit the last package!

  12 10:58:46.093 25/09/03 Sev = Info/4 IKE / 0 x 63000013

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

  13 10:58:51.093 25/09/03 Sev = Info/4 IKE / 0 x 63000021

  Retransmit the last package!

  14 10:58:51.093 25/09/03 Sev = Info/4 IKE / 0 x 63000013

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

  15 10:58:56.093 25/09/03 Sev = Info/4 IKE / 0 x 63000017

  Marking of IKE SA delete (I_Cookie = 20FC277498A5D2DC R_Cookie = 0000000000000000) reason = DEL_REASON_PEER_NOT_RESPONDING

  16 10:58:56.593 25/09/03 Sev = Info/4 IKE/0x6300004A

  IKE negotiation to throw HIS (I_Cookie = 20FC277498A5D2DC R_Cookie = 0000000000000000) reason = DEL_REASON_PEER_NOT_RESPONDING

  17 10:58:56.593 25/09/03 Sev = Info/4 CM / 0 x 63100014

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

  18 10:58:56.593 25/09/03 Sev = Info/5 CM / 0 x 63100025

  Initializing CVPNDrv

  19 10:58:56.593 25/09/03 Sev = Info/4 IKE / 0 x 63000001

  Signal received IKE to complete the VPN connection

  20 10:58:56.625 25/09/03 Sev = critique/1 CVPND/0xE3400001

  Service Microsoft's IPSec Policy Agent started successfully

  21 10:58:57.093 25/09/03 Sev = Info/4 IPSEC / 0 x 63700014

  Remove all keys

  22 10:58:57.093 25/09/03 Sev = Info/4 IPSEC / 0 x 63700014

  Remove all keys

  23 10:58:57.093 25/09/03 Sev = Info/4 IPSEC / 0 x 63700014

  Remove all keys

  24 10:58:57.093 25/09/03 Sev = Info/4 IPSEC/0x6370000A

  IPSec driver successfully stopped

  Journal of Pix:

  crypto_isakmp_process_block: CBC x.x.x.194, dest x.x.x.226

  Peer VPN: ISAKMP: approved new addition: ip:x.x.x.194 Total VPN peer: 1

  Peer VPN: ISAKMP: ip:x.x.x.194 Ref cnt is incremented to peers: 1 Total VPN EEP

  RS: 1

  Exchange OAK_AG

  ISAKMP (0): treatment ITS payload. Message ID = 0

  ISAKMP (0): audit ISAKMP transform 1 against the policy of priority 1

  ISAKMP: encryption... What? 7?

  ISAKMP: hash SHA

  ISAKMP: default group 2

  ISAKMP: preshared extended auth

  ISAKMP: type of life in seconds

  ISAKMP: lifespan (IPV) 0x0 0 x 20 0xc4 0x9b

  ISAKMP: attribute 3584

  ISAKMP (0): atts are not acceptable. Next payload is 3

  ISAKMP (0): audit ISAKMP transform against the policy of priority 1 2

  ISAKMP: encryption... What? 7?

  ISAKMP: MD5 hash

  ISAKMP: default group 2

  ISAKMP: preshared extended auth

  ISAKMP: type of life in seconds

  ISAKMP: lifespan (IPV) 0x0 0 x 20 0xc4 0x9b

  ISAKMP: attribute 3584

  ISAKMP (0): atts are not acceptable. Next payload is 3

  ISAKMP (0): audit ISAKMP transform 3 against the policy of priority 1

  ISAKMP: encryption... What? 7?

  ISAKMP: hash SHA

  ISAKMP: default group 2

  ISAKMP: preshared auth

  ISAKMP: type of life in seconds

  ISAKMP: lifespan (IPV) 0x0 0 x 20 0xc4 0x9b

  ISAKMP: attribute 3584

  ISAKMP (0): atts are not acceptable. Next payload is 3

  ISAKMP (0): audit ISAKMP transform 4 against the policy of priority 1

  ISAKMP: encryption... What? 7?

  ISAKMP: MD5 hash

  ISAKMP: default group 2

  ISAKMP: preshared auth

  ISAKMP: type of life in seconds

  ISAKMP: lifespan (IPV) 0x0 0 x 20 0xc4 0x9b

  ISAKMP: attribute 3584

  ISAKMP (0): atts are not acceptable. Next payload is 3

  ISAKMP (0): audit ISAKMP transform 5 against the policy of priority 1

  ISAKMP: encryption... What? 7?

  ISAKMP: hash SHA

  ISAKMP: default group 2

  ISAKMP: preshared extended auth

  ISAKMP: type of life in seconds

  ISAKMP: lifespan (IPV) 0x0 0 x 20 0xc4 0x9b

  ISAKMP: attribute 3584

  ISAKMP (0): atts are not acceptable. Next payload is 3

  ISAKMP (0): audit ISAKMP transform 6 against the policy of priority 1

  ISAKMP: encryption... What? 7?

  ISAKMP: MD5 hash

  ISAKMP: default group 2

  ISAKMP: preshared extended auth

  ISAKMP: type of life in seconds

  ISAKMP: lifespan (IPV) 0x0 0 x 20 0xc4 0x9b

  ISAKMP: attribute 3584

  ISAKMP (0): atts are not acceptable. Next payload is 3

  ISAKMP (0): audit ISAKMP transform 7 against the policy of priority 1

  ISAKMP: encryption... What? 7?

  ISAKMP: hash SHA

  ISAKMP: default group 2

  ISAKMP: preshared auth

  ISAKMP: type of life in seconds

  ISAKMP: lifespan (IPV) 0x0 0 x 20 0xc4 0x9b

  ISAKMP: attribute 3584

  ISAKMP (0): atts are not acceptable. Next payload is 3

  ISAKMP (0): audit ISAKMP transform 8 against the policy of priority 1

  ISAKMP: encryption... What? 7?

  ISAKMP: MD5 hash

  ISAKMP: default group 2

  ISAKMP: preshared auth

  ISAKMP: type of life in seconds

  ISAKMP: lifespan (IPV) 0x0 0 x 20 0xc4 0x9b

  ISAKMP: attribute 3584

  ISAKMP (0): atts are not acceptable. Next payload is 3

  ISAKMP (0): audit ISAKMP transform 9 against the policy of priority 1

  ISAKMP: 3DES-CBC encryption

  ISAKMP: hash SHA

  ISAKMP: default group 2

  ISAKMP: preshared extended auth

  ISAKMP: type of life in seconds

  ISAKMP: lifespan (IPV) 0x0 0 x 20 0xc4

  crypto_isakmp_process_block: CBC x.x.x.194, dest x.x.x.226

  Peer VPN: ISAKMP: ip:x.x.x.194 Ref cnt is incremented to peers: 2 Total VPN EEP

  RS: 1

  Peer VPN: ISAKMP: ip:x.x.x.194 Ref cnt decremented to peers: 1 Total VPN EEP

  RS: 1

  crypto_isakmp_process_block: CBC x.x.x.194, dest x.x.x.226

  Peer VPN: ISAKMP: ip:x.x.x.194 Ref cnt is incremented to peers: 2 Total VPN EEP

  RS: 1

  Peer VPN: ISAKMP: ip:x.x.x.194 Ref cnt decremented to peers: 1 Total VPN EEP

  RS: 1

  ISAKMP (0): retransmission of phase 1...

  ISAKMP (0): retransmission of phase 1...

  ISAKMP (0): delete SA: src x.x.x.194 dst x.x.x.226

  ISADB: Reaper checking HIS 0x80db91c8, id_conn = 0 DELETE IT!

  Peer VPN: ISAKMP: ip:x.x.x.194 Ref cnt decremented to peers: 0 Total of VPN EEP

  RS: 1

  Peer VPN: ISAKMP: deleted peer: ip:x.x.x.194 VPN peer Total: 0

  ISAKMP: Remove the peer node for x.x.x.194

  Thanks for any help

  Hello

  Pix isakmp policy should have DES, MD5, and group 2 for the 4.x to connect Cisco VPN client, these are proposals that the client sends to the server...

  http://www.Cisco.com/univercd/CC/TD/doc/product/VPN/client/rel4_0/admin_gd/vcach6.htm#1157757

  This link will show you IKE proposals be configured on the PIX (VPN server)

  Arthur

• VPN to PIX, Win2K, Active Directory - where to start?

  Hello world.

  I am waiting the arrival of a PIX 515 and 501 for firewalls and creating VPN between my main site and a remote location. Remoteness is having a LAN installed but will not have a real Win2k domian while the main site is an area complete with exchange and AD win2k. The two site will connect to INet w / cable modems.

  Here's the question:

  Is it possible to have this remote site to be part of my site main area via the VPN? Can I set up a server on the remote site to replicate AD to, in which case the VPN is stopped for some reason any. Do I need to open ports on the firewall or not because it will be on a VPN?

  Is it an easy thing to do? Is a beginner at the top of his head?

  Thanks in advance for any advice.

  Marc

  No router required - basically, everything will be static routed - your customers, regardless of the site, will have the pix as the default gateway. each pix will have a default gateway configured, by you, by a statement of 'road '. Each pix ACL crypto will also act as a static route through the tunnel to the other pix

• VPN concentrator + PIX on LAN-> 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

• PIX - 515 does not identify Tokenring Interfacecard

  Hello

  I installed a PIX-1 TR interface in the PIX 515. Start ok, 'answer' no configuration. SH LVE and sho int etc. presents only the build Ethernet0 and Eth1 but no interface tokenring.

  HS release looks like as follows.

  Thanks Ruedi

  pixfirewall # sh ver

  Cisco PIX Firewall Version 6.2 (2)

  Cisco PIX Device Manager Version 2.0 (2)

  Updated Saturday, June 7 02 17:49 by Manu

  pixfirewall until 10 mins dry 14

  Material: PIX - 515, 32 MB RAM, Pentium 200 MHz processor

  I28F640J5 @ 0 x 300 Flash, 16 MB

  BIOS Flash AT29C257 @ 0xfffd8000, 32 KB

  0: ethernet0: the address is 0003.6bf6.a8a9, irq 11

  1: ethernet1: the address is 0003.6bf6.a8aa, irq 10

  Features licensed:

  Failover: disabled

  VPN - A: enabled

  VPN-3DES: disabled

  Maximum Interfaces: 3

  Cut - through Proxy: enabled

  Guardians: enabled

  URL filtering: enabled

  Internal hosts: unlimited

  Throughput: unlimited

  Peer IKE: unlimited

  Serial number: 405341167 (0x182903ef)

  Activation key running: xxxxxxxxx

  Modified configuration of enable_15 to 13:11:47.490 UTC Tuesday, December 23, 2003

  pixfirewall #.

  Hello

  Token-Ring is no longer supported, I think since version 6.0.

• Upgrade from PIX 515

  Hi all

  My company needs upgrade its PIX 515 to have the function VPN 3DES for remote site connection. So I just need to buy a license of 3DES for the PIX functionality? and can I also upgrade the IOS 6.1 so that I can use PDM to config the PIX? And I also need to upgrade the memory in the PIX?

  Thank you very much!

  Best regards

  Teru Lei

  Yes to the first question.

  Better 6.2 and pdm 2.1 I think.

  How much memory do you have? Reach

  http://www.Cisco.com/en/us/customer/products/sw/secursw/ps2120/prod_release_note09186a00800b1138.html#xtocid4

  There is memory for pix 6.2 requirements

  Good luck!

  --

  Alexis Fidalgo

  Systems engineer

  AT & T Argentina

• Save the password on the Client VPN with PIX

  I'm running a PIX 515 6.1 (2) configured for a small number of VPN clients. I want VPN clients to automatically remember the password of login for users do not have to enter it each time (we have an application which periodically autoconnexions).

  While it is a configurable option with concentrators 3000 series, it seems not be configurable with the PIX.

  The only work around, I can find is to make the connection file (.pcf) read-only and set SaveUserPassword = 1. The problem

  which is the password, and then must be stored in clear text in the file and it becomes inconvenient for the user to change their password.

  Does anyone know if the command exists on the PIX from the VPN client to save the connection password?

  Thank you

  Misha

  The command to do this is not currently available on the PIX. He has just been included in the IOS EZVPN server functionality, but have not heard of anything anyone yet as to if it will be included in the PIX.

  If you want this feature, do not hesitate to contact your account manager and have them grow for him, the more customers requesting a new feature faster he gets.

• PIX 515 adding a second DMZ

  Hello

  This is the specification of our PIX:

  Cisco PIX Firewall Version 6.2 (2)

  Cisco PIX Device Manager Version 2.0 (2)

  Updated Saturday, June 7 02 17:49 by Manu

  Firewall of the hours - days.

  Material: PIX - 515, 32 MB RAM, Pentium 200 MHz processor

  I28F640J5 @ 0 x 300 Flash, 16 MB

  BIOS Flash AT29C257 @ 0xfffd8000, 32 KB

  0: ethernet0: the address is 0003.6bf6.74a2, irq 11

  1: ethernet1: the address is 0003.6bf6.74a3, irq 10

  2: ethernet2: the address is 00a0.c944.395b, irq 9

  Features licensed:

  Failover: disabled

  VPN - A: enabled

  VPN-3DES: enabled

  Maximum Interfaces: 3

  Cut - through Proxy: enabled

  Guardians: enabled

  URL filtering: enabled

  Internal hosts: unlimited

  Throughput: unlimited

  Peer IKE: unlimited

  Is it possible to add a second DMZ simply by adding another network card to the system? If this is not the case, what I have to do to get a second DMZ?

  Kind regards

  Alan

  You have already 3 interfaces, and your license only allows 3 (that you run limited license). Read the line of your worm above show: maximum Interfaces: 3

  You must update your Unrestricted license, then you can have up to 6 interfaces.

  It will be useful.

  Steve

• VPN via a natted router

  Hello

  I think that vpn via nat is 'enabled' in the 6.3.1 software for the pix? I have problems to run. Can someone give me directions, including everything I need to know about the router?

  I guess that everything that I have to do is create a static nat from 1 to 1 of the legal IP outside the pix outside IP router? Then configure the vpn as usual to accept vpn as usual (I use the 4.0.1 cisco client).

  I'd appreciate any help.

  Thanks for your time

  Andy

  I think that you need to configure the NAT-Traversal, the command to do this is isakmp nat-traversal]

  NAT - T can be enabled or disabled:

  By default? OFF for site to site tunnels

  By default? We'RE for hardware and software VPN clients