Windows 7 Home Premium, 64 bit running on a Toshiba laptop with loads of memory and a humongous hard drive.
VyprVPN 188.8.131.5242 - also true in earlier versions.
I also have VMware Workstation installed, which creates at least one synthetic network that is always guaranteed to work, but goes nowhere if no virtual machines are running. (Which, IMHO, is a defect in VMware, not VyprVPN)
When starting the VyprVPN service I (occasionally) get the following dialog:
The VyprVPN service could not be contacted. Would you like to attempt to start the service?
First things first: As a Software QA Engineer of many years standing, this is, without a doubt, one of the very best error dialogs I have ever seen. It succinctly describes the problem and (even better!), offers the user a useful workaround. Two thumbs up!
I notice that this appears to happen in one of two cases:
- There is no “real” (i.e. connected to the Internet), network connection.
- The VyprVPN service attempts to start too soon, before critical dependencies are running.
A potential workaround to case #2 is to set the startup attribute to “Automatic (Delayed Start)” instead of just “Automatic”
I do not know a workaround to case number one.
An additional data point:
If the VyprVPN service is started prior to the user realizing that there is no active network, the VyprVPN application just hangs with no icon in the system tray, no desktop dialog, and no way to kill it except by using the task manager and selecting “Kill process tree”, though a simple “Kill process” may work just as well.
Why this is a problem
I am often abroad, in countries where my local e-mail provider will not allow a mobile SMTP connection. I solve that problem by punching trough to a US based location, (usually NY), to avoid that restriction. To make things both easier and automatic, I have VyprVPN set to start when Windows starts.
However, this is not always the case, as when I am at home, within the US, on a known-good, high bandwidth, network connection - this occasionally happens. (Though I reduced the severity by changing the service’s startup attribute.)
This is also true if I am within the US, using a wireless network, and VyprVPN attempts to start prior to connecting to a live network rather than just VMware’s virtual network
In a future release,
- Make “Automatic (Delayed Start)” the default startup attribute for the VyprVPN service.
- Allow VyprVPN to detect, and ignore, virtual networks set up by virtualization software.
Is there a way to avoid the issue of VyprVPN failing/hanging on a missing network?