Hamachi Gateway Fails with VB 4.0.6
Posted: 17. May 2011, 17:44
I know this is a rather obscure configuration, but I'm still curious if someone else has run into the same problem.
I'm running VB 4.0.6, hosted on Window 7, and have a WinXP (SP3) guest VM. The VM is running LogMeIn Hamachi 2.0.3.111 and is configured as a Hamachi Gateway (so it provides entry into the rest of my network for remote Hamachi clients). It has worked perfectly for quite some time, that is, until I updated to VB 4.0.6. Now the Hamachi Gateway fails. It just sits there endlessly trying to resolve w/ LogMeIn. However, if I revert to VB 4.0.4 it works again. I even tried changing to a Windows XP host, no difference. Something seems to have changed in VB 4.0.6 that's resulted in this failure. Note, if the VM is configured as a simple Hamachi client, it works fine. It's *only* a problem when I attempt to configure it as a Gateway. Something seems to go awry when the local and Hamachi adapters are bridged, but I'm just not sure what. Anyway, for now I'm just sticking w/ VB 4.0.4. But I'm a little concerned that this is such an obscure configuration that no one will realize the problem even exists.
I'm running VB 4.0.6, hosted on Window 7, and have a WinXP (SP3) guest VM. The VM is running LogMeIn Hamachi 2.0.3.111 and is configured as a Hamachi Gateway (so it provides entry into the rest of my network for remote Hamachi clients). It has worked perfectly for quite some time, that is, until I updated to VB 4.0.6. Now the Hamachi Gateway fails. It just sits there endlessly trying to resolve w/ LogMeIn. However, if I revert to VB 4.0.4 it works again. I even tried changing to a Windows XP host, no difference. Something seems to have changed in VB 4.0.6 that's resulted in this failure. Note, if the VM is configured as a simple Hamachi client, it works fine. It's *only* a problem when I attempt to configure it as a Gateway. Something seems to go awry when the local and Hamachi adapters are bridged, but I'm just not sure what. Anyway, for now I'm just sticking w/ VB 4.0.4. But I'm a little concerned that this is such an obscure configuration that no one will realize the problem even exists.