Showing results for 
Search instead for 
Did you mean: 
Active Contributor

Hamachi2 Gateways - Lessons Learned

Here are a few things that I've learned in setting up Hamachi Gateways...


  • It's easier to install the client on the gateway before creating a Hamachi Network.  This makes it available to select during the "Create Network" wizards.
  • At least for gateways, it is easier to create the network from the site, not the Hamachi client.
  • The Hamachi Client not only runs on all client computers, it also runs on the Gateway computer.
  • Running the gateway on VMWare vSphere ESX 4.0 (also ESX 3.x) requires the network adapter in ESX to be configured in "Promiscuous Mode".  If it is not configured, network connectivity on the server VM will be lost when the Hamachi Client on the Gateway is installed.
  • Based on the above, I suspect "Promiscuous Mode" would need to be turned on when using a more advanced SOHO or business grade switch like an HP ProCurve.  Consumer grade switches already have it turned on.
  • Must "Disable UAC" on Vista and Server 2008.  Google to find out how.  On 2008 this can be done by Start -> Run -> msconfig -> Tools tab -> "Disable UAC"
  • I've gotten Hamachi to works on Server 2003, Server 2008, and XP as gateways.
  • I've been able to get Hamachi to work as a client on Windows 7 Ultimate, Vista, and XP.
  • On Windows 7 Hamachi required my RSA key to be authenticated.  This showed up as a blocked connection.  Right click -> Details... -> then double click Authentication and click "Trusted"
  • If the client running on the gateway is "Powered Off" it disconnects all Hamachi connections essentially turning the entire Hamachi Gateway network off.   

Tunnel notes - Under connection "details... " in the Hamachi client

  • "Direct" links are the best tunnels and I typically see Round-trip times of 45-60ms where I'm at. 
  • "via Relays" is the next best tunnel and I typically see 100-200ms Round-trip times.
  • "via Servers" is the slowest and with the free Hamachi product I've seen 500+ms Round-trip times.
  • When Hamachi first connects it finds the fastest link then if the fast link drops off for whatever reason, it reconnects with the next fastest tunnel until it connects "via Servers"

Add comments as needed.





New Contributor


New Contributor

hihihi i got it now 

Man Mad

New Contributor

Smiley Happy

New Contributor

Do you know of any one that would be willing to remotly set up two windows server 2008 machine with hamachi gate to create a tunnel? I am more that happy to pay a fee.

New Contributor

I learned a valuable lesson too: Never configure a network for "Gateway" - it simply does not work.

At least, not with a unix server..  Just go for hub-and-spoke instead..



New Contributor

hi im meji

New Contributor

100-200ms on relayed tunnel? Pfft. Its around 500-800ms on relayed.

New Contributor

@tkalfaoglu wrote:

I learned a valuable lesson too: Never configure a network for "Gateway" - it simply does not work.

At least, not with a unix server..  Just go for hub-and-spoke instead..



I have just found the same with windows server 2008 R2.


I spent hours trying to configure a gateway network which just brought the physical network to a crawl because of the network bridge it sets up.


I have now set up a hub and spoke network with one hub and it worked flawlessly first time.


I found this thread extremely useful in getting the network setup properly.

Active Contributor

@thornrag wrote:

It's unintuitively under the "Add/Remove Members" tab on the "Edit Network" page. Once you click that, the radio buttons to select "Gateway" or "Member" (or Hub or Spoke) appear. It's in the FAQ, but of course you have to know what you're looking for.

Almost two years provided my answer.  I've actually had Hamachi running for over a year, but it is so reliable, that I never have to touch it.  Only when I had to re-install Server 2003 (from scratch!) did I remember how unintuitive the setup process is.  Now I have to tell 25 people to reconnect to the server.  Oh well, better than telling them they can't connect to the server, eh? 

Thanks, thornrag.


New Contributor

I suppose you get what you pay for! Can't see paying for this service when it is difficult to establish a gateway network. Can't get a Windows 7 machine on a LAN?homegroup to be seen by any number of clients. All indicate that the gateway is offline, "Domain disabled" in settings, even though the Users Guide states gateway is not possible when the gateway machine is a member of a Domain?!?!?!?! What am I missing having followed the Lessons Learned" post well written at the top of this thread. Thx for the work on this BTW. Wish support was as clear as the suer who posted lessons learned!