cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2569
Views
0
Helpful
2
Replies

VPN Client Version 5.0.07.0440 IPSec Connection drops every 47mins...

daydreaming
Level 1
Level 1

I'm on win 7 Ultimate 64 bit and the vpn client version is: Cisco Systems VPN Client Version 5.0.07.0440. The connection is made through IPSec/UDP.

And here's the problem, firstly, I don't know why but every time when it connects I got these warning in the log:

1) 19:16:37.473 03/01/13 Sev=Warning/2 CVPND/0xE3400013 AddRoute failed to add a route with metric of 0: code 160 Destination 192.168.56.255 Netmask 255.255.255.255 Gateway 10.0.0.1 Interface 10.113.0.2

2) 19:16:37.473 03/01/13 Sev=Warning/2 CM/0xA3100024 Unable to add route. Network: c0a838ff, Netmask: ffffffff, Interface: a710002, Gateway: a000001.

But things seem to work all right until after about 47 minutes, the connection would drop by itself. The following is how it looks like:

http://i.stack.imgur.com/SrMwq.jpg

This is weird and I've no idea what's wrong, and also here're some error logs right before the connection drops:

1 19:46:18.398 02/28/13 Sev=Warning/3 IKE/0xE30000A9 Invalid Proxies for requested QM negotiation: LocalProxy : ID=0.0.0.0/0.0.0.0 Protocol=0 port=0, RemoteProxy : ID=0.0.0.0/0.0.0.0 Protocol=0 port=0 :(PLMgrID:367)

2 19:46:18.398 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to process ID payload (MsgHandler:681)

3 19:46:18.398 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to process QM Msg 1 (NavigatorQM:386)

4 19:46:18.398 02/28/13 Sev=Warning/2 IKE/0xE30000A7 Unexpected SW error occurred while processing Quick Mode negotiator:(Navigator:2263)

5 19:46:22.398 02/28/13 Sev=Warning/3 IKE/0xE30000A9 Invalid Proxies for requested QM negotiation: LocalProxy : ID=0.0.0.0/0.0.0.0 Protocol=0 port=0, RemoteProxy : ID=0.0.0.0/0.0.0.0 Protocol=0 port=0 :(PLMgrID:367)

6 19:46:22.398 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to process ID payload (MsgHandler:681)

7 19:46:22.398 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to process QM Msg 1 (NavigatorQM:386)

8 19:46:22.398 02/28/13 Sev=Warning/2 IKE/0xE30000A7 Unexpected SW error occurred while processing Quick Mode negotiator:(Navigator:2263)

9 19:46:29.599 02/28/13 Sev=Warning/3 IKE/0xE30000A9 Invalid Proxies for requested QM negotiation: LocalProxy : ID=0.0.0.0/0.0.0.0 Protocol=0 port=0, RemoteProxy : ID=0.0.0.0/0.0.0.0 Protocol=0 port=0 :(PLMgrID:367)

10 19:46:29.599 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to process ID payload (MsgHandler:681)

11 19:46:29.599 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to process QM Msg 1 (NavigatorQM:386)

12 19:46:29.599 02/28/13 Sev=Warning/2 IKE/0xE30000A7 Unexpected SW error occurred while processing Quick Mode negotiator:(Navigator:2263)

13 19:46:42.564 02/28/13 Sev=Warning/3 IKE/0xE30000A9 Invalid Proxies for requested QM negotiation: LocalProxy : ID=0.0.0.0/0.0.0.0 Protocol=0 port=0, RemoteProxy : ID=0.0.0.0/0.0.0.0 Protocol=0 port=0 :(PLMgrID:367)

14 19:46:42.564 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to process ID payload (MsgHandler:681)

15 19:46:42.564 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to process QM Msg 1 (NavigatorQM:386)

16 19:46:42.564 02/28/13 Sev=Warning/2 IKE/0xE30000A7 Unexpected SW error occurred while processing Quick Mode negotiator:(Navigator:2263)

