barney_5uk
Dear all
I have one notebook where OpenVPN was installed and worked well until Cyberghost was installed on that machine. From that time OpenVPN encoutered issues, the OpenVPN TAP adaptor did not work properly until I reinstalled OpenVPN. Now that user has deinstalled the Cyberghost but from that time OpenVPN does not work anymore at all on that one machine. Even after reinstalling OpenVPN, deleting the OpenVPN folder under Program Files, removing any registry key related to OpenVPN and then reinstalling OpenVPN again it does not work anymore at all.
- the client.ovpn is places in the openvpn\config folder, plus the certificates and keys
- the OpenVPN GUI starts but when I try to "connect" the window whee the log entries should appear stays empty
- when I click on "View Log" then I see this:
Thu Feb 27 17:45:30 2014 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Jun 3 2013
Enter Management Password:
Thu Feb 27 17:45:30 2014 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Thu Feb 27 17:45:30 2014 Need hold release from management interface, waiting...
So I would like to ask ...
Has somenoe ever encoutered such a behaviour? Had ever someone had installed OpenVPN together with Cyberghost and what was that experience?
Does someone know where, other than the OpenVPN program folder and the registry, might be settings for OpenVPN located which might be of use here?
Kind Regards
Bernard
barney_5uk
Thanks for that answer. At the moment I don't have access to the notebook in question so I will check this later. I can however produce the issue on other clients when I insert the "hold" command into the client.ovpn.
- when the "hold" command is inserted I get exactly that state, the status window is empty and nothing is done to connect
- when I remove this "hold" command I get the usual connection and the status window is filled with the log
however when I use "hold off" or "hold release" command I still get that same hold state, with no connection.
I suspect that the Cyberghost (which has installed an own customized version of OpenVPN) has left some settings somewhere in the system which prevents OpenVPN from leaving this "hold" state after its deinstallation.
Kind Regards
Bernard
barney_5uk
Thanks for all -
finally the issue is solved by disabling and step-by-step re-enabling the Avast (!)-
I can just assume that the Cyberghost did interfere his customized OpenVPN with the already installed real OpenVPN.
I will also try to find out what the Cyberghost does with it's built-in customized version of OpenVPN and when I find out more about that I will post it here - maybe it might be usefull for others.
Kind Regards
Bernard
