Re: W2K/2.0-pre14 service start troubles|
"Juergen K. Zick" <juergen.zick,AT,ifa,DOT,uni-kassel,DOT,de>|
Wed, 25 Sep 2002 13:53:42 +0200|
I observe exactly the same and could not yet figure out why this happens
... My solution just is to start the CIPED via the NET command line
interface manually ..
I have some W2K boxes where it works without problems, on some others it
doesn't work ... and the combination W2K <--> W2K or W2K <--> does not
effect this strange behavior ...
At least the registry keys and their contents are identical ....
Any other idea where to look Chris, Olaf ? Event logs were no help as well ...
>The CIPED_Service doesn't start on boot despite being set to 'Automatic'.
>I've got a Win2K (Pro, SP2) box running CIPE-Win32 2.0-pre14 - it works
>perfectly except that the CIPED_Service (listed as 'DKW Heavy Industries
>VPN Adaptor. Service') doesn't start on boot, despite being listed as
>'Automatic'. I've tried running 'cipsrvr.exe install' to correct this,
>but it hasn't changed anything. Solutions / work-arounds much
>The system takes longer to boot, and in particular sits with a message
>saying 'Preparing network connections' for longer than I recall seeing in
>Win2k service settings:
> Start parameters: none
> Action on failure: take no action
> State after boot: stopped
> Startup type: automatic
>Win2k Pro SP2 with CIPE-Win32 2.0-pre14
>(192.168.1.2 / 255.255.255.0) CIPE interface
>(192.168.2.2 / 255.255.255.0) Real IP
>Linux 2.4.18 (RH 3) smp with CIPE-1.5.4
>(192.168.1.1 / 255.255.255.0) CIPE interface
>(192.168.2.1 / 255.255.255.0) Real IP
>The Linux box's CIPE connection is permanently available (always running,
>and never terminates on errors), so it is certainly available at boot
>time, should Win2k need that.