VPN Client Error : The remote peer is no longer responding

Unanswered Question
Dec 31st, 2012
User Badges:

Hello,


A particular VPN user is getting the below error while he try to connect using Cisco vpn client (version 5.0).

</code></pre><pre><code>Secure VPN connection terminated locally by the Client  
Reason 412: The remote peer is no longer responding.


I tried to connect VPN using the same profile and it was working fine. Other VPN users can also connect without any issue.


Below are the logs that I am getting from the VPN client:


82    02:02:14.445  12/31/12  Sev=Info/4    IKE/0x63000013
SENDING >>> ISAKMP OAK AG (Retransmission) to x.x.x.x

83    02:02:19.593  12/31/12  Sev=Info/4    IKE/0x63000021
Retransmitting last packet!

84    02:02:19.593  12/31/12  Sev=Info/4    IKE/0x63000013
SENDING >>> ISAKMP OAK AG (Retransmission) to x.x.x.x

85    02:02:24.710  12/31/12  Sev=Info/4    IKE/0x63000021
Retransmitting last packet!

86    02:02:24.710  12/31/12  Sev=Info/4    IKE/0x63000013
SENDING >>> ISAKMP OAK AG (Retransmission) to x.x.x.x

87    02:02:29.858  12/31/12  Sev=Info/4    IKE/0x63000017
Marking IKE SA for deletion  (I_Cookie=CC3B6AF2C2BD2FCA R_Cookie=0000000000000000) reason = DEL_REASON_PEER_NOT_RESPONDING

88    02:02:30.373  12/31/12  Sev=Info/4    IKE/0x6300004B
Discarding IKE SA negotiation (I_Cookie=CC3B6AF2C2BD2FCA R_Cookie=0000000000000000) reason = DEL_REASON_PEER_NOT_RESPONDING

89    02:02:30.373  12/31/12  Sev=Info/4    CM/0x63100014
Unable to establish Phase 1 SA with server "x.x.x.x" because of "DEL_REASON_PEER_NOT_RESPONDING"

90    02:02:30.373  12/31/12  Sev=Info/5    CM/0x63100025
Initializing CVPNDrv

91    02:02:30.373  12/31/12  Sev=Info/6    CM/0x63100046
Set tunnel established flag in registry to 0.

92    02:02:30.373  12/31/12  Sev=Info/4    IKE/0x63000001
IKE received signal to terminate VPN connection

93    02:02:31.387  12/31/12  Sev=Info/4    IPSEC/0x63700014
Deleted all keys

94    02:02:31.387  12/31/12  Sev=Info/4    IPSEC/0x63700014
Deleted all keys

95    02:02:31.387  12/31/12  Sev=Info/4    IPSEC/0x63700014
Deleted all keys

96    02:02:31.387  12/31/12  Sev=Info/4    IPSEC/0x6370000A
IPSec driver successfully stopped


I tried to disable  firewall, reinstall vpn client software and followed few links like http://www.lamnk.com/blog/vpn/cisco-vpn-client-reason-412-the-remote-peer-is-no-longer-responding/ but didn't find a poosible solution.


The Cisco VPN Client(x64) is installed on Server2008 Ent (x64). Please help me on this issue.


Regards,
Tony


http://yadhutony.blogspot.com       

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Mariusz Bochen Mon, 12/31/2012 - 07:27
User Badges:

Hi Yadhu,


I had exactly the same problem a while ago and it was related to user authentication.

Yadhu Tony wrote:



I tried to connect VPN using the same profile and it was working fine. Other VPN users can also connect without any issue.


Have you tried the same profile and the same user credentials?


How the authentication is configured on your firewall, is it tacacs calling AD or some different config?

If that's the case you can use ASDM to test credentials. Thanks to this method I have found and resolved my issue.


Let me know please how it goes.


Regards

Mariusz

Yadhu Tony Mon, 12/31/2012 - 19:50
User Badges:

Hello Mariusz,


Thank you for your reply. I tried the same profile using the same credentials and found that it is working perfectly from my site.

AAA is configured locally on the firewall.

Is there any other things do I need to check? Please help me out.



Regards,
Tony

http://yadhutony.blogspot.com

Mariusz Bochen Wed, 01/02/2013 - 08:12
User Badges:

Hi Tony,


Happy New Year


Try to narrow the problem even more.

Have you try to login as affected user from the same network, but a different host?

Another test would be the same host, but different user profile, and so on...

While doing this you can enable debug for crypto isakmp and setup some capture matching your source IP to check if you're hitting the firewall (and also how the firewall behaves).


Regards

Mariusz

Yadhu Tony Wed, 01/02/2013 - 23:33
User Badges:

Hello Mariusz,


Happy New Year !


The issue got resolved. The problem was with the antivirus package which is installed on remote host. Now the remote user can connect without any issue. Thank you for your support


Regards,
Tony

http://yadhutony.blogspot.com

Sam Pragash Mon, 03/25/2013 - 01:10
User Badges:

Hi Tony,


I am also facing the same problem. Did u uninstalled the Antivirus? which one it is?


Sam.

Aut0Kills Sat, 02/25/2017 - 05:13
User Badges:

Same here ! Thanks a lot for your help, fixed all my problems :)

hriday.dhali Thu, 12/01/2016 - 22:18
User Badges:

Cisco VPN is disconnect after every 1 hr ,wher destination IP address is responding very well.There no ping drop of the IP address.

But its disconnected time to time.



2 08:58:11.598 12/02/16 Sev=Warning/2 CM/0xA3100024
Unable to add route. Network: c0a838ff, Netmask: ffffffff, Interface: a14f1ec, Gateway: a14f101.

3 10:10:46.254 12/02/16 Sev=Warning/3 IKE/0xE3000066
Could not find an IKE SA for 10.20.33.2. KEY_REQ aborted.

4 10:10:46.254 12/02/16 Sev=Warning/2 IKE/0xE300009B
Failed to initiate P2 rekey: Error dectected (Initiate:176)

5 10:10:46.254 12/02/16 Sev=Warning/2 IKE/0xE300009B
Unable to initiate QM (IKE_MAIN:463)

6 10:10:47.209 12/02/16 Sev=Warning/2 CVPND/0xA3400015
Error with call to IpHlpApi.DLL: CheckUpVASettings: Found IPADDR entry addr=10.20.241.236, error 0

7 10:10:48.213 12/02/16 Sev=Warning/2 CVPND/0xA3400015
Error with call to IpHlpApi.DLL: CheckUpVASettings: Found IPADDR entry addr=10.20.241.236, error 0

8 10:10:49.227 12/02/16 Sev=Warning/2 CVPND/0xA3400015
Error with call to IpHlpApi.DLL: CleanUpVASettings: Was able to delete all VA settings after all, error 0

9 10:19:14.483 12/02/16 Sev=Warning/2 CVPND/0xE3400013
AddRoute failed to add a route with metric of 0: code 160

mohammed.mubash... Fri, 02/24/2017 - 20:45
User Badges:

If you are connecting from behind the Router.

Check for router firewall configuration "IPSec bypass" and enable it.

It worked for me that way.

Attachment: 

Actions

This Discussion

Related Content