Cisco VPN Client follow-up

Hello

I have a Cisco 2821 and ASA 5510 VPN router in my network.

Our remote users are using Cisco VPN Client 5.0.07 and I need to track on a server and keep their login information to generate reports for my manager.

Could you please let me know how I can do this trick of surveillance?

Thank you

Mike

It can be done by choosing one of three types of monitoring of the performance of the VPN:

http://www.Cisco.com/en/us/docs/net_mgmt/vpn_solutions_center/1.1/user/guide/VPN_UG5.html

I hope this helps!

Tags: Cisco Security

Similar Questions

  • Receive message "Validation of C:\WINDOWS\System32\VSINIT.dll failure" error message when trying to run Cisco VPN Client.

    windows\system32\vsinit.dll

    I try to run CISCO "VPN Client" connect from my PC at home for my work PC.

    Then, I get a message:

    Validation failed for C:\WINDOWS\System32\VSINIT.dll

    Any ideas?

    Martin

    Hello

    Run the checker system files on the computer. Link, we can see: Description of Windows XP and Windows Server 2003 System File Checker (Sfc.exe): http://support.microsoft.com/kb/310747

    Note that: if he asks you the service pack CD, follow these steps from the link: you are prompted to insert a Windows XP SP2 CD when you try to run the tool on a Windows XP SP2 computer system File Checker: http://support.microsoft.com/kb/900910 (valid for Service pack 3)

    If the steps above is not enough of it please post your request in the TechNet forum for assistance: http://social.technet.microsoft.com/Forums/en/category/windowsxpitpro

  • Problems to connect via the Cisco VPN client IPSec of for RV180W small business router

    Hello

    I tried to configure my router Cisco of RV180W as a customer VPN IPSec, but have encountered a problem that I hope someone can help me with. "" I managed to do the work of configuration so that the Cisco's VPN IPSec client authenticates successfully with the XAUTH user, I put on the router, but during the negotiation, the client ends with the following, which appears several times on the router error message: ' Mar 20 Oct 19:41:53 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [34360] has no config mode.

    I've read around the internet and a number of people seem to say that the Cisco VPN Client is not compatible with the router, but the same thing happens to my iPhone VPN client.

    Is it possible that this can be implemented? Below, I have attached the full configuration files and the log files. Thank you much in advance.

    Router log file (I changed the IP addresses > respectively as well as references to MAC addresses)

    Mar 20 Oct 20:03:10 2015 (GMT + 0000): [r1] [IKE] INFO: floating ports NAT - T with counterpart > [44074]
    Mar 20 Oct 20:03:10 2015 (GMT + 0000): [r1] [IKE] WARNING: notification to ignore INITIAL-CONTACT > [44074] because it is admitted only after the phase 1.
    Mar 20 Oct 20:03:10 2015 (GMT + 0000): [r1] [IKE] INFO: NAT - D payload does not match for > [4500]
    Mar 20 Oct 20:03:10 2015 (GMT + 0000): [r1] [IKE] INFO: NAT - D payload does not match for > [44074]
    Mar 20 Oct 20:03:10 2015 (GMT + 0000): [r1] [IKE] INFO: received unknown Vendor ID
    Mar 20 Oct 20:03:10 2015 (GMT + 0000): [r1] [IKE] INFO: received Vendor ID: CISCO-UNITY
    Mar 20 Oct 20:03:10 2015 (GMT + 0000): [r1] [IKE] INFO: NAT detected: is located behind a device. NAT and alsoPeer is behind a NAT device
    Mar 20 Oct 20:03:10 2015 (GMT + 0000): [r1] [IKE] INFO: request sending Xauth for > [44074]
    Mar 20 Oct 20:03:10 2015 (GMT + 0000): [r1] [IKE] INFO: ISAKMP Security Association established for > [4500] -> [44074] with spi =>.
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] INFO: receives the type of the attribute 'ISAKMP_CFG_REPLY' of > [44074]
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] INFO: login successful for the user "myusername".
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] INFO: myusername XAuthUser connected from the IP >
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] INFO: sending of information Exchange: Notify payload [10381]
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] INFO: receives the type of the attribute 'ISAKMP_CFG_REQUEST' of > [44074]
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no config mode
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no config mode
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no config mode
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no config mode
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] WARNING: ignored attribute 5
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no config mode
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no config mode
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no config mode
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no config mode
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no config mode
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no config mode
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] WARNING: attribute ignored 28683
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no mode config

    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] WARNING: attribute ignored 28684
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no config mode
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: local configuration for > [44074] has no mode config

    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] ERROR: remove the invalid payload with doi:0.
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] INFO: purged-Association of ISAKMP security with proto_id = ISAKMP and spi =>.
    Mar 20 Oct 20:03:15 2015 (GMT + 0000): [r1] [IKE] INFO: myusername XAuthUser Logged Out of the IP >
    Mar 20 Oct 20:03:16 2015 (GMT + 0000): [r1] [IKE] INFO: ISAKMP Security Association deleted for > [4500] -> [44074] with spi =>

    The router configuration

    IKE policy

    VPN strategy

    Client configuration

    Hôte : < router="" ip=""> >

    Authentication group name: remote.com

    Password authentication of the Group: mysecretpassword

    Transport: Enable Transparent Tunneling; IPSec over UDP (NAT/PAT)

    Username: myusername

    Password: mypassword

    Please contact Cisco.

    Correct, the RV180 is not compatible with the Cisco VPN Client.  The Iphone uses the Cisco VPN Client.

    You can use the PPTP on the RV180 server to connect a PPTP Client.

    In addition, it RV180 will allow an IPsec connection to third-party customers 3.  Greenbow and Shrew Soft are 2 commonly used clients.

  • 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?

  • PIX: Cisco VPN Client connects but no routing

    Hello

    We have a Cisco PIX 515 with software 7.1 (2). He accepts Cisco VPN Client connections with no problems, but no routing does to internal networks directly connected to the PIX. For example, my PC is affected by the IP 172.16.2.57 and then ping does not respond to internal Windows server 172.16.0.12 or trying to RDP. The most irritating thing is that these attempts are recorded in the system log, but always ended with "SYN timeout", as follows:

    2009-01-06 23:23:01 Local4.Info 217.15.42.214% 302013-6-PIX: built 3315917 for incoming TCP connections (172.16.2.57/1283) outside:172.16.2.57/1283 inside: ALAI2 / 3389 (ALAI2/3389)

    2009-01-06 23:23:31 Local4.Info 217.15.42.214% 302014-6-PIX: TCP connection disassembly 3315917 for outside:172.16.2.57/1283 inside: ALAI2 / 3389 duration 0:00:30 bytes 0 SYN Timeout

    2009-01-06 23:23:31 Local4.Debug 217.15.42.214% 7-PIX-609002: duration of disassembly-outside local host: 172.16.2.57 0:00:30

    We tried to activate and deactivate "nat-control", "permit same-security-traffic inter-interface" and "permit same-security-traffic intra-interface", but the results are the same: the VPN connection is successfully established, but remote clients cannot reach the internal servers.

    I enclose the training concerned in order to understand the problem:

    interface Ethernet0

    Speed 100

    full duplex

    nameif outside

    security-level 0

    IP address xx.yy.zz.tt 255.255.255.240

    !

    interface Ethernet1

    nameif inside

    security-level 100

    172.16.0.1 IP address 255.255.255.0

    !

    access extensive list ip 172.16.0.0 inside_nat0_outbound allow 255.255.255.0 172.16.2.56 255.255.255.248

    !

    access extensive list ip 172.16.0.0 outside_cryptomap_dyn_20 allow 255.255.255.0 172.16.2.56 255.255.255.248

    !

    VPN_client_group_splitTunnelAcl list standard access allowed 172.16.0.0 255.255.255.0

    !

    IP local pool pool_vpn_clientes 172.16.2.57 - 172.16.2.62 mask 255.255.255.248

    !

    NAT-control

    Global xx.yy.zz.tt 12 (outside)

    NAT (inside) 0-list of access inside_nat0_outbound

    NAT (inside) 12 172.16.0.12 255.255.255.255

    !

    internal VPN_clientes group strategy

    attributes of Group Policy VPN_clientes

    xxyyzz.NET value by default-field

    internal VPN_client_group group strategy

    attributes of Group Policy VPN_client_group

    Split-tunnel-policy tunnelspecified

    value of Split-tunnel-network-list VPN_client_group_splitTunnelAcl

    xxyyzz.local value by default-field

    !

    I join all the details of the cryptographic algorithms because the VPN is successfully completed, as I said at the beginning. In addition, routing tables are irrelevant in my opinion, because the inaccessible hosts are directly connected to the internal LAN of the PIX 515.

    Thank you very much.

    can you confirm asa have NAT traversal allow otherwise, activate it in asa and vpn clients try again.

    PIX / ASA 7.1 and earlier versions

    PIX (config) #isakmp nat-traversal 20

    PIX / ASA 7.2 (1) and later versions

    PIX (config) #crypto isakmp nat-traversal 20

  • RV120 VPN with full Cisco VPN Client?

    Is it possible to configure the RV120 for a VPN IPsec for use with the complete Cisco VPN client?

    I tried, but it does not appear to support "Goup of authentication.

    I see in the confi router I can put a PSK, but the complete VPN client seems only accecpt "Goup authentication."

    I managed on the basis for the work "Fast VPN", how it works is beyond me, because he does not appear to create an adapter with an IP address or anything on the local line, and I didn't even create a VPN policy...

    Or put another way, what alternative (Free) VPN clients are there to work with the RV120?

    Try the following link for instructions for Cisco VPN and the SA500:

    http://www.Cisco.com/en/us/docs/security/multi_function_security/multi_function_security_appliance/sa_500/TechNote/note/SA500_vpnclient_appnote.PDF

    I hope this helps.

    Thank you

    Rick Roe

    Cisco Small Business Support Center

  • Impossible to install the Cisco VPN Client on Windows 7

    Hello

    After an uninstall successful VPN Cisco version 4. I try to install the Cisco VPN Client 5.0.07.0290 version.

    But after the launch of vpnclient_setup.msi, the wizard starts. When I click on the next button, I get the following message: "installation ended prematurely because of an error".

    As an attachment, I add the details of the discovery of the error in the logs of windows (logError.txt) and the logs generated by the MSI installer in verbose (log2.txt) mode.

    My computer is a lenovo W500 with Windows 7 64-bit and 4 GB of memory (compatible with the requirements of the Cisco VPN Client).

    I have administrative privileges on this computer.

    Please help me!

    I need to use it to connect to my corporate network.

    Thanks in advance.

    BR

    Jerome

    If you want to try another software, I know that works I used it up until cisco came out with a 64-bit client there. Is the 64-bit version of shrew 2.1.0 it worked very well, you will just need your file FCP of cisco for import into if you have. This will tell you if the client or your system at least.

  • Cisco VPN Client is blocking incoming connections

    Hello

    I somethimes (not always) a problem with the Cisco VPN Client.

    As soon as the CISCO VPN Client is installed (it must not be running) it blocks inbound connections from the local network.

    The problem is that I use Ultra VNC SC to support some of my clients. Another client is supported by Cisco VPN. With UltraVNC SC customer clients try to connect to my PC.

    But if I installed the cisco VPN Client, no incoming connections are possible.

    How can I change this behavior?

    This behavior is not always the same. Last incoming connections of two months were possible, but from one day to another is not possible more.

    I recently installed the Client, but it takes no effect :-(

    I have NOT activated the firewall Cisco on the VPN Client and the behavior is NOT only if the Client is activated. This is the behavior even if it is NOT active and just installed.

    Hi Chris,

    Zone alarm is installed on the PC that is defective?

    Try to restart the Cisco VPN service and launch the vpn client.

    I remember having a similar problem with the Cisco VPN Client. Some conflict between the VPN client and Zone-Alarm, installed on the same PC.

    The problem was with VSDATANT variables in the registry key.

    Please see the following mail took from another forum:

    http://www.OutpostFirewall.com/Forum/showthread.php?t=9917

  • Cisco VPN Client 5.0.0 does not connect

    Hello

    I am trying to establish the VPN session the firewall to 5525 X Cisco ASA crossing 9.1.1 Cisco VPN Client. Although AnyConnect is the way to go, the inherited method must always be supported for some time as part of a migration. I tried two VPN users (authenticated by ad) on two client computers running Windows 7 64 bit and Cisco VPN Client 5.0.07.0440. Both users are able to establish a session to a computer at the ASA, but not the other. Entering credentails evil, the login popup will appear immediately. On the combination of username/password correct name, the following VPN client log messages are generated and the session drops that is "not connected" in the status bar. The PCF file is the same on both client computers.

    Cisco Systems VPN Client Version 5.0.07.0440

    Copyright (C) 1998-2010 Cisco Systems, Inc. All Rights Reserved.

    Client Type(s): Windows, WinNT

    Running on: 6.1.7601 Service Pack 1

    119    22:49:16.933  06/23/13  Sev=Info/6          IKE/0x6300003B

    Attempting to establish a connection with 203.99.111.44.

    120    22:49:16.939  06/23/13  Sev=Info/4          IKE/0x63000001

    Starting IKE Phase 1 Negotiation

    121    22:49:16.942  06/23/13  Sev=Info/4          IKE/0x63000013

    SENDING >>> ISAKMP OAK AG (SA, KE, NON, ID, VID(Xauth), VID(dpd), VID(Frag), VID(Nat-T), VID(Unity)) to 203.99.111.44

    122    22:49:16.973  06/23/13  Sev=Info/5          IKE/0x6300002F

    Received ISAKMP packet: peer = 203.99.111.44

    123    22:49:16.973  06/23/13  Sev=Info/4          IKE/0x63000014

    RECEIVING <<< ISAKMP OAK AG (SA, KE, NON, ID, HASH, VID(Unity), VID(Xauth), VID(dpd), VID(Nat-T), NAT-D, NAT-D, VID(Frag), VID(?)) from 203.99.111.44

    124    22:49:16.974  06/23/13  Sev=Info/5          IKE/0x63000001

    Peer is a Cisco-Unity compliant peer

    125    22:49:16.974  06/23/13  Sev=Info/5          IKE/0x63000001

    Peer supports XAUTH

    126    22:49:16.974  06/23/13  Sev=Info/5          IKE/0x63000001

    Peer supports DPD

    127    22:49:16.974  06/23/13  Sev=Info/5          IKE/0x63000001

    Peer supports NAT-T

    128    22:49:16.974  06/23/13  Sev=Info/5          IKE/0x63000001

    Peer supports IKE fragmentation payloads

    129    22:49:16.977  06/23/13  Sev=Info/6          IKE/0x63000001

    IOS Vendor ID Contruction successful

    130    22:49:16.977  06/23/13  Sev=Info/4          IKE/0x63000013

    SENDING >>> ISAKMP OAK AG *(HASH, NOTIFY:STATUS_INITIAL_CONTACT, NAT-D, NAT-D, VID(?), VID(Unity)) to 203.99.111.44

    131    22:49:16.977  06/23/13  Sev=Info/6          IKE/0x63000055

    Sent a keepalive on the IPSec SA

    132    22:49:16.977  06/23/13  Sev=Info/4          IKE/0x63000083

    IKE Port in use - Local Port =  0xCA7C, Remote Port = 0x1194

    133    22:49:16.977  06/23/13  Sev=Info/5          IKE/0x63000072

    Automatic NAT Detection Status:

    Remote end is NOT behind a NAT device

    This   end IS behind a NAT device

    134    22:49:17.000  06/23/13  Sev=Info/5          IKE/0x6300002F

    Received ISAKMP packet: peer = 203.99.111.44

    135    22:49:17.000  06/23/13  Sev=Info/4          IKE/0x63000014

    RECEIVING <<< ISAKMP OAK TRANS *(HASH, ATTR) from 203.99.111.44

    136    22:49:17.211  06/23/13  Sev=Info/4          IPSEC/0x63700008

    IPSec driver successfully started

    137    22:49:17.211  06/23/13  Sev=Info/4          IPSEC/0x63700014

    Deleted all keys

    138    22:49:23.207  06/23/13  Sev=Info/4          IKE/0x63000013

    SENDING >>> ISAKMP OAK TRANS *(HASH, ATTR) to 203.99.111.44

    139    22:49:23.393  06/23/13  Sev=Info/5          IKE/0x6300002F

    Received ISAKMP packet: peer = 203.99.111.44

    140    22:49:23.393  06/23/13  Sev=Info/4          IKE/0x63000014

    RECEIVING <<< ISAKMP OAK TRANS *(HASH, ATTR) from 203.99.111.44

    141    22:49:23.393  06/23/13  Sev=Info/4          IKE/0x63000013

    SENDING >>> ISAKMP OAK TRANS *(HASH, ATTR) to 203.99.111.44

    142    22:49:23.401  06/23/13  Sev=Info/5          IKE/0x6300005E

    Client sending a firewall request to concentrator

    143    22:49:23.401  06/23/13  Sev=Info/4          IKE/0x63000013

    SENDING >>> ISAKMP OAK TRANS *(HASH, ATTR) to 203.99.111.44

    144    22:49:23.427  06/23/13  Sev=Info/5          IKE/0x6300002F

    Received ISAKMP packet: peer = 203.99.111.44

    145    22:49:23.427  06/23/13  Sev=Info/4          IKE/0x63000014

    RECEIVING <<< ISAKMP OAK TRANS *(HASH, ATTR) from 203.99.111.44

    146    22:49:23.427  06/23/13  Sev=Info/5          IKE/0x63000010

    MODE_CFG_REPLY: Attribute = INTERNAL_IPV4_ADDRESS: , value = 10.2.193.69

    147    22:49:23.427  06/23/13  Sev=Info/5          IKE/0x63000010

    MODE_CFG_REPLY: Attribute = INTERNAL_IPV4_DNS(1): , value = 10.2.5.2

    148    22:49:23.428  06/23/13  Sev=Info/5          IKE/0x63000010

    MODE_CFG_REPLY: Attribute = INTERNAL_IPV4_DNS(2): , value = 10.1.5.2

    149    22:49:23.428  06/23/13  Sev=Info/5          IKE/0x6300000D

    MODE_CFG_REPLY: Attribute = MODECFG_UNITY_SAVEPWD: , value = 0x00000000

    150    22:49:23.428  06/23/13  Sev=Info/5          IKE/0x6300000D

    MODE_CFG_REPLY: Attribute = MODECFG_UNITY_SPLIT_INCLUDE (# of split_nets), value = 0x00000001

    151    22:49:23.428  06/23/13  Sev=Info/5          IKE/0x6300000F

    SPLIT_NET #1

    subnet = 10.0.0.0

    mask = 255.0.0.0

    protocol = 0

    src port = 0

    dest port=0

    152    22:49:23.428  06/23/13  Sev=Info/5          IKE/0x6300000E

    MODE_CFG_REPLY: Attribute = MODECFG_UNITY_DEFDOMAIN: , value = example.org

    153    22:49:23.428  06/23/13  Sev=Info/5          IKE/0x6300000D

    MODE_CFG_REPLY: Attribute = MODECFG_UNITY_PFS: , value = 0x00000000

    154    22:49:23.428  06/23/13  Sev=Info/5          IKE/0x6300000E

    MODE_CFG_REPLY: Attribute = APPLICATION_VERSION, value = Cisco Systems, Inc ASA5525 Version 9.1(1) built by builders on Wed 28-Nov-12 11:15 PST

    155    22:49:23.428  06/23/13  Sev=Info/5          IKE/0x6300000D

    MODE_CFG_REPLY: Attribute = MODECFG_UNITY_SMARTCARD_REMOVAL_DISCONNECT: , value = 0x00000001

    156    22:49:23.428  06/23/13  Sev=Info/5          IKE/0x6300000D

    MODE_CFG_REPLY: Attribute = Received and using NAT-T port number , value = 0x00001194

    157    22:49:23.445  06/23/13  Sev=Info/4          IKE/0x63000056

    Received a key request from Driver: Local IP = 10.2.193.69, GW IP = 203.99.111.44, Remote IP = 0.0.0.0

    158    22:49:23.445  06/23/13  Sev=Info/4          IKE/0x63000013

    SENDING >>> ISAKMP OAK QM *(HASH, SA, NON, ID, ID) to 203.99.111.44

    159    22:49:23.477  06/23/13  Sev=Info/5          IKE/0x6300002F

    Received ISAKMP packet: peer = 203.99.111.44

    160    22:49:23.477  06/23/13  Sev=Info/4          IKE/0x63000014

    RECEIVING <<< ISAKMP OAK INFO *(HASH, NOTIFY:STATUS_RESP_LIFETIME) from 203.99.111.44

    161    22:49:23.477  06/23/13  Sev=Info/5          IKE/0x63000045

    RESPONDER-LIFETIME notify has value of 86400 seconds

    162    22:49:23.477  06/23/13  Sev=Info/5          IKE/0x63000047

    This SA has already been alive for 7 seconds, setting expiry to 86393 seconds from now

    163    22:49:23.477  06/23/13  Sev=Info/5          IKE/0x6300002F

    Received ISAKMP packet: peer = 203.99.111.44

    164    22:49:23.477  06/23/13  Sev=Info/4          IKE/0x63000014

    RECEIVING <<< ISAKMP OAK INFO *(HASH, NOTIFY:NO_PROPOSAL_CHOSEN) from 203.99.111.44

    165    22:49:23.478  06/23/13  Sev=Info/4          IKE/0x63000013

    SENDING >>> ISAKMP OAK INFO *(HASH, DEL) to 203.99.111.44

    166    22:49:23.478  06/23/13  Sev=Info/4          IKE/0x63000049

    Discarding IPsec SA negotiation, MsgID=F3E3C530

    167    22:49:23.478  06/23/13  Sev=Info/4          IKE/0x63000017

    Marking IKE SA for deletion  (I_Cookie=CD65262E1C3808E4 R_Cookie=912AE160ADADEE65) reason = DEL_REASON_IKE_NEG_FAILED

    168    22:49:23.478  06/23/13  Sev=Info/5          IKE/0x6300002F

    Received ISAKMP packet: peer = 203.99.111.44

    169    22:49:23.479  06/23/13  Sev=Info/4          IKE/0x63000058

    Received an ISAKMP message for a non-active SA, I_Cookie=CD65262E1C3808E4 R_Cookie=912AE160ADADEE65

    170    22:49:23.479  06/23/13  Sev=Info/4          IKE/0x63000014

    RECEIVING <<< ISAKMP OAK INFO *(Dropped) from 203.99.111.44

    171    22:49:24.310  06/23/13  Sev=Info/4          IPSEC/0x63700014

    Deleted all keys

    172    22:49:26.838  06/23/13  Sev=Info/4          IKE/0x6300004B

    Discarding IKE SA negotiation (I_Cookie=CD65262E1C3808E4 R_Cookie=912AE160ADADEE65) reason = DEL_REASON_IKE_NEG_FAILED

    173    22:49:26.849  06/23/13  Sev=Info/4          IKE/0x63000001

    IKE received signal to terminate VPN connection

    174    22:49:26.855  06/23/13  Sev=Info/4          IPSEC/0x63700014

    Deleted all keys

    175    22:49:26.855  06/23/13  Sev=Info/4          IPSEC/0x63700014

    Deleted all keys

    176    22:49:26.855  06/23/13  Sev=Info/4          IPSEC/0x63700014

    Deleted all keys

    177    22:49:26.855  06/23/13  Sev=Info/4          IPSEC/0x6370000A

    IPSec driver successfully stopped

    Any ideas why the second client of Windows 7 does not work?

    Kind regards

    Rick.

    Rick

    Thanks for the additional output. It shows the xauth authentication step, which is good to see. But it does not offer much clarity on what is causing the problem.

    My attention is drawn to a couple of message on the balls that are in line with the two sessions for which you posted newspapers.

    32 00:36:08.178 24/06/13 Sev = Info/5 IKE/0x6300005E

    Customer address a request from firewall to hub

    I'm not sure that we see any answer to this, but it makes me wonder if it is somehow involved in the issue. Is it possible that there is a difference in the configuration of firewall and operating between two clients?

    I am also interested in this series of posts

    48 00:36:08.210 24/06/13 Sev = Info/4 IKE / 0 x 63000056

    Received a request from key driver: local IP = 10.2.193.69, GW IP = 203.99.111.44, Remote IP = 0.0.0.0

    I don't know why the pilot requested a key at this point, and I wonder why the remote IP is 0.0.0.0?

    It is followed by a package in which the ASA provides the value of the life of SA - which seems to be on the path to a successful connection. that is followed by

    55 00:36:08.350 24/06/13 Sev = Info/5 IKE/0x6300002F

    Received packet of ISAKMP: peer = 203.99.111.44

    56 00:36:08.350 24/06/13 Sev = Info/4 IKE / 0 x 63000014

    RECEIVING< isakmp="" oak="" info="" *(hash,="" notify:no_proposal_chosen)="" from="">

    during which the SAA indicates that no proposal has been selected. It seems therefore that the ASA is not happy about something.

    If we do not find indications of the client that allows to identify the problem, then maybe we look at the ASA. Are all log messages generated on the SAA during this attempt to establish VPN that could show us the problem? Would it not be possible to run debugs on the SAA in a trial of this machine?

    HTH

    Rick

  • Problem Cisco VPN Client with local authentication

    I configured PIX for the Cisco VPN client for remote access. It must be connected and also inside network is accessible. It is without any authentication username. It works well with a vpngroup name and the password for the vpngroup, configured on PIX and also on the Cisco VPN client. (version 4.6)

    When I configure crypto for local authentication, it did not work. configuration is as follows.

    #crypto card: name of the map of local authentication client

    I created a user with private = 15.

    Client VPN must be connected, and then it pops up a window user name and password. After giving these details. The user is not authenticated.

    Are there patterns more to do in / isakmp / ipsec / aaa configurations.

    Thank you

    AAA-server local LOCAL Protocol

    client authentication card crypto remote_vpn LOCAL

    client configuration address card crypto remote_vpn throw

    client configuration address card crypto remote_vpn answer

  • Cisco VPN Client 2801 router

    Hello

    I installed a router cisco 2801 to accept vpn connections, I use the cisco vpn client and the tunnel is created and is being created of the its.

    However, I cannot ping my vlan (only those who have a nat inside the ACL, those who have not said I can ping), so I have a NAT problem, just don't know where.

    Heres part of my setup on the ACL,

    IP local pool ippool 192.168.100.10 192.168.100.100

    by default-gateway IP X.X.X.X (ISP GATEWAY)

    IP forward-Protocol ND

    IP http server

    no ip http secure server

    IP http flash path:

    !

    !

    IP nat inside source list 1 interface FastEthernet0/1 overload

    IP nat inside source list 2 interface FastEthernet0/1 overload

    IP nat inside source list 3 interface FastEthernet0/1 overload

    IP nat inside source list 6 interface FastEthernet0/1 overload

    overload of IP nat inside source list 20 interface FastEthernet0/1

    IP nat inside source map route SHEEP interface FastEthernet0/1 overload

    IP route 0.0.0.0 0.0.0.0 X.X.X.X (external IP)

    Route IP 192.168.10.0 255.255.255.0 192.168.90.2

    IP route 192.168.20.0 255.255.255.0 192.168.90.2

    IP route 192.168.30.0 255.255.255.0 192.168.90.2

    IP route 192.168.40.0 255.255.255.0 192.168.90.2

    IP route 192.168.50.0 255.255.255.0 192.168.90.2

    IP route 192.168.60.0 255.255.255.0 192.168.90.2

    IP route 192.168.200.0 255.255.255.0 192.168.90.2

    !

    NAT extended IP access list

    deny ip 192.168.10.0 0.0.0.255 192.168.100.0 0.0.0.255

    deny ip 192.168.20.0 0.0.0.255 192.168.100.0 0.0.0.255

    deny ip 192.168.30.0 0.0.0.255 192.168.100.0 0.0.0.255

    deny ip 192.168.60.0 0.0.0.255 192.168.100.0 0.0.0.255

    deny ip 192.168.90.0 0.0.0.255 192.168.100.0 0.0.0.255

    permit ip 192.168.10.0 0.0.0.255 any

    ip licensing 192.168.20.0 0.0.0.255 any

    IP 192.168.30.0 allow 0.0.0.255 any

    IP 192.168.60.0 allow 0.0.0.255 any

    IP 192.168.90.0 allow 0.0.0.255 any

    !

    access-list 1 permit 192.168.90.0 0.0.0.255

    access-list 2 allow to 192.168.10.0 0.0.0.255

    access-list 3 allow 192.168.30.0 0.0.0.255

    access-list 6 permit 192.168.60.0 0.0.0.255

    access-list 20 allow 192.168.200.0 0.0.0.255

    !

    SHEEP allowed 10 route map

    corresponds to the IP NAT

    !

    The 192.168.90.2 address is my switch L3 (Cisco 3750)

    Any pointer is more than welcome,

    Concerning

    Miranda,

    Have you tried to remove the following lines:

    IP nat inside source list 1 interface FastEthernet0/1 overload

    IP nat inside source list 2 interface FastEthernet0/1 overload

    IP nat inside source list 3 interface FastEthernet0/1 overload

    IP nat inside source list 6 interface FastEthernet0/1 overload

    overload of IP nat inside source list 20 interface FastEthernet0/1

    And simply let this one:

    IP nat inside source map route SHEEP interface FastEthernet0/1 overload

    ?

    I have all the neceary allowed in the ACL of NAT, so you do not have individual lines for each network.

    Also, I noticed that your ACL 20 reads

    access-list 20 allow 192.168.200.0 0.0.0.255

    But your NAT ACL bed

    ip licensing 192.168.20.0 0.0.0.255 any

    I think you have a typo in there, you have a 200 on 20 and on the other.

    Check it out and let me know how it goes. Don't forget to clear the NAT table after deleting these lines:

    clear the ip nat trans *.

    I hope this helps!

    Raga

  • Cisco VPN client put in place

    Hi guru of cisco

    Help me please to configure VPN access on ASA 5505 for Cisco VPN Client. I want to let the customers gateway, but access remote 192.168.17.0/24 and 192.168.10.0/24 (connected through site-to-site) networks.

    Will be much appreciated for your help.

    My config:

    Output from the command: 'display conf '.

    !
    ASA Version 8.2 (2)
    !
    name of host host1
    domain domain name
    activate the encrypted password password
    encrypted passwd password
    names of
    !
    interface Vlan1
    Description INTERNET
    0000.0000.0001 Mac address
    nameif WAN
    security-level 0
    IP address a.a.a.a 255.255.255.248 watch a1.a1.a1.a1
    OSPF cost 10
    !
    interface Vlan2
    OLD-PRIVATE description
    0000.0000.0102 Mac address
    nameif OLD-private
    security-level 100
    IP 192.168.17.2 255.255.255.0 watch 192.168.17.3
    OSPF cost 10
    !
    interface Vlan6
    Description MANAGEMENT
    0000.0000.0106 Mac address
    nameif management
    security-level 100
    IP 192.168.1.2 255.255.255.0 ensures 192.168.1.3
    OSPF cost 10
    !
    interface Vlan100
    Failover LAN Interface Description
    !
    interface Ethernet0/0
    !
    interface Ethernet0/1
    Shutdown
    !
    interface Ethernet0/2
    Shutdown
    !
    interface Ethernet0/3
    Shutdown
    !
    interface Ethernet0/4
    Shutdown
    !
    interface Ethernet0/5
    switchport access vlan 100
    !
    interface Ethernet0/6
    switchport trunk allowed vlan 2.6
    switchport mode trunk
    !
    interface Ethernet0/7
    Shutdown
    !
    boot system Disk0: / asa822 - k8.bin
    passive FTP mode
    DNS domain-lookup WAN
    DNS server-group DefaultDNS
    Server name dns.dns.dns.dns
    domain domain name
    permit same-security-traffic intra-interface
    object-group Protocol TCPUDP
    object-protocol udp
    object-tcp protocol
    object-group service RDP - tcp
    RDP description
    EQ port 3389 object
    object-group Protocol DM_INLINE_PROTOCOL_1
    ip protocol object
    icmp protocol object
    object-protocol udp
    object-tcp protocol
    Access extensive list ip 192.168.17.0 LAN_nat0_outbound allow 255.255.255.0 192.168.10.0 255.255.255.0
    Standard access list LAN_IP allow 192.168.17.0 255.255.255.0
    WAN_access_in list of allowed ip extended access all any debug log
    WAN_access_in list extended access allowed icmp a.a.a.a 255.255.255.248 192.168.10.0 255.255.255.0 inactive debug log
    WAN_access_in list extended access permit tcp any object-group RDP any RDP log debugging object-group
    WAN_access_in list extended access allowed icmp a.a.a.a 255.255.255.248 a.a.a.a 255.255.255.248 debug log
    MANAGEMENT_access_in list of allowed ip extended access all any debug log
    access-list extended OLD-PRIVATE_access_in any allowed ip no matter what debug log
    access-list OLD-PRIVATE_access_in allowed extended object-group DM_INLINE_PROTOCOL_1 interface OLD-private 192.168.10.0 255.255.255.0 inactive debug log
    access-list OLD-PRIVATE_access_in allowed extended object-group TCPUDP interface OLD-private no matter what inactive debug log
    access-list OLD-PRIVATE_access_in allowed extended icmp host 192.168.10.254 interface private OLD newspaper inactive debugging
    access-list OLD-PRIVATE_access_in allowed extended icmp host 192.168.17.155 interface private OLD newspaper debugging
    access-list 101 extended allow host tcp 192.168.10.7 any eq 3389 debug log
    Access extensive list ip 192.168.17.0 WAN_1_cryptomap allow 255.255.255.0 192.168.10.0 255.255.255.0
    WAN_1_cryptomap to access ip 192.168.1.0 scope list allow 255.255.255.0 192.168.10.0 255.255.255.0
    WAN_cryptomap_2 to access ip 192.168.1.0 scope list allow 255.255.255.0 192.168.10.0 255.255.255.0
    Capin list extended access permit ip host 192.18.17.155 192.168.10.7
    Capin list extended access permit ip host 192.168.10.7 192.168.17.155
    LAN_access_in list of allowed ip extended access all any debug log
    Access extensive list ip 192.168.17.0 WAN_nat0_outbound allow 255.255.255.0 192.168.10.0 255.255.255.0
    WAN_nat0_outbound list of allowed ip extended access all 192.168.17.240 255.255.255.252
    WAN_nat0_outbound to access extended list ip 192.168.2.0 allow 255.255.255.0 192.168.2.0 255.255.255.248
    Access extensive list ip 192.168.17.0 WAN_2_cryptomap allow 255.255.255.0 192.168.10.0 255.255.255.0
    permit inside_nat0_outbound to access extended list ip 192.168.10.0 255.255.255.0 192.168.17.0 255.255.255.0
    LAN_IP_inbound list standard access allowed 192.168.10.0 255.255.255.0
    Standard access list IPSec_VPN_splitTunnelAcl allow a
    access extensive list ip 192.168.17.0 vpnusers_splitTunnelAcl allow 255.255.255.0 any
    sheep - in extended Access-list allow IP 192.168.17.0 255.255.255.0 192.168.2.0 255.255.255.0
    vpn_ipsec_splitTunnelAcl list standard access allowed 192.168.2.0 255.255.255.0
    pager lines 24
    Enable logging
    logging trap information
    asdm of logging of information
    Debugging trace record
    MTU 1500 WAN
    MTU 1500 OLD-private
    MTU 1500 management
    mask 192.168.1.150 - 192.168.1.199 255.255.255.0 IP local pool VPN_Admin_IP
    IP local pool vpnclient 192.168.2.1 - 192.168.2.5 mask 255.255.255.0
    failover
    primary failover lan unit
    failover lan interface failover Vlan100
    15 75 holdtime interface failover pollTime
    key changeover *.
    failover interface ip failover 192.168.100.1 255.255.255.0 ensures 192.168.100.2
    ICMP unreachable rate-limit 1 burst-size 1
    ICMP permitted host b.b.b.b WAN
    ICMP allow 192.168.10.0 255.255.255.0 WAN
    ICMP permitted host c.c.c.c WAN
    ICMP allow 192.168.17.0 255.255.255.0 WAN
    ICMP deny any WAN
    ICMP permitted host OLD-private b.b.b.b
    ICMP allow 192.168.10.0 255.255.255.0 OLD-private
    ICMP allow 192.168.17.0 255.255.255.0 OLD-private
    ICMP permitted host c.c.c.c OLD-private
    ICMP permitted host b.b.b.b management
    ICMP permitted host 192.168.10.0 management
    ICMP permitted host 192.168.17.138 management
    ICMP permit 192.168.1.0 255.255.255.0 management
    ICMP permitted host 192.168.1.26 management
    ASDM image disk0: / asdm - 631.bin
    don't allow no asdm history
    ARP timeout 14400
    Global (WAN) 1 interface
    Global (OLD-private) 1 interface
    Global interface (management) 1
    NAT (OLD-private) 0-list of access WAN_nat0_outbound
    NAT (OLD-private) 1 0.0.0.0 0.0.0.0
    WAN_access_in access to the WAN interface group
    Access-group interface private-OLD OLD-PRIVATE_access_in
    Access-group MANAGEMENT_access_in in the management interface
    Route WAN 0.0.0.0 0.0.0.0 a.a.a.185 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
    the ssh LOCAL console AAA authentication
    local AAA authentication attempts 10 max in case of failure
    Enable http server
    http 192.168.1.0 255.255.255.0 WAN
    http 0.0.0.0 0.0.0.0 WAN
    http a.a.a.a 255.255.255.255 WAN
    No snmp server location
    No snmp Server contact
    Server enable SNMP traps snmp authentication linkup, linkdown cold start
    Service resetoutside
    Crypto ipsec transform-set ESP-DES-SHA esp - esp-sha-hmac
    Crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-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
    Crypto ipsec transform-set esp-SHA-ESP-3DES-3des esp-sha-hmac
    life crypto ipsec security association seconds 28800
    Crypto ipsec kilobytes of life - safety 4608000 association
    card crypto WAN_map 1 corresponds to the address WAN_1_cryptomap
    card crypto WAN_map 1 set peer b.b.b.b
    WAN_map 1 transform-set ESP-DES-SHA crypto card game
    card crypto WAN_map WAN interface
    ISAKMP crypto enable WAN
    crypto ISAKMP policy 10
    preshared authentication
    3des encryption
    sha hash
    Group 2
    life 86400
    crypto ISAKMP policy 30
    preshared authentication
    the Encryption
    sha hash
    Group 1
    life 86400
    Telnet timeout 5
    SSH b.b.b.b 255.255.255.255 WAN
    SSH timeout 30
    SSH version 2
    Console timeout 0
    dhcpd auto_config OLD-private
    !

    a basic threat threat detection
    host of statistical threat detection
    Statistics-list of access threat detection
    a statistical threat detection tcp-interception rate-interval 30 burst-400-rate average rate 200
    NTP server 129.6.15.28 source WAN prefer
    WebVPN
    attributes of Group Policy DfltGrpPolicy
    Protocol-tunnel-VPN IPSec svc webvpn
    internal admin group strategy
    group admin policy attributes
    DNS.DNS.DNS.DNS value of DNS server
    Protocol-tunnel-VPN IPSec
    internal vpn_ipsec group policy
    attributes of the strategy of group vpn_ipsec
    value 192.168.17.80 DNS server dns.dns.dns.dns
    Split-tunnel-policy tunnelspecified
    value of Split-tunnel-network-list vpn_ipsec_splitTunnelAcl
    the address value vpnclient pools
    username admin password encrypted password privilege 15
    n1ck encrypted password privilege 15 password username
    type tunnel-group admin remote access
    tunnel-group admin general attributes
    address pool IPSec_VPN_pool
    vpnclient address pool
    LOCAL authority-server-group
    strategy-group-by default admin
    tunnel-group admin ipsec-attributes
    pre-shared-key *.
    tunnel-group b.b.b.b type ipsec-l2l
    tunnel-group b.b.b.b General-attributes
    strategy-group-by default admin
    b.b.b.b tunnel ipsec-attributes group
    pre-shared-key *.
    NOCHECK Peer-id-validate
    type tunnel-group vpn_ipsec remote access
    tunnel-group vpn_ipsec General-attributes
    vpnclient address pool
    Group Policy - by default-vpn_ipsec
    vpn_ipsec group of tunnel ipsec-attributes
    pre-shared-key *.
    !
    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
    inspect the icmp

    Thanks a lot for the confirmation. There is some lack of configurations and also some configuration errors.

    They are here:

    (1) Split tunnel-access list is incorrect:

    vpn_ipsec_splitTunnelAcl list standard access allowed 192.168.2.0 255.255.255.0

    It should be allowed in your internal network. Please, add and remove the following:

    standard access list vpn_ipsec_splitTunnelAcl allow 192.168.17.0 255.255.255.0

    No vpn_ipsec_splitTunnelAcl of the standard access list only allowed 192.168.2.0 255.255.255.0

    (2) NAT 0-list of access should also include the traffic between the local subnet to the Pool of IP VPN:

    Access extensive list ip 192.168.17.0 WAN_nat0_outbound allow 255.255.255.0 192.168.2.0 255.255.255.0

    (3) dynamic-map has not been created and assigned to crypto card:

    Crypto-map dynamic dynmap 10 game of transformation-ESP-3DES-SHA

    card crypto ipsec WAN_map 65000-isakmp dynamic dynmap

    (4) Finally, you have not enabled protocol IPSec in your group strategy:

    attributes of the strategy of group vpn_ipsec

    Protocol-tunnel-VPN IPSec

    Hope that helps.

    If it still does not after the changes described above, please kindly share the latest config and also the output of the following debugs when you try to connect:

    debugging cry isa

    debugging ipsec cry

  • Cisco VPN Client causes a blue screen crash on Windows XP Pro (Satellite M30)

    Hello

    I have a Satellite Pro M30 running Windows XP Professional.

    After you start a vpn Tunnel via a customer of Cisco VPN (Version 4.6 and 4.7), the system crashes with a blue screen.

    I see that the key exchange is successful, but immediately after the vpn connection is established Windows XP crashes with a blue screen.

    Someone has any idea how to solve this problem?

    Perhaps by the updated device driver? And if so, which driver should be updated?

    Kind regards

    Thorsten

    Hello

    Well, it seems that the Cisco client is a problem.
    I m unaware of this product because it of not designed by Toshiba.
    I think that the drivers are not compatible with the Windows operating system.
    However, I found this site troubleshooting cisco vpn client:
    Please check this:
    http://www.CITES.uiuc.edu/wireless/trouble-index.html

  • Professional Windows Vista crashes when you use Cisco VPN Client 5.05.0290

    I have a Dell Latitude E6400 Windows Vista Business (32 bit) operating system. When I go to turn on the VPN client, I get invited to my username / password and once entered, the system just hangs. The only way to answer, it's a re-start. I took action:

    1 disabled UAC in Windows
    2 tried an earlier version of the VPN client
    3. by the representative of Cisco, I put the application runs as an administrator

    If there are any suggestions or similar stories, I would be grateful any offereings.

    It IS the COMODO Firewall with the 5.0.x CISCO VPN client that causes the gel. The last update of COMODO has caused some incompatibility. I tried to install COMODO without the built in Zonealerm, but it is still frozen. The only way to solve it is to uninstall COMODOD. Since then, my CISCO VPN client works again...

  • Cisco vpn client minimized in the taskbar and the rest in status: disconnect

    I used 5.0.07.0240 cisco vpn client for 1 month with my pc under windows 7-64 bit. Worked well for 1 month. All of a sudden now when I double click the icon to start, VPN automatically minimizes to the taskbar with the disconnected state. It does not connect the option to hit or anything before it reduced to a minimum. I've not seen this before and no changes... but now it simply doesn't work. All solutions? Windows just patch automatically breaking cisco?
    Unfortunately, cisco does not world class technical service... they called but no use.

    In my view, there is now a published version of the x 64 client, you need to download.
    If you suspect an update of Windows, why not try a system restore for a day, it was
    working correctly?
     
    On Wednesday, April 28, 2010 17:27:46 + 0000, akshay2112 wrote:
     
    > I used 5.0.07.0240 cisco vpn client for 1 month with my pc under windows 7-64 bit. Worked well for 1 month. All of a sudden now when I double click the icon to start, VPN automatically minimizes to the taskbar with the disconnected state. It does not connect the option to hit or anything before it reduced to a minimum. I've not seen this before and no changes... but now it simply doesn't work. All solutions? Windows just patch automatically breaking cisco? Unfortunately, cisco does not world class technical service... they called but no use.
     

    Barb Bowman www.digitalmediaphile.com

Maybe you are looking for