Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 525
  • Last Modified:

Cisco VPN Client is occasionally unable to connect to Cisco VPN Concentrator

We use a Cisco 3015 Concentrator (software version 4.7.2) and the Cisco VPN Software client (version 4.6) running on Notebook computers with Windows XP SP2.  Occasionally users are unable to connect to the VPN concentrator getting the error “Reason 412: The remote peer is no longer responding.”

The very same machine may be able to connect from different location (employee moves to a different hotel) without any problems at all – with all things being the same on the notebook computer and concentrator.  When the failure is occurring – the concentrator event log does not appear to register a login attempt and on the client log indicates several ISAKMP OAK AG (Retransmissions) and the “Discarding IKE SA negotiation” followed by DEL_REASON_PEER_NOT_RESPONDING.
0
wpburgess
Asked:
wpburgess
  • 2
1 Solution
 
Scotty_ciscoCommented:
ok you hit the nail on the head.
>The very same machine may be able to connect from different location (employee moves to a different hotel) without any problems at all

that is because they are not passing through IKE SA and the other location is... the problem is there is really no solution to this other than finding hotels that setup the nat and distributions to users correctly.

We have this problem as well with a checkpoint VPN solution for that reason we also have a corprate dialup account as well.

its called NAT traversal in the cisco world..... and in the checkpoint world it is NAT-T.

Thanks
Scott

0
 
SorensonCommented:
What devices are between the outside port of the 3015 concentrator and the internet?  It would appear to be either a flaky internet connection, or a firewall between the vpn concentrator and the internet that is timing out the connection before the session is actually complete.  Double check the interface information on the vpn concentrator to be sure that there are no ethernet errors (like speed / duplex mismatches indicated by CRC and Runts) as well.

0
 
SorensonCommented:
sorry. didnt read all the way through the question.  I thought it was with clients that could connect and then suddenly could not.  I think Scotty_cisco's answer hits it on the head.

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.

Join & Write a Comment

Featured Post

What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now