Skip to content

Cisco VPN Client: Reason 412 – The remote peer is no longer responding

 

The error: "Secure VPN connection terminated locally by the Client. Reason 412: The remote peer is no longer responding" means the software VPN Client detected that the VPN server is not responding anymore and deleted the connection. This is caused by several different reasons, for example:

  • The user is behind a firewall that is blocking ports UDP 4500/500 and/or ESP.
  • The VPN client is using connecting on TCP and the default TCP port 10000 for NATT is blocked.
  • The internet connection is not stable and some packets are not reaching the VPN concentrator/server or the replies from the server/concentrator aren’t getting to the client, hence the client thinks the server is no longer available.
  • The VPN client is behind a NAT device and the VPN Server doesn’t have NAT-T enabled. In this case the user will not be able to send or receive traffic at all. It will be able to connect but that’s all. After some time the software client deletes the VPN tunnel.

Suggested solutions:

  • If you are using wireless, try to connect with cable
  • Turn your firewall off, then test the connection to see whether the problem still occurs. If it doesn’t then you can turn your firewall back on, add exception rules for port 500, port 4500 and the ESP protocol in your firewall
  • Turn on NAT-T/TCP in your profile ( remember to unblock port 10000 in your firewall)
  • Edit your profile with your editor and change ForceKeepAlive=0 to 1
  • Digg
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • StumbleUpon
  • Ma.gnolia
  • Reddit

Related posts:

  • Ojo
    Since my company IT support can't help to solve my issues for a while.
    I found this and your post very helpful for me.

    Thanks.
  • Wildan Usman
    Hi, your solution to turn off the windows firewall helps me.
    Thanks.

    Happy New Year 2009!!!!
  • Steve Mayer
    I get this error but it is after the VPN connection has been up and working for quite some time successfully. I find that it frequently happens after 23 hours and xx minutes (frequently 59 minutes). This makes me think that there is something on the server or client that has a timeout which fires after the connection has been up for 24 hours. However, it is not consistent. Some times I can stay up for days, sometimes for only 10-12 hours, but when I get the error I would say 70% of the time it occurs after 23 hours and 59 minutes. Any ideas on what I should check for?

    Thanks, Steve
  • Derrick G.
    Steve, as I understand it, the ISAKMP lifetime is by default 86,400 seconds (i.e. 24 hours) and when this is up, the connection fails. Here's a link with the details: http://www.cisco.com/en/US/products/ps6120/prod...

    Cheers.
  • Rafael
    I´ve the same error but I tried all the sugestions and my vpn doesn't work yet.
    Do you have more suggestions??

    Hugs!
  • Patrick J.
    I was having this same problem with a client of mines and I tried disabling the on board network controller. It worked immediately. I was able to be login to cisco vpn. I didn't get the error 412. The on board nic for this laptop was a broadcom nextreme 57xx Gigabit Controller. I checked the driver version in which was 3/26/2007. I wasn't able to try and update the driver because Dell website was slow or something.

    let me know if this helps!
  • Lamnk
    Thank you for sharing tip with us, Patrick. This is unfortunately only applicable for computers with more than one network adapter and laptops don't have this luxury. May I suggest updating the onboard controller's driver first ? ;-)
  • Lamnk
    @Steve: If that is the case, your admin probably has set the maximal lifetime for a VPN connection to 24 hours. The connection, however, can drop sooner due to other reasons. I know because we have this policy at my university :)
  • Mahamadali
    "Secure VPN connection terminated locally by the Client. Reason 412: The remote peer is no longer responding"

    I am getting this error using one ISP connection but if use other ISP connection then VPN works fine. How can it work for one ISP and not for other ?
  • akhlaqahmad
    check your internet. i think your internet is giving drops or losing communication packets.
    make sure your internet is not losing communication packets.
  • Accelya Spain
    Thank you very much for the post!!!
  • nice short and simple, i like it.
  • Nosleep
    I installed the VPN client on Vista 64bit and when I go to the client I receive "Secure VPN connection terminated locally by the Client Reason 440: Driver Failure" Can you help
  • Hi,

    Cisco Client doesn't run on Windows 64. Why ? Because Cisco refuses to offer/develope 64 bit version of VPN Client. You can use Shrew Soft VPN Client instead.
  • 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.
  • DaveKan
    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 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
blog comments powered by Disqus