17 19:47:05.891 02/28/13 Sev=Warning/3 IKE/0xE30000A9 Invalid Proxies for requested QM negotiation: LocalProxy : ID=0.0.0.0/0.0.0.0 Protocol=0 port=0, RemoteProxy : ID=0.0.0.0/0.0.0.0 Protocol=0 port=0 :(PLMgrID:367)

18 19:47:05.891 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to process ID payload (MsgHandler:681)

19 19:47:05.891 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to process QM Msg 1 (NavigatorQM:386)

20 19:47:05.891 02/28/13 Sev=Warning/2 IKE/0xE30000A7 Unexpected SW error occurred while processing Quick Mode negotiator:(Navigator:2263)

21 19:47:47.885 02/28/13 Sev=Warning/3 IKE/0xE30000A9 Invalid Proxies for requested QM negotiation: LocalProxy : ID=0.0.0.0/0.0.0.0 Protocol=0 port=0, RemoteProxy : ID=0.0.0.0/0.0.0.0 Protocol=0 port=0 :(PLMgrID:367)

22 19:47:47.886 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to process ID payload (MsgHandler:681)

23 19:47:47.886 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to process QM Msg 1 (NavigatorQM:386)

24 19:47:47.886 02/28/13 Sev=Warning/2 IKE/0xE30000A7 Unexpected SW error occurred while processing Quick Mode negotiator:(Navigator:2263)

25 19:50:47.567 02/28/13 Sev=Warning/3 IKE/0xE3000066 Could not find an IKE SA for 10.255.255.255. KEY_REQ aborted.

26 19:50:47.567 02/28/13 Sev=Warning/2 IKE/0xE300009B Failed to initiate P2 rekey: Error dectected (Initiate:176)

27 19:50:47.567 02/28/13 Sev=Warning/2 IKE/0xE300009B Unable to initiate QM (IKE_MAIN:463)

28 19:50:47.718 02/28/13 Sev=Warning/2 CVPND/0xA3400015 Error with call to IpHlpApi.DLL: CheckUpVASettings: Found IPADDR entry addr=10.113.0.2, error 0

29 19:50:48.729 02/28/13 Sev=Warning/2 CVPND/0xA3400015 Error with call to IpHlpApi.DLL: CleanUpVASettings: Was able to delete all VA settings after all, error 0

It's super annoying since you have to re-connect every 47 minutes. Would any experienced please tell me what should I do to fix it?

2 Replies 2

daydreaming
Level 1
Level 1

Anybody? Please...

Or maybe there's some certain steps to debug and narrow down the problem?

Right now I've no idea what to do...

Day Dreamer,

ISAKMP/IKE Policy Mismatch Issues

Sometimes you'll experience a problem where the  appropriate ISAKMP/IKE Phase 1 transform, called an IKE Proposal on  Cisco VPN 3000 concentrators, or the ISAKMP/ IKE Phase 2 transform  doesn't match that found on the client. The Cisco Easy VPN clients,  which include the Cisco VPN Client software, already have a list of  predefined proposals and policies incorporated into their software. The  Cisco Easy VPN Server must have a corresponding match for both the Phase  1 and Phase 2 transforms/policies. If a match is not found in Phase 1,  no session is established. If no match is found in Phase 2, the  ISAKMP/IKE Phase 1 management session will be built, but the data  connection will failin this instance, the client will tear down the  management connection also.

On the Cisco VPN Client, if there is not a matching transform/policy on the Easy VPN Server, you'll see in the message shown in Example 12-7 in the connection status pop-up window:

Example 12-7. Mismatched ISAKMP/IKE Phase 1 Policy with the Default Logging Level

Initializing the connection...
Contacting the security gateway at 192.1.1.1...
Secure VPN Connection terminated locally by the Client.
Reason 412: The remote peer is no longer responding.
Not connected.

http://fengnet.com/book/vpnconf/ch12lev1sec6.html

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: