Cisco VPN Client - Connection Error Reason 412

[m***@gmail.com]

Hi All,

***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

[Joe Morris]

Post by m***@gmail.com
***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.

[snip]

Post by m***@gmail.com
---------------------------LOG---------------------
Cisco Systems VPN Client Version 5.0.01.0600

[snip]

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

Joe Morris

[m***@gmail.com]

Post by Joe Morris
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.

Post by Joe Morris

Post by m***@gmail.com
***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.

[snip]

Post by m***@gmail.com
---------------------------LOG---------------------
Cisco Systems VPN Client Version 5.0.01.0600

[snip]
Is that version of the client supported on Vista?  I'm currently using
5.0.03.0530 under Vista without problems.
Joe Morris

[angryaboutvista]

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

Post by m***@gmail.com

Post by Joe Morris
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.

Post by Joe Morris

Post by m***@gmail.com
***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.

[snip]

Post by m***@gmail.com
---------------------------LOG---------------------
Cisco Systems VPN Client Version 5.0.01.0600

[snip]
Is that version of the client supported on Vista? I'm currently using
5.0.03.0530 under Vista without problems.
Joe Morris

[Ferd Burfel]

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/doc/product/vpn/client/5_0/50client.htm
http://www.lamnk.com/blog/vpn/cisco-vpn-client-reason-412-the-remote-peer-is-no-longer-responding/

Google is your friend.

Ferd

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

Post by m***@gmail.com

Post by Joe Morris
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.

Post by Joe Morris

Post by m***@gmail.com
***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.

[snip]

Post by m***@gmail.com
---------------------------LOG---------------------
Cisco Systems VPN Client Version 5.0.01.0600

[snip]
Is that version of the client supported on Vista? I'm currently using
5.0.03.0530 under Vista without problems.
Joe Morris

[Devinship]

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

--
Devinship

[DaveKan]

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

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

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

UseLegacyIKEPort=

--
DaveKa
-----------------------------------------------------------------------
DaveKan's Profile: http://forums.techarena.in/members/172193.ht
View this thread: http://forums.techarena.in/vista-help/1041711.ht

http://forums.techarena.i

[David H. Lipman]

From: "DaveKan" <***@DoNotSpam.com>

| 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 -- DaveKan


TechArena.in is a leech of Usenet and fakes that it provides forums when they are
actually Usenet news groups and uses the vBulletin USENET gateway. In this case it is a
news group within the Microsoft.* hierarchy and can be directly accessed via the Microsoft
news server; MSNews.Microsoft.Com using a news client via TCP port 119.

Users of TechArena.in are strongly ENCOURAGED to drop the TechArena.in leech of
Usenet and access "this" News Group directly with the following News URL...

news://msnews.microsoft.com/microsoft.public.windows.vista.general

[w***@gmail.com]

Post by David H. Lipman
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
UseLegacyIKEPort=1
--
DaveKan
------------------------------------------------------------------------
DaveKan's Profile: http://forums.techarena.in/members/172193.htm
View this thread: http://forums.techarena.in/vista-help/1041711.htm
http://forums.techarena.in

Thank you very much sir. This pointed me in the right direction

[mattula]

I just solved this 512 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!



-