Skip to main content

Installing Hamachi (free edition) on SBS 2003 Server as a service

Hamachi is a free VPN networking tool that enables easy creation of VPN's without having to worry about having static IP addresses or understanding VPN technologies very much.

You can download it for free from here:

While the product is free it comes for free with a number of limitations one of which is it can't be installed as a service unless you pay for a premium subscription.

However with the aid of the Windows Resource kit for your platform you should be able to follow this procedure to get it running as a service. The following tutorial will show you how to configure Hamachi to run and automatically connect in Windows 2000, XP, and 2003.

To install Hamachi, simply download and run the install file from the Hamachi website. I recommend installing Hamachi in the default folder and not having it run automatically, especially if you would like to have it run as a service, like I describe below. After the installation you will need to reboot the computer.

After rebooting the machine start up Hamachi from the newly created shortcut. It will give you instructions to set up your account. Basically, you pick a nickname and it phones home to the Hamachi server to obtain your unique 5.X.X.X IP address. You might want to do this step at the same time on all your computers you plan to access with Hamachi. That way they will all get IP addresses close to one another. You then click “create new network” and enter a network name and password. I recommend using a site like to obtain a secure password.
Once you have installed Hamachi on all the computers you plan on using, you will need to click the button to “Join existing network” on all the other PCs. Enter your network name and password and click “Join”. Once it detects the the other computers it will place a green dot next to their entry in the list. You should then be able to access network shares and remote desktop or VNC into the computers. Use the assigned 5.X.X.X IP address to access each computer. One limitation of Hamachi is that you cannot currently use the program to securely surf the net from a remote location without using some kind of remote control app. Another program called OpenVPN is much better suited for that and other advanced routing tasks. I will cover OpenVPN in another article.
Running Hamachi as a Windows service:
I highly recommend running Hamachi as a Windows service. It takes a little more effort, but here’s how you do it.
You need two utilities - instsrv.exe and srvany.exe. Both can be found in the Windows Server Resource Kits. You can find the Windows 2003 Server Resource Kit here. But it is rather large and won’t install on Pre-XP Windows machines. So you might be better off doing a Google search for a site like this.
Once you have these utiltites, copy them into your Hamachi directory. (I’m going to assume that you used the default directory from here on out.)
Go to Start - Run - and type cmd to open the Command Prompt
Type these commands in order and hit enter after each:
cd C:\Program Files\Hamachi\instsrv AutoHamachi “c:\program files\hamachi\srvany.exe”
This will add Hamachi as an available service in Windows.
Edit the Registry:
Then you need to edit the registry to run the service properly. Add one of the following entries according to your Windows version.
For Windows 2000: (Win2000HamachiServiceConfig.reg - right-click, save, and run)
HKLM\SYSTEM\CurrentControlSet\Services\AutoHamachi\ParametersApplication = c:\\program files\\hamachi\\hamachi.exeAppDirectory = c:\\program files\\hamachi\\AppParameters = -srvany
For Windows XP / 2003: (WinXPHamachiServiceConfig.reg - right-click, save, and run)
HKLM\SYSTEM\CurrentControlSet\Services\AutoHamachi\ParametersApplication = c:\\program files\\hamachi\\hamachi.exe -srvany
UPDATE: With the new version the above registry keys have an additional command to point the service to the correct profile. Instead of simply the -srvany you need to add a -config tag followed by the file path to it. By default the config file will have the path:
C:\Documents and Settings\_your_user_name_\Application Data\Hamachi
So for the new version you will have a string like this:
-srvany -config “C:\Documents and Settings\Administrator\Application Data\Hamachi”
Note: Don’t forget the quotes around the file path and replace “Administrator” with your username.
With the later version you can now skip ahead to the “Configure the service” section below.
Next you need to copy the user profile data you created during the installation from the current Windows user to the default system user in the registry. This needs to be done so that when Hamachi runs as a service it will have access to the info needed be able to connect to the virtual network you created. There is several ways to copy the necessary registry data from one area to another, but this is the only way that I have found that works on all versions of Windows.
Go to Start - Run - and type regedit and click OK to open up the regsistry editor.
Navigate to:
HKEY_CURRENT_USER\Software\Applied Networking
In the top menu go to File (or Registry in server version) - Export (or Export Registry File)
Give the file a name and then save it.
Open the file in a text editor like Notepad.
You need to edit the file to replace the two instances of:
Save the changed file as a .reg file and double-click it to apply the data to the registry. This effectively copies the Hamachi user profile from the original location in the regsitry to HKEY_USERS\.DEFAULT
Note: The copying of this data can also be done at the command prompt using the reg.exe program’s copy command, but it is not available on all versions of Windows.
Next you need to make sure this registry key is set to the value 1 so that Hamachi automatically connects on startup: (HamachiAutoConnect.reg - right-click, save, and run)
HKEY_USERS\.DEFAULT\Software\Applied Networking\HamachiAutoConnect = 1
Configure the service:
Go to Start - Control Panel - Administrative Tools - Services
Right Click AutoHamachi - click Properties
Select “Log On” tab - check “Local System Account” and then under it check “Allow service to interact with the desktop”.
Go back to the “General” tab and for Startup Type select “Automatic”.
Reboot the machine and Hamachi should automatically start and connect. You should then be able to start up Hamachi on the the other computers and verify their connectivity.
To make it easier to access other computers on your network, add the 5.X.X.X IP addresses with their corresponding host names to the hosts files of all the PCs.
Note: If you do run into any errors or it just doesn’t work for you, make sure you double check the syntax of everything. Make sure Hamachi is not running during any of the stages of configuring it as a service. Also, check Hamachi’s settings to make sure it is not set to automatically start up when you login. Feel free to post a comment if you encounter any other issues with this process.
Other Hamachi links:
Here’s some links to info on using Hamachi on other operating systems and some other uses:
Running Hamachi as a service in Linux:


