Cisco VPN secure vpn connection terminated locally by the client eason 412: the remote peer is no longer responding

Hi guys,

I have looked around this topic:
"Cisco VPN secure vpn connection terminated locally by the client eason 412: the remote peer is no longer responding"

but so far I have not found a solution for my problem, this is my scenario:
I have several clients working with cisco vpn clients without problem, but I have one particular user that can't connect to my ASA, my VPN configuration was modified to have these service in port 80, as I said before, all users are working and only one is having problems, after check and troubleshoot, I have found that this user is not able to do a ping to my IP(all other can do ping), I check that he can go to any web site, so port 80 is open :) , but ping is not enabled.
My question: Cisco VPN client need to perform a ping to check if the peer is up when he is establishing the connection?

Thanks for your help guys
yasselAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
CybersreeConnect With a Mentor Commented:
Can you do a debug while trying the VPN connection from the particular user.? This is just to understand that the user is able to hit your ASA, if so what is happening..

debug crypto isakmp

Hope that this link would help you to troubleshoot.. :  http://www.cisco.com/en/US/tech/tk583/tk372/technologies_tech_note09186a00800949c5.shtml

If you donot see any hits then the issue in reachability.
0
 
ibrahim52Team LeaderCommented:
is it static IP or dynamic URL and If you can try un-installing network drivers through device manager and installing it back.
0
 
yasselAuthor Commented:
is an static IP, and I try in the same client with 4 machines :(, 2 new instalations of windows XP, 7, and a linux, all are the same OS that is working in my other clients, and as last resort, I went to the offices of my client, and I check with my laptop and I get the same result.
0
Managing Security & Risk at the Speed of Business

Gartner Research VP, Neil McDonald & AlgoSec CTO, Prof. Avishai Wool, discuss the business-driven approach to automated security policy management, its benefits and how to align security policy management with business processes to address today's security challenges.

 
LeeeeeConnect With a Mentor Commented:
If it's limited to one user in a specific location in which you tested and experienced the same issue, it may be an access restriction on the equipment at that site..as in an ACL on a firewall/router.
0
 
yasselAuthor Commented:
Hi Leeeee,

well, so far the only restriction that I have found was the ping, the client does not have any ACL limiting port 80 outbound, remember that my VPN service is hosted in port 80, exactly to avoid any miss configuration or any ISP restriction.

If you use port 80 to make the connection, that is the only port used between the cisco client and my ASA?

And of course the Cisco VPN client is configured to use IPsec over TCP

PD: the ping restriction was imposed by the ISP
0
 
yasselAuthor Commented:
I'm working in that point of view Cybersree, actually you are right, I have done a simple telnet test to port 80 and I don't get any connection attempt to my ASA, I have trying from another place and I get at least the IP coming to my ASA on port 80, so I need to check with the ISP of this user, WOW a simple connection on port 80 not working, something that not come to my mind at all.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.