Cisco VPN Error 412

Cisco VPN error 412 occasionally occurs when using the Cisco VPN client.

The exact error message may differ between versions of the Cisco VPN client, but will be similar to this:

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

Causes for Cisco VPN Error 412

There are many error 412 causes, including:

Poor network connection. Packet delay or loss can force the VPN session to drop.
Hardware failure in a network interface card or network device.
A firewall or ACL (Access Control List) is blocking required protocols or ports:
- For PPTP, IP protocol 47 and TCP port 1723 are required
- For IPSec, IP protocol 51 and UDPport 500 are required

Troubleshooting Tips

If it is wirelessly connected, try to connect it with cable.
Turn the installed firewall off. Test the connection to see whether the problem still occurs. If it does not, turn the firewall back on and add exception rules for port 500, port 4500, and the ESP protocol in the firewall.
Turn on NAT-T/TCP in the profile (remember to unblock port 10000 in the firewall or turn the firewall off temporarily).
Edit the profile with an editor and change ForceKeepAlive=0 to ForceKeepAlive =1

Respond to “Cisco VPN Error 412”

Fred Ferland says:

February 17, 2011 at 3:51 pm Fred Ferland(Quote)

Hello,

we tried all of the above and we’re unable to determine the problem. The conenction drops after 2-3 mins. Any recommendation ? Thanks.

Reply
Jo Laws says:

February 28, 2011 at 4:47 pm Jo Laws(Quote)

Hey fred, have you tried turning off your windows firewall and prehaps instead of using a router firewall, plug the computer direct into the internet port via an inbuilt modem or something similar, or disable your antivirus while using the VPN software

Reply
Sebastian says:

March 2, 2011 at 4:29 pm Sebastian(Quote)

Add the UseLegacyIKEPort=1 option in the .pcf file.

Reply
Tim says:

March 3, 2011 at 12:22 pm Tim(Quote)

Hello, I’ve had a heap of trouble with this 412 thing, your advice helped (UseLegacyIKEPort=1) also i found you can add. ForceKeepAlive=1 to stop the dropping out too.

Thanks, Tim

Reply
John Harrington says:

July 11, 2011 at 5:56 pm John Harrington(Quote)

Hi! I saw a post on Fiberlink’s website that addressed this error specifically. The author of the post stated:

“You may need to work with your network administrator or help desk to make sure your account is ok (not locked) and you’re using the correct credentials.

If you’re using tokens, make sure the token key is synchronized.
In some cases, if you’re connected and then get disconnect with this error, uninstalling and re-installing the VPN client may help.
Sometimes a firewall or anti-virus policy mismatch needs to be checked.”

I hope these tips help some of you. To view the rest of the post click here: http://links.maas360.com/CiscoVPNerror413

Reply