vpn keys said…
Awesome! Its genuinely awesome article, I have got much clear idea regarding from this piece of writing.
Best vpn

Popular posts from this blog

Install or Reinstall TeamViewer 11/12/13 Personal (Non-Commercial) License on Windows Server (2012/2012 R2/2016 etc) [Updated Dec 2017]

After running out of the TeamViewer commercial trial period I sought to find a solution to the problem of having to buy an expensive licence for my home server (which is only used for non-commercial personal use).[Update Dec 2017]: I can confirm that these procedures still apply and work with Teamviewer version 12 and 13 also (as tested on Windows Server 2016).
Procedure A: If TeamViewer is NOT Already Installed (Note: If it is already installed, then first follow procedure B. below)Download and Run the installer downloaded from On the Welcome to TeamViewer page be sure to check the "Show advanced settings" check box (outlined in red at bottom left in picture), then click "Accept - next". Leave the "Advanced settings" installation window open (as shown above) and start Windows Explorer (i.e. the file manager, not Internet Explorer). Now go to your temp directory by typing "%tmp%" into the location bar and hitting enter.…

Removing the WLAN / WiFi pcie card whitelist on Lenovo IdeaPad u410 Touch with BIOS update


I recently (early 2016) acquired a 2013 Lenovo IdeaPad u410 Touch.

It was not my first choice but still useful but I wanted to upgrade it to more recent tech and make it more usable as it is not the fastest CPU around, i.e. an i5-3337U dual core (quad thread) at 1.8GHz.

First thing I did was upgrade the BIOS to latest (as anyone would/should do really) version 65CN99WW (8/28/2014) available here:

I then added 2 x Kingston SO-DIMM KVR16LS11/8 1.35V (Low Voltage) 8G DDR3 1600 Notebook Ram SODIMM's despite the specs I could find all saying it would only take 8GB and it works fine with the 16GB as the Intel i5-3337U CPU (says 32GB) & Mobile Intel HM77 Express Chipset specifications suggest.…

Migrating/cloning an Apple MAC OSX with Windows 7 / 8 / 10 Bootcamp partition to another hard or solid state (HDD / SSD) disk drive (Updated March 2018)

I got a Mac Book Pro 13" in 2012 that in 2016 I upgraded to a 240GB SSD from a similar sized 250GB HDD.  Since then I have followed this procedure a number of time for friends and customers. This week I again had to upgrade that same Mac Book Pro from the 240GB SSD to a new 480GB SSD and again came across a number of problems.  For this reason, I have decided to invest my time in documenting this troublesome process for the benefit of others and so next time I have to do it I won't have to remember and re-discover everything again.

TL;DR - The Crux of this article is that unfortunately, there is no easy way to just copy the whole old drive, with the different Mac and Windows Bootcamp partitions to a new drive. However, with this guide, the complex process is fully explained and broken up into five manageable and easy to understand processes along with their individual steps to do so.

NOTE: I use the word 'drive' loosely here but these processes could work to/or from eit…