...Because someone's gotta tell the story...


To return to the main Blog List, click Full Blog Listing.


Group Policy

Hamachi's VPN Gateway and Hyper-V

Wednesday, December 01, 2010 in Technical Articles (Views: 3795)
One of the thrills to not always being home is that I want to be connected to my network. For those who know the theme of the website, it's simple: is a hobbyist project gone way overboard.

Up front, sorry for a lot more bolding than usual in this article. There are a few little annoyances that get you, but again, does a great job of providing a great free product for the IT Pro who wants to expand his home network outside of the home.

A great product I have found for such remote access is's Hamachi. With Hamachi, you can set up one of 3 VPN types (I chose Gateway being the most effective for me). With the Gateway, you can set up a single box to act as a "traffic cop" between the two networks. The gateway will eventually provide name resolution, once the clients are all discovered. The Gateway can be a simple workstation, XP Pro or later recommended, not joined to a domain or another network.

Note: Hamachi is a free product for home users of up to 16 clients. There is a catch here - if you are installing this in any commercial enterprise, you must license with them.

What if you have a Domain model at home? It's not a problem - the Gateway resolved me to my domain, and I was able to run gpupdate, modify group policy, and work as though I was connected to the network.

What about that "goofy" bridge it needs to set up? One complaint I did see is that the bridge works in VMWare, but not Hyper-V. I have found a cute little fix for this. You need to do 2 things:

1. Set up compatibility mode for the network adapter (bridge).

2. Set up a static IP for the network bridge.
Note: The bridge is set in Non-Promiscuous Mode, and needs to be set to compatibility. Once you do this, the static IP was what got the VPN working for me.

Compatibility mode can be set by using netsh. Here's a couple of commands you may find helpful:

• netsh bridge show adapter
• netsh bridge set adapter 1 forcecompatmode=enable

Make sure to record the adapter number of the bridge, in my case, it was 1 (above).

As always, I hope you found this blog helpful, and happy computing.


Related Blogs You May Be Interested In:

To leave a comment, please log in and/or register.