Using Windows 7 Pro RTM, Hamachi 188.8.131.52 (just upgraded from the last 1.x version to try fixing this problem). I've been using Hamachi for a while for personal use, to keep connected to my Windows Home Server while away from home. It works great, for the most part. But, it seems that there is one large problem that Hamachi causes, for some reason. It may be a common network configuration problem, but since Hamachi is supposed to be "set and forget" - or, "zero configuration" - I figure this should be brought to light.
Windows 7 (as well as any other networked OS, judging by the problem) seems to have a bit of difficulty with Hamachi's default gateway - which I don't understand the purpose of, to begin with (why have a nonexistent gateway on a private LAN segment?). Here's the problem:
LAN IP: 192.168.4.2/24
Default gateway: 192.168.4.1/24
Hamachi IP: 5.117.xxx.xxx/8
Deafult gateway: 184.108.40.206/8
This poses a bit of a problem: there are now TWO default gateways. Windows presents a warning about using "multiple gateways on multiple disjoint network segments" (or something to that effect) causing network connectivity issues. If a packet from a web browser (or any other application - it hinders ALL network access except across the LAN) is destined for, say, 64.129.xxx.xxx, which is outside both subnets, which gateway should Windows use?
Well, Windows seems to pick one at random and sticks to it. I'm finding myself frequently having to disable my Hamachi network adapter (taking it offline or exiting doesn't fix it) and network access springs back to life. I don't know why Hamachi needs a default gateway on a /8 network, which can only serve to confuse Windows, but Hamachi complains if I manually configure my IP.
Can anything be done to properly solve this problem instead of band-aiding it by disabling it every day?
Well to fix a brain dead feature of Windows 7 (and Vista I think) a default gateway is required in order for Win 7 to recognise the LAN as a "Private Network" and not a "Public Network". Recognising Hamachi (or any other private network as a public network) causes Windows to put security measure in place that you almost certainly don't want.
I've not had the problem you report though, and I don't think others have either, the gateway on Hamachi should be set as a very low priority (this is certainly how Hamachi sets it) and as such it should only try to use it when and if the higher priority and real gateway is not working.
My guess is one of the following
Something is setting the proper default gateway to a low priority
Something is setting Hamachi default gatewat to high priority
Your proper local gateway fails to respond from time to time causing Windows to try and switch to Hamachi
I am having the exact same problem with Hamachi 2 and Win7. That is with Hamachi 1.x everything worked fine, but now with Hamachi 2, the internet is very slow and intermittent if I do not disable Hamachi. I also have a static IP for my LAN, and get the same Default Gateway conflict message when I go into my adapter TCP/IP settings.
I have this same problem on all three of my computers that use Hamachi and Windows 7, and have worked around the issue for quite some time by disabling the adapter. I'm very interested in a real solution.
Looks like this thread was revived after a year but still no solution. I'm on Windows 7 Professional and I have the same problem. It pops up after resuming from Sleep mode, and not every time - maybe one in 5 times. This morning I resumed from Sleep and:
- I couldn't resolve any sites by DNS
- I could access my router address 192.168.18.1
- I disabled the Hamachi adapter and everything started working again
- I re-enabled the adapter and DNS stopped working again
- I went to TCP/IP settings for my Ethernet card, made no changes, clicked OK, and then everything started working again.
I really don't want to have to keep going through this silly routine again and again. There must be a better way.
I am trying an experiment to see if I can make things a little more stable with my adapters even with the Hamachi adapter enabled. I have gone into the TCPIP settings for each of my adapters and have manually set the interface metric for each adapter. My wired adapter I set at 1, my wireless adapter I set at 2 and the Hamachi adapter I have set at 3. Usually these are all set to automatically choose. Anyway, so far so good. Wireless hasn't gone out on me at all yet (granted it has only been 10 minutes but I've had it go out a lot quicker than that). I'll try to remember to update as I have used the computer more. I plan on working several hours tonight so that should give me a good indication as to whether this fixes it or not. If you want to try this and need help finding where to manually change each adapters metric, let me know and I can give you a step by step.
Just a quick update. The problem definitely still exists. Whenever I reboot my computer, the hamachi network adapter will automatically enable itself even though I had previously disabled it. So, when I suddenly am unable to browse the Internet or access network shares, I have to remember to disable the hamachi network adapter again and immediately I am able to browse again and it never has the problem again unless I enable the Hamachi network adapter. I wish someone could come up with a solution. Before I figured out that it was Hamachi causing the problems, I thought that maybe my wireless card was going out. Glad it isn't that but would love to see a real solution.
I am running Windows 7 Ultimate 64 bit. Please come up with a solution soon.