Cisco VPN – Reason 412: The remote peer is no longer responding January 15, 2014 By Gareth Gudger 10 Comments I ran into this issue recently while trying to make a Remote Access VPN work on a Cisco ASA 5505 firewall. The VPN had been working at one point but was rarely used. CyberGhost and Private Internet Access can be found on most “top 10 Cisco Vpn Client Error 412 Windows 7 VPNs” lists. If you’re wondering which VPN is the better one, you’re in luck as we’re going to find out by comparing these two services across various categories. C: Program Files Cisco Systems VPN Client vpnclient stat traffic C: Program Files Cisco Systems VPN Client vpnclient stat tunnel Re: Reason 412: The remote peer is no longer responding. Cisco Vpn 412 Error Fix. 700+ VPN servers in 60+ countries. Anonymous access and zero traffic logs. Unlimited bandwidth. Connect up to 5 devices at once.

Cisco VPN users will sometimes drop their VPN connection and receive error 412, 'The remote peer is no longer responding.' This can be caused by a number of things, but assuming that the VPN tunnel is currently up and running properly, the issue usually lies with latency causing packet loss on the end-user's internet connection.

4 Steps total

Step 1: Delete the current VPN policy from the user's VPN client

Step 2: Using a text editor, open the .pcf policy file

Step 3: Add the line 'ForceKeepAlive=1' anywhere in the file along with the other parameters

Error Vpn Cisco 412

NOTE: If the 'ForceKeepAlive' line is already there but is set to '=0,' simply change it to '=1.'

Step 4: Save the .pcf file and re-import it to the VPN client

Cisco Vpn Client Error Reason 412

That should be it. This is helpful for users who tend to have DSL or generally low/inconsistent bandwidth coming in from their ISP's.

0 Comments