Cisco Vpn Error Del_reason_peer_not_responding
Contents |
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help cisco vpn reason 412 the remote peer is not responding Create a Freelance Project Hire for a Full Time Job Ways to
Reason 412 The Remote Peer Is No Longer Responding Cisco Vpn
Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services cisco vpn error 433 reason not specified by peer Groups Website Testing Store Headlines Experts Exchange > Questions > Cisco VPN Connectivity Issues "DEL_REASON_PEER_NOT_RESPONDING" Want to Advertise Here? Solved Cisco VPN Connectivity Issues "DEL_REASON_PEER_NOT_RESPONDING" Posted on 2007-07-02 IPsec del_reason_peer_not_responding vpn client VPN 1 Verified Solution 3 Comments 20,779 Views Last Modified: 2012-06-21 I am having an issue getting some VPN clients to connect to the VPN concentrator and actually establish the connection. I am using the following: Cisco 3000 series VPN concentrator Cisco VPN Client Version 4.0 (REL) Authentication is done via PKI authentication (Entrust/Entelligence 6.1.100.624) The issue: When some
Unable To Establish Phase 1 Sa With Server Because Of "del_reason_peer_not_responding"
users attempt to connect they get the following error message: "Secure VPN Connection terminated locally by the Client. Reason: The remote peer is no longer responding." This does NOT affect all users, only a few. Thus far I have asked users to modify the MTU settings on the client system itself via the MTU tool included in the VPN client software. That has worked, however; I am still having users get the same error message even after changing the MTU. The MTU value I had them set was 1300 (seemingly the default in the client) but again, for some; no go. Firewalls have also been disabled and each machine is built from one Windows XP SP2 image, still the same issue after disabling desktop firewalls. The VPN concentrator log shows the user logging in and being authenticated successfully but then kills the connection citing an error with "Oakley Aggressive Mode" (I do not have complete logs due to this being a managed service. However, since the workstation modifications seemed to work, I do
to a Cisco ASA firewall running 7.2(5). It was a simple problem, caused by a simple oversight, but it took quite a while for the cause to become apparent. If a VPN client attempted to connect (using IPSEC/UDP), it would fail and a log of the session would show DEL_REASON_PEER_NOT_RESPONDING as the cause. The ASA never seemed to show any relevant debug information, in fact it seemed https://www.experts-exchange.com/questions/22672132/Cisco-VPN-Connectivity-Issues-DEL-REASON-PEER-NOT-RESPONDING.html to be oblivious to the fact that a client was trying to connect. Here is the full client log (in this case from an OSX machine), with the peer address changed to 1.1.1.1: Cisco Systems VPN Client Version 4.9.01.0230 Copyright (C) 1998-2009 Cisco Systems, Inc. All Rights Reserved. Client Type(s): Mac OS https://razamattaz.wordpress.com/2010/09/30/del_reason_peer_not_responding-with-cisco-vpn-client-and-asa/ X Running on: Darwin 10.4.0 Darwin Kernel Version 10.4.0: Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4-1/RELEASE 1386 i386 Config file directory: /etc/opt/cisco-vpnclient 1Â Â Â Â Â Â Â Â Â Â Â Â Â 17:40:35.421 08/11/2010 Sev=Info/4Â Â Â Â CM/Ox43100002 Begin connection process 2Â Â Â Â Â Â Â Â Â Â Â Â Â 17:40:35.422 08/11/2010 Sev=Info/4Â Â Â Â CM/Ox43100004 Establish secure connection using Ethernet 3Â Â Â Â Â Â Â Â Â Â Â Â Â 17:40:35.422 08/11/2010 Sev=Info/4Â Â Â Â CM/Ox43100024 Attempt connection with server "1.1.1.1" 4Â Â Â Â Â Â Â Â Â Â Â Â Â 17:40:35.422 08/11/2010 Sev=Info/4Â Â Â Â CVPND/Ox43400019 Privilege Separation: binding to port: (500). 5Â Â Â Â Â Â Â Â Â Â Â Â Â 17:40:35.422 08/11/2010 Sev=Info/4Â Â Â Â CVPND/Ox43400019 Privilege Separation: binding to port: (4500). 6Â Â Â Â Â Â Â Â Â Â Â Â Â 17:40:35.422 08/11/2010 Sev=Info/6Â Â Â Â IKE/Ox4300003B Attempting to establish a connection with 1.1.1.1. 7Â Â Â Â Â Â Â Â Â Â Â Â Â 17:40:35.510 08/11/2010 Sev=Info/4Â Â Â Â IKE/Ox43000013 SENDING >>> ISAKMP OAK AG (SA, KE, NON, ID, VID(Xauth), VID(dpd), VID(Frag), VID(Nat-T), VID(Unity)) to 1.1.1.1 8Â Â Â Â Â Â Â Â Â Â Â Â Â 17:40:35.552 08/11/2010 Sev=Info/4Â Â Â Â IPSEC/Ox43700008 IPSec driver successfully started 9Â Â Â Â Â Â Â Â Â Â Â Â Â 17:40:35.552 08/11/2010 Sev=Info/4Â Â Â Â IPSEC/Ox43700014 Deleted all keys 10Â Â Â Â Â Â Â Â Â Â Â Â 17:40:40.552 08/11/2010 Sev=Info/4Â Â Â Â IKE/0x43000021 Retransmitting last packet! 11Â Â Â Â Â Â Â Â Â Â Â Â 17:40:40.552 08/11/2010 Sev=Info/4Â Â Â Â IKE/0x43000021 SENDING >>> ISAKMP OAK AG (Retransmission) to 1.1.1.1 12Â Â Â Â Â Â Â Â Â Â Â Â 17:40:45.552 08/11/2010 Sev=Info/4Â Â Â Â IKE/0x43000021 Retransmitting last packet! 13Â Â Â Â Â
Invalid Server Name Used "vpnx.llnl.gov", which does not exist in the server list, to generate this http://cisco3000vpn-client-logs.blogspot.com/2012/03/cisco-vpn-client-log-collection-guide.html error User Authentication Prompt?: No Client Response: Secure VPN Connection terminated locally by the Client. Reason 403: Unable to contact the secure gateway. Log Excerpt: Unable to resolve server address "vpnx.llnl.gov" Error Type: Incorrect Server Name Used "vpn1.llnl.gov", which is a VPN 5000 server, to generate this error User Authentication Prompt?: No Client Response: Secure VPN cisco vpn Connection terminated locally by the Client. Reason 412: The remote peer is no longer responding. Log Excerpt: DEL_REASON_PEER_NOT_RESPONDING Error Type: IPSec pass-through protocol disabled Disabled IPSec pass-trhough protocol in the Linksys WRT54G router (Security tab > VPN) to generate this error User Authentication Prompt?: No Client Response: Secure VPN Connection terminated locally by the Client. Reason cisco vpn error 412: The remote peer is no longer responding. Log Excerpt: DEL_REASON_PEER_NOT_RESPONDING Error Type: Invalid Group Name Used "groupb", which does not exist in the group list, to generate this error User Authentication Prompt?: No Client Response: Secure VPN Connection terminated locally by the Client. Reason 412: The remote peer is no longer responding. Log Excerpt: DEL_REASON_PEER_NOT_RESPONDING Error Type: Incorrect Group Name Used "vpn-llnlc", which is the VPN-C group name, with a VPN account to generate this error User Authentication Prompt?: Yes Client Response: Secure VPN Connection terminated locally by the Client. Reason 413: User authentication failed. Log Excerpt: DEL_REASON_WE_FAILED_AUTH Error Type: Incorrect Group Password Used "notagood", which is not a valid password for the llnl-vpn group, to generate this error User Authentication Prompt?: No Client Response: Secure VPN Connection terminated locally by the Client. Reason 403: Unable to contact the secure gateway. Log Excerpt: Sev=Warning/3 IKE/0xC3000056 The received HASH payload cannot be verified Sev=Warning/2 IKE/0xC300007D Hash verification failed... may be configured with invalid group password. Sev=Warni