[vpn-help] what does INVALID-ID-INFORMATION in log mean?

[Brian Preston]

I'm setting up your VPN Client for the first time, with settings sent to me
by co-worker.  I get a 'negotiation timout occurred' in the connection log.
I searched here for info on that and enabled the trace log and found the
'received peer INVALID-ID-INFORMATION notification' message, which I figured
was the root cause.  What does that mean?

 

VPN Client Version = 2.1.5

Windows OS Version  = Windows 7

Gateway Make/Model - dunno

 

Here's the debug log from the Trace application:

 

10/07/28 15:31:14 ii : - isakmp spi = a8645b3357bf9f6a:4fee761a48e3f501

10/07/28 15:31:14 ii : - data size 0

10/07/28 15:31:19 -> : resend 1 phase1 packet(s) 192.168.1.6:500 ->
*.*.*.*:500

10/07/28 15:31:19 <- : recv IKE packet *.*.*.*:500 -> 192.168.1.6:500 ( 56
bytes )

10/07/28 15:31:19 DB : phase1 found

10/07/28 15:31:19 ii : processing informational packet ( 56 bytes )

10/07/28 15:31:19 =< : cookies a8645b3357bf9f6a:631df3b9591bab08

10/07/28 15:31:19 =< : message 00000000

10/07/28 15:31:19 << : notification payload

10/07/28 15:31:19 ii : received peer INVALID-ID-INFORMATION notification

10/07/28 15:31:19 ii : - *.*.*.*:500 -> 192.168.1.6:500

10/07/28 15:31:19 ii : - isakmp spi = a8645b3357bf9f6a:631df3b9591bab08

10/07/28 15:31:19 ii : - data size 0

10/07/28 15:31:24 -> : resend 1 phase1 packet(s) 192.168.1.6:500 ->
*.*.*.*:500

10/07/28 15:31:24 <- : recv IKE packet *.*.*.*:500 -> 192.168.1.6:500 ( 56
bytes )

10/07/28 15:31:24 DB : phase1 found

10/07/28 15:31:24 ii : processing informational packet ( 56 bytes )

10/07/28 15:31:24 =< : cookies a8645b3357bf9f6a:3f847177522c3c35

10/07/28 15:31:24 =< : message 00000000

10/07/28 15:31:24 << : notification payload

10/07/28 15:31:24 ii : received peer INVALID-ID-INFORMATION notification

10/07/28 15:31:24 ii : - *.*.*.*:500 -> 192.168.1.6:500

10/07/28 15:31:24 ii : - isakmp spi = a8645b3357bf9f6a:3f847177522c3c35

10/07/28 15:31:24 ii : - data size 0

10/07/28 15:31:29 -> : resend 1 phase1 packet(s) 192.168.1.6:500 ->
*.*.*.*:500

10/07/28 15:31:29 <- : recv IKE packet *.*.*.*:500 -> 192.168.1.6:500 ( 56
bytes )

10/07/28 15:31:29 DB : phase1 found

10/07/28 15:31:29 ii : processing informational packet ( 56 bytes )

10/07/28 15:31:29 =< : cookies a8645b3357bf9f6a:845c45f00afc66e7

10/07/28 15:31:29 =< : message 00000000

10/07/28 15:31:29 << : notification payload

10/07/28 15:31:29 ii : received peer INVALID-ID-INFORMATION notification

10/07/28 15:31:29 ii : - *.*.*.*:500 -> 192.168.1.6:500

10/07/28 15:31:29 ii : - isakmp spi = a8645b3357bf9f6a:845c45f00afc66e7

10/07/28 15:31:29 ii : - data size 0

10/07/28 15:31:34 ii : resend limit exceeded for phase1 exchange

10/07/28 15:31:34 ii : phase1 removal before expire time

10/07/28 15:31:34 DB : phase1 deleted ( obj count = 0 )

10/07/28 15:31:34 DB : policy not found

10/07/28 15:31:34 DB : policy not found

10/07/28 15:31:34 DB : tunnel stats event canceled ( ref count = 1 )

10/07/28 15:31:34 DB : removing tunnel config references

10/07/28 15:31:34 DB : removing tunnel phase2 references

10/07/28 15:31:34 DB : removing tunnel phase1 references

10/07/28 15:31:34 DB : tunnel deleted ( obj count = 0 )

10/07/28 15:31:34 DB : removing all peer tunnel refrences

10/07/28 15:31:34 DB : peer deleted ( obj count = 0 )

10/07/28 15:31:34 ii : ipc client process thread exit ...

10/07/28 15:31:47 ii : halt signal received, shutting down

10/07/28 15:31:47 ii : ipc server process thread exit ...

10/07/28 15:31:47 ii : pfkey process thread exit ...

10/07/28 15:31:48 ii : network process thread exit ...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.shrew.net/pipermail/vpn-help/attachments/20100728/022b7729/attachment.html>