Results 1 to 5 of 5

Thread: Cisco VPN Client - Connection Error Reason 412

  1. #1
    mahesh.nimbalkar@gmail.com Guest

    Cisco VPN Client - Connection Error Reason 412

    ***Cisco VPN Client - Connection Error Reason 412***

    I am trying to connect office through my laptop from home. But I am
    getting following error. The log is also inclued here.

    After searching a lot on internet and trying solutions I am posting
    question here.

    1) I can connect from home if I use different laptop with XP
    installed.
    2) Not able to connect from laptop which has Vista Home Premium.
    3) I tried IPSec over TCP.
    4) I tried UseLegacyIKEPort=1 and ForceKeepAlive=1.
    5) I tried other versions of VPN Client such as 4.8
    6) I can ping VPN server

    ---------------------------ERROR---------------------
    Secure VPN Connection terminated locally by the Client.
    Reason 412: The remote peer is no longer responding.

    ---------------------------LOG---------------------
    Cisco Systems VPN Client Version 5.0.01.0600
    Copyright (C) 1998-2007 Cisco Systems, Inc. All Rights Reserved.
    Client Type(s): Windows, WinNT
    Running on: 6.0.6001 Service Pack 1
    Config file directory: C:\Program Files\Cisco Systems\VPN Client\

    1 23:33:34.861 09/20/08 Sev=Warning/2 CVPND/0xA3400011
    Error -21 sending packet. Dst Addr: 0xC0A800FF, Src Addr: 0xC0A80002
    (DRVIFACE:1201).

    2 23:33:35.406 09/20/08 Sev=Warning/2 CVPND/0xA3400011
    Error -21 sending packet. Dst Addr: 0x42A24DE8, Src Addr: 0x00000000
    (DRVIFACE:2424).

    3 23:33:35.407 09/20/08 Sev=Warning/2 CVPND/0xA3400011
    Error -21 sending packet. Dst Addr: 0x42A24DE8, Src Addr: 0x00000000
    (DRVIFACE:2424).

    4 23:33:46.574 09/20/08 Sev=Warning/2 CVPND/0xA3400011
    Error -21 sending packet. Dst Addr: 0xC0A800FF, Src Addr: 0xC0A80002
    (DRVIFACE:1201).

    5 23:33:46.581 09/20/08 Sev=Warning/2 CVPND/0xA3400011
    Error -21 sending packet. Dst Addr: 0x42A24DE8, Src Addr: 0x00000000
    (DRVIFACE:2424).

    6 23:33:47.044 09/20/08 Sev=Warning/3 IKE/0xE3000069
    Failed to send 870 bytes to xx.xx.xx.xx, error = 0xFFFFFFEB

    7 23:33:52.154 09/20/08 Sev=Warning/3 IKE/0xE3000069
    Failed to send 870 bytes to xx.xx.xx.xx, error = 0xFFFFFFEB

    8 23:33:57.223 09/20/08 Sev=Warning/3 IKE/0xE3000069
    Failed to send 870 bytes to xx.xx.xx.xx, error = 0xFFFFFFEB

    9 23:34:02.293 09/20/08 Sev=Warning/3 IKE/0xE3000069
    Failed to send 870 bytes to xx.xx.xx.xx, error = 0xFFFFFFEB

  2. #2
    Joe Morris Guest
    Is that version of the client supported on Vista? I'm currently using
    5.0.03.0530 under Vista without problems.

    I am not sure, but I guess that version supposed to work on Vista.

    I use version 5.0.03.0530 and still have exactly the same problems: trying to
    connect i get the 412 error.

    The 5.x client is supported on Vista, I use 5.0.01.0600 on Vista Ultimate
    32-bit. There is no Cisco VPN client for any of the 64-bit Vistas.

    According to Cisco, error 412 is a problem in the VPN device (the other end
    of the connection). The IP address could have changed, or other issues.
    There is a possible workaround:

    http://www.cisco.com/univercd/cc/td/...0/50client.htm

    I'm running Windows Vista (SP1) and Cisco VPN Client (Version 5.0.01.0600) and things have been working great until I installed some Windows Updates the other day. Then my Cisco VPN Client started giving me the following error:
    "Secure VPN Connection terminated locally by the Client. Reason 412:"

    In order to fix this I've added an "exception" in "Windows Firewall" of 'C:\Program Files\Cisco Systems\VPN Client\vpngui.exe'. I also created an INBOUND Rule (UDP protocol, port 500) in "Windows Firewall with Advanced Security".

  3. #3
    Devinship Guest

    Re: Cisco VPN Client - Connection Error Reason 412

    I am trying to load Cisco VPN client on Vista Home Edition and receive
    the error message:
    "...\vpnclient-win-msi-5.0.01.0600-k9[1].exe is not a valid Win32
    application."
    Does anyone know why?

  4. #4
    Join Date
    Jan 2010
    Posts
    1

    Re: Cisco VPN Client - Connection Error Reason 412

    This tip did the trick for me, I am using windows 7, I went back and undid all the other things I tried and this one change (adding UseLegacyIKEPort) to the PCF file got it working.
    ----------------------

    Windows Vista Error 412
    When running under Windows Vista, you might encounter error 412: The remote peer is no longer responding.

    To work around this error, upgrade the local NAT device firmware. If this is not possible, switch to TCP. If switching to TCP is not possible, use the following keyword in the connection profile (*.pcf):

    UseLegacyIKEPort=1

  5. #5
    Join Date
    Jul 2010
    Posts
    1

    Re: Cisco VPN Client - Connection Error Reason 412

    I just solved this 412 error. Turn your firewalls and virus scanners off for troubleshooting first! We're using a Microsoft CA server and certificate authentication for the client. It turns out that the latest Cisco client 5.0.x may have some kind of flaw when requesting the client side certificate. Our standard is to utilize a password in the OU field and to use the rest of the fields = example: CN or O for company name, organizational name etc. Well, it turns out if you use lots of punctuation, spaces and special characters in that request, when the cert is processed and given back to the end user, the cert will malfunction. Also, since our CA is not publicly accessable, we need to give the root cert to the end user and have the user right click and add the root ca to their local microsoft store (default location that it picks) then have the CISCO client IMPORT the root ca (using the import button on the Cisco client of course) on the root CA.

    Solution: keep your cert requests minimal and simple when you do request them from the client. Try minimizing the amount of jibberish in the fields. I made several successful by just entering a simple vendor name (no spaces) in the CN field and our pw in the OU field. I submitted it to the cert server, generated the cert, gave it back to the end user along with a copy of the root CA cert, right clicked on the CA cert and imported it into the microsoft cert store that it chose automatically, then went to the cisco client, imported the issued certificate, then imported the rootca into cisco as well... viola - no more 412 errors!

    I also got this to work also using a UBUNTU linux system and oracle virtual box running XP pro under a bridged wireless adapter without any hassle!
    Last edited by mattula; 29-07-2010 at 04:20 PM. Reason: correction

Similar Threads

  1. Replies: 6
    Last Post: 03-09-2010, 06:48 PM
  2. Cisco VPN client fails on Vista with Reason 442
    By Hassan in forum Vista Help
    Replies: 4
    Last Post: 12-11-2009, 07:09 PM
  3. cisco vpn client doesnt work on wireless connection
    By aileen in forum Windows Vista Network
    Replies: 3
    Last Post: 02-05-2008, 12:23 AM
  4. Cisco VPN Reason 442
    By nehal_serpa in forum Windows Vista Network
    Replies: 3
    Last Post: 24-03-2007, 01:50 AM
  5. Getting Client Connection 80072ef Error on WSUS
    By Ascetica in forum Server Update Service
    Replies: 4
    Last Post: 29-04-2006, 09:29 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,710,838,387.37910 seconds with 16 queries