Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Wednesday, February 23, 2011

Failed to connect to the engine

I have this issue on several of my Clients, however, hamachi2 starts anyway and eventually connects. I just  do not get the interface to pop-up until i manuall start hamachi2.
Based on this I suspect an addition of DependOnService stringwith the correct value(tcpip?,lanmanworkstation?,NetBIOS?, NetBT?) in the HKLM\SYSTEM\CurrentControlSet\Services\Hamachi2Svc key would solve the problem
[put two ampersand symbols instead of ASAS]

When you put the start of the UI it in the Startup folder it might get started before the Hamachi2 tunnel service is up and running.
Put a delay in front of it. There are other more elegant sollutions. But this simple one works for me.
C:\Windows\System32\cmd.exe /c sleep 20 ASAS start "" /MIN "C:\Program Files\LogMeIn Hamachi\hamachi-2-ui.exe"

I wrote this little program for fixing the issue.
it set Hahachi service autostart to manual.
It start hamachi
Download link:
The best solution... in case you guys haven't notice at the services where the logmein thing is... it says at properties clearly what the path to the actual executable is... and that is hamachi tunneling exe not the ui one... and also you can see a -s at it... well ta da! make a shortcut to the exe (the one with tunneling engine thing:hamachi-2.exe) and add at path a -s. this also opens hamachi for me... i mean no need to use the other shortcut well at least for me...
I added a download also in case you guys can't make it work... oh... and notice that the path to the downloaded shortcut i put is for my computer... change it accordingly to ur path.
(Read more at link)
After getting the Hamachi 2 update (without a prior notice, nicely done… No more auto update if they continue to break stuff) I started to notice a bunch of XPs receiving this error after a reboot: Failed to connect to the engine.
Hamachi is auto started, at boot, because we have a shortcut in the startup folder. No other way to auto start the free version (as far as I know).
Yet, when starting Hamachi manually after the PC had booted, there were no more errors. So it’s clear Hamachi tried to start before the engine (see services.msc -> LogMeIn Hamachi Engine or something) was started.
And reinstalling Hamachi only seemed to work on one of the XPs.
As there’s no easy way to delay the starting up of a program, I used some dirty vbs and batch… Kinda.
Here’s my solution:
Place both scripts in the Hamachi directory (c:\program files\logmein hamachi\)
Set WshShell = CreateObject("WScript.Shell")
WshShell.Run chr(34) & ".\hamachi.bat" & Chr(34), 0
Set WshShell = Nothing
@echo off
ping -n 30 >NUL
"C:\Program Files\LogMeIn Hamachi\hamachi-2-ui.exe"
Hamachi.vbs will start the bat file. This seems to be the only way to prevent a command prompt from opening (and staying open all the time).
Hamachi.bat will ping itself for 30ish seconds (don’t think there’s a cleaner way to do this…) and then start the Hamachi GUI.
If you’re still having problems, increase 30 to something like 60 or even more.
Anyway, last thing you’ll need to do is to make a shortcut of hamachi.vbs, and drag it into the startup folder.
Reboot, wait a bit, and enjoy.
You can do this without vbs. Just use “start” before path to hamachi:
 @echo off
  ping -n 30 >NUL
  start “C:\Program Files\LogMeIn Hamachi\hamachi-2-ui.exe”
You can also use “hidcon.exe” to start your bat file in hidden console widow.
> hidcon hamachi.bat
I found this tool rather hard to find now…
so I’ve uploaded it here:
MD5: B2DADAB18C318443301D0087CD7200BA

No comments: