Can you please provide the option to power on hamachi from a command line? This is really becoming a problem, here is what happens:
workstation restarts, due to windows operating system update, environment power condition, etc, and once everything restarts, hamachi is in the "powered off" condition. Then we are screwed, because there is no remote access, and now a human being has to make a physical trip to the workstation to click on "power on".
Please add this functionality, I am a long time hamachi user. But this power off thing that is happening at random with windows 10 is really becoming an issue.
Solved! Go to Solution.
So, I've figured out a way to deal with this. I wrote a windows service that monitors the logmein service and it's power on status. If either get turned off my service restarts them. So far has been working very well and ended the random shutdowns that can happen.
So, I've figured out a way to deal with this. I wrote a windows service that monitors the logmein service and it's power on status. If either get turned off my service restarts them. So far has been working very well and ended the random shutdowns that can happen.
I can't speak for Jerry but an easy way to check the status of the Hamachi connection is
c:\Program Files (x86)\LogMeIn Hamachi\x64\hamachi-2.exe --cli list
Exclude the full pathname if appropriate in your specific case, etc etc. If the VPN is currently off, this will be the result
You have no networks.
If the script picks that up as a response, have it run
c:\Program Files (x86)\LogMeIn Hamachi\x64\hamachi-2.exe --cli logon
And that's the equivalent of pressing the power button on the UI. That way whenever the Hamachi is disconnected for whatever reason, it will attempt to reconnect and log back on without the need of the UI.
For some reason on a new computer that I installed Hamachi on, it seems to randomly decide not to auto-connect (aka "Power" on) and it would be offline, requiring me to press the power button on its UI. Other times it would auto-connect just fine. Apparently this is controlled via a config file some place but the fact that it isn't being consistent was something I found odd. So what I did was create a task run in Task Scheduler to execute that previous command (hamachi-2 --cli logon) set to run "At Startup", set it to run with Administrative privileges whether a user is logged in or not, and set a Condition for it to run after getting a Network Connection with the device that provides internet access. This way Hamachi is already connected to the VPN before anyone logs on (assuming the person doesn't log in fast enough to get ahead of it). From now on I won't have to deal with the randomness of it not auto-connecting or worry about its configuration set to do so.
Thanks @nawcom for sharing this. This is extremely helpful and was not able to find any evidence of these functions existing when searching documentation. Really appreciate it!
So there is a an ini file that hamachi uses, in the windows serviceprofiles area.
h2-engine.ini
In this file, there is a reconnect line
Reconnect 1 means powered on
Reconnect 0 means powered off
Basically the service I wrote polls that file every so often, if it finds the state powered off, it stops the service, changes that line, and then restarts the service. It also checks to make sure the service is running and also starts it up if the service is stopped. I also keep the hamachi in "do not self update" mode...
The other suggestion is good too.
Hi guys,
I created a batch file that turns on hamachi and enables a network on startup. To get it to run subtletly on startup I created a shortcut to the file and changed the properties so it starts minimized.
Open notepad and paste in the following code.
cd C:\Program Files (x86)\LogMeIn Hamachi\x64 hamachi-2.exe --cli login hamachi-2.exe --cli go-online <network ID>
NB: 1: The first line will vary depending on the location of your hamachi install
2: Replace the "<network ID>" with the numerical identifier displayed when you hover over your Network in the Hamachi client.
Save As and add ".cmd" to the file. Store it somehwere safe (I put it in the hamachi folder) and create a shortcut.
Open start menu, type "run" and press enter.
Type "shell:startup" to open your startup folder and move the shortcut here. Finally right click on the shortcut, click properties and change the dropdown menu adjacent to "run" to Minimized.
Hope this helps, I'm not a coder so aplogies if this doesn't work for you. I built this out of some very basic how to guides and some trial and error with the hamachi-2.exe in CMD.
ganeshowen:
you wrote: 2: Replace the "<network ID>" with the numerical identifier displayed when you hover over your Network in the Hamachi client.
When I hover over over my network it just gives me the network name as the network ID. All letters, no numbers.
Hi,
I've attached a screenshot of what I see when my mouse hovers over the network. Where the red-line is where I see a numerical Network ID (XXX-XXX-XXX) that I used in my simple batch file.
Hope this helps.
Looking at your screen shot I see I am looking at the same place you are. The only difference is my shows the network ID to be the same as the network. In otherwords, your network ID should be Arena if it is working like mine. One difference though, your type is gateway, mine is mesh. Could that make a difference?
Just to clarify, after rebooting my computer, Hamachi starts after I log in just fine. Which of course is no help at all. I need it to be working before logging in otherwise I can't get to it to log in. Is this what your batch file is suppose to fix? Or have I misunderstood.