PCinvent Studio - Hamachi VPN & VMware Troubleshooting

Read More Articles in: Technology>>>System

This Article is written by This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

VPN and Virtual Machine technologies are becoming very popular. If you have Hamachi VPN installed in your Vmware host server, you might found out that next time you reboot, your guest VM will not be able to ping outside. And sometimes, when you want to start Hamachi, it will just threw out an error, Let's see what's going wrong......

VMWare

Many's configurations of VMware are set to Bridge which is virtualized network adapter which can have a unique IP. The problem is that the default setting in VMware is to have Automatic choose an network adapter. So guess what, after you install the Hamachi which will created a virtaul network adapter, it will choose that Virtual Adapter for bridge when next time you reboot. No wonder you will not be able to ping then.

Solution is that go to Vmware->Host->Virtual Network Editor->Disable Automatic Bridging->Choose your right physical network adapter in "Host Virtual network Mapping

Hamachi in Linux

You found out that Hamachi threw this error:

 
          tap: connect() failed 2 (No such file or directory)

 
When you  restart your machine. Tried Re-install Hamchi and still got the same result???

 
Basically, you will just need to type:

 
          tuncfg tuncfg

 
Then you will be able to hamachi start.

Comments (2) Add Comment

...
written by Mike grossman, September 17, 2008

I had the same issue, it took me about an hour to figure out what the issue was. I was searching google for "vmware bridge problems" and not even thinking about hamachi causing the issue. I finally took a wild guess and explored the properties of the hamachi adapter. Anyway, you may want to add "vmware bridge problems" to your tags so people can find this post in the future... (unless this comment is enough to index those keywords on google)