[vpn-help] 2.2.2-release stopped working between reboots

Colin Buckley colin.e.buckley at gmail.com
Tue Feb 25 04:04:35 CST 2014


Recently had a similar problem which showed similar results.

Take a look in  Device Manager -> Network adapters -> Shrew Soft Virtual 
Adapter and see if Windows has tagged it as "unsigned" if so the driver 
was never loaded.

To prove it,  press F8 during boot-up and select the option which 
ignores unsigned drivers.


On 25/02/2014 06:21, Heuberger, Thomas wrote:
> I'm running 2.2.2-release on Win 8.1 x64 and it ceased working between reboots and I can't get it to work again.
>
> I tried updating my NIC drivers (Intel NIC) to the latest version, tried resetting the TCP/IP stack (netsh int ip reset), no go.
>
> I uninstalled and re-installed every version of the VPN client from 2.2.0 to 2.2.2.
>
> The error message I'm getting in the VPN Access Manager is
>
> config loaded for site xxx.vpn'
> attached to key daemon ...
> peer configured
> iskamp proposal configured
> esp proposal configured
> client configured
> local id configured
> remote id configured
> pre-shared key configured
> bringing up tunnel ...
> network unavailable
> tunnel disabled
> detached from key daemon
>
> ---
>
> The IKE Service log shows:
>
> 14/02/25 07:18:26 ## : IKE Daemon, ver 2.2.2
> 14/02/25 07:18:26 ## : Copyright 2013 Shrew Soft Inc.
> 14/02/25 07:18:26 ## : This product linked OpenSSL 1.0.1c 10 May 2012
> 14/02/25 07:18:26 ii : opened 'C:\Program Files\ShrewSoft\VPN Client\debug\iked.log'
> 14/02/25 07:18:26 ii : rebuilding vnet device list ...
> 14/02/25 07:18:26 ii : device ROOT\VNET\0000 disabled
> 14/02/25 07:18:26 ii : network process thread begin ...
> 14/02/25 07:18:26 ii : pfkey process thread begin ...
> 14/02/25 07:18:26 !! : vflt device attach failed
> 14/02/25 07:18:26 ii : ipc server process thread begin ...
> 14/02/25 07:18:27 !! : vflt device attach failed
> 14/02/25 07:18:28 !! : vflt device attach failed
> 14/02/25 07:18:29 !! : vflt device attach failed
> 14/02/25 07:18:30 !! : vflt device attach failed
> 14/02/25 07:18:31 !! : vflt device attach failed
> 14/02/25 07:18:32 !! : vflt device attach failed
> 14/02/25 07:18:33 !! : vflt device attach failed
> 14/02/25 07:18:34 ii : ipc client process thread begin ...
> 14/02/25 07:18:34 <A : peer config add message
> 14/02/25 07:18:34 <A : proposal config message
> 14/02/25 07:18:34 <A : proposal config message
> 14/02/25 07:18:34 <A : client config message
> 14/02/25 07:18:34 <A : xauth username message
> 14/02/25 07:18:34 <A : xauth password message
> 14/02/25 07:18:34 <A : local id 'admin at gba.geolba.ac.at' message
> 14/02/25 07:18:34 <A : preshared key message
> 14/02/25 07:18:34 <A : remote resource message
> 14/02/25 07:18:34 <A : peer tunnel enable message
> 14/02/25 07:18:34 DB : peer added ( obj count = 1 )
> 14/02/25 07:18:34 ii : local address 192.168.101.10 selected for peer
> 14/02/25 07:18:34 DB : tunnel added ( obj count = 1 )
> 14/02/25 07:18:34 DB : new phase1 ( ISAKMP initiator )
> 14/02/25 07:18:34 DB : exchange type is aggressive
> 14/02/25 07:18:34 DB : 192.168.101.10:500 <-> 192.168.101.1:500
> 14/02/25 07:18:34 DB : 695134047b5b5e68:0000000000000000
> 14/02/25 07:18:34 DB : phase1 added ( obj count = 1 )
> 14/02/25 07:18:34 >> : security association payload
> 14/02/25 07:18:34 >> : - proposal #1 payload
> 14/02/25 07:18:34 >> : -- transform #1 payload
> 14/02/25 07:18:34 >> : key exchange payload
> 14/02/25 07:18:34 >> : nonce payload
> 14/02/25 07:18:34 >> : identification payload
> 14/02/25 07:18:34 >> : vendor id payload
> 14/02/25 07:18:34 ii : local supports XAUTH
> 14/02/25 07:18:34 >> : vendor id payload
> 14/02/25 07:18:34 ii : local supports FRAGMENTATION
> 14/02/25 07:18:34 >> : vendor id payload
> 14/02/25 07:18:34 ii : local is SHREW SOFT compatible
> 14/02/25 07:18:34 >> : vendor id payload
> 14/02/25 07:18:34 ii : local is NETSCREEN compatible
> 14/02/25 07:18:34 >> : vendor id payload
> 14/02/25 07:18:34 ii : local is SIDEWINDER compatible
> 14/02/25 07:18:34 >> : vendor id payload
> 14/02/25 07:18:34 ii : local is CISCO UNITY compatible
> 14/02/25 07:18:34 >= : cookies 695134047b5b5e68:0000000000000000
> 14/02/25 07:18:34 >= : message 00000000
> 14/02/25 07:18:34 -> : send IKE packet 192.168.101.10:500 -> 192.168.101.1:500 ( 418 bytes )
> 14/02/25 07:18:34 ii : phase1 removal before expire time
> 14/02/25 07:18:34 DB : phase1 deleted ( obj count = 0 )
> 14/02/25 07:18:34 DB : policy not found
> 14/02/25 07:18:34 DB : policy not found
> 14/02/25 07:18:34 DB : policy not found
> 14/02/25 07:18:34 DB : policy not found
> 14/02/25 07:18:34 DB : removing tunnel config references
> 14/02/25 07:18:34 DB : removing tunnel phase2 references
> 14/02/25 07:18:34 DB : removing tunnel phase1 references
> 14/02/25 07:18:34 DB : tunnel deleted ( obj count = 0 )
> 14/02/25 07:18:34 DB : removing all peer tunnel references
> 14/02/25 07:18:34 DB : peer deleted ( obj count = 0 )
> 14/02/25 07:18:34 ii : ipc client process thread exit ...
> 14/02/25 07:18:34 !! : vflt device attach failed
> 14/02/25 07:18:35 !! : vflt device attach failed
> 14/02/25 07:18:36 !! : vflt device attach failed
>
>
> The IPSEC Service log shows:
>
> 14/02/25 07:19:38 ## : IPSEC Daemon, ver 2.2.2
> 14/02/25 07:19:38 ## : Copyright 2013 Shrew Soft Inc.
> 14/02/25 07:19:38 ## : This product linked OpenSSL 1.0.1c 10 May 2012
> 14/02/25 07:19:38 ## : This product linked zlib v1.2.3
> 14/02/25 07:19:38 ii : network send process thread begin ...
> 14/02/25 07:19:38 !! : vflt send device attach failed
> 14/02/25 07:19:38 ii : network recv process thread begin ...
> 14/02/25 07:19:38 !! : vflt recv device attach failed
> 14/02/25 07:19:38 ii : pfkey server process thread begin ...
> 14/02/25 07:19:38 ii : pfkey client process thread begin ...
> 14/02/25 07:19:38 K< : recv DUMP UNSPEC message
> 14/02/25 07:19:38 K< : recv X_SPDDUMP UNSPEC message
> 14/02/25 07:19:38 ii : pfkey client process thread begin ...
> 14/02/25 07:19:38 K< : message REGISTER AH received
> 14/02/25 07:19:38 K< : message REGISTER ESP received
> 14/02/25 07:19:38 K< : message REGISTER IPCOMP received
> 14/02/25 07:19:38 K< : recv X_SPDDUMP UNSPEC message
> 14/02/25 07:19:39 !! : vflt recv device attach failed
> 14/02/25 07:19:39 !! : vflt send device attach failed
> 14/02/25 07:19:40 !! : vflt recv device attach failed
> 14/02/25 07:19:40 !! : vflt send device attach failed
> 14/02/25 07:19:41 !! : vflt send device attach failed
> 14/02/25 07:19:41 !! : vflt recv device attach failed
> 14/02/25 07:19:42 !! : vflt send device attach failed
> 14/02/25 07:19:42 !! : vflt recv device attach failed
> 14/02/25 07:19:43 !! : vflt send device attach failed
> 14/02/25 07:19:43 !! : vflt recv device attach failed
> 14/02/25 07:19:44 !! : vflt recv device attach failed
> 14/02/25 07:19:44 !! : vflt send device attach failed
> 14/02/25 07:19:45 !! : vflt send device attach failed
> 14/02/25 07:19:45 !! : vflt recv device attach failed
> 14/02/25 07:19:46 !! : vflt recv device attach failed
> 14/02/25 07:19:46 !! : vflt send device attach failed
> 14/02/25 07:19:47 !! : vflt send device attach failed
> 14/02/25 07:19:47 !! : vflt recv device attach failed
> 14/02/25 07:19:48 !! : vflt send device attach failed
> 14/02/25 07:19:48 !! : vflt recv device attach failed
> 14/02/25 07:19:49 !! : vflt send device attach failed
> 14/02/25 07:19:49 !! : vflt recv device attach failed
> 14/02/25 07:19:50 !! : vflt send device attach failed
> 14/02/25 07:19:50 !! : vflt recv device attach failed
>
>
> Any ideas?
>
> Thanks,
> Tom
>
> _______________________________________________
> vpn-help mailing list
> vpn-help at lists.shrew.net
> https://lists.shrew.net/mailman/listinfo/vpn-help



More information about the vpn-help mailing list