On 20/02/2017 19:32, debbie10t wrote:
>
>
> On 20/02/17 16:36, Samuli Seppänen wrote:
>> On 20/02/2017 17:09, Samuli Seppänen wrote:
>
>>>
>>> Debbie10t: can you launch Powershell and issue
>>>
>>> Get-WMIObject -Class win32_service -Filter "Name='OpenVPNService'"
>>>
>>> With default settings it should output this:
>>>
>>> ExitCode : 0
>>> Name : OpenVpnService
>>> ProcessId : 0
>>> StartMode : Manual
>>> State : Stopped
>>> Status : Ok
>>>
>>> If "StartMode" is truly set to Manual, yet after a reboot "State" says
>>> "Running", then we have a genuine problem.
>>>
>>
>> Could you run the above Get-WMIObject command just in case? That would
>> help rule out the possibility that the graphical UI is confused about
>> the StartupType of OpenVpnService.
>>
>
>
> (Knowing about Windows Faststart #804)
>
> Stop running openvpnserv2 + openvpn.exe
> REBOOT
>
> Result of powershell:
>
> ExitCode: 0
> Name: OpenVPNService
> ProcessID: 2324
> StartMode: Manual
> State: Running
> Status: OK
>
> Weird ?
>
> Thanks for your help :)
> Regards
>
>
Very weird indeed.
Does the application event log show the usual message for starting
OpenVPNService? Here's a rather naty Powershell command-line to check
that out:
Get-EventLog Application|Where-Object { $_.Source -eq "OpenVPNService"
-and $_.Message -like "*started*" }|Select -Last 5
Or you can just use the Event Viewer. In any case you should see a
message "Service started successfully." with a timestamp that matches
the time you rebooted,
My hunch is that _something_ outside the usual boot procedure starts the
service.
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users
