virtualbox.org

The patch works great for me too. THANKS !

This is a show stopper, really. The built-in DHCP server isn't giving out IPs when using "internal network" either. Had to downgrade because of it.

Sadly this bug is still present in 4.0.2 and the patch won't work on the new VBoxC.dll.
I hope this get's fixed by the devs ASAP.

Sadly this bug is still present in 4.0.2 and the patch won't work on the new VBoxC.dll.
I hope this get's fixed by the devs ASAP.

Same here. Was very much hoping 4.0.2 would fix.

To all having DHCP server problems with host-only: here is a link to the test build with the fix: http://www.virtualbox.org/download/test ... tiArch.exe

Please give it a try.

Appears to be working for me. I now have hostonly connection on 192.168.56.101 working like it used to. Thanks for the update.

Shutdown vm (ubuntu) > uninstalled 4.0.2 > installed version above > rebooted host (win7)

Ah, nice. Test build fixes the problem for my VMs. Thanks.

reinstall virtualBox by file "VirtualBox-2011-01-21-19-21-01-win-4.0-rel-4.0.3-r69593-MultiArch.exe".

Host-Only Addapter in Both WinXP SP3 Guest & Win7 x86 Guest is able to get ip from VirtualBox DHCP.
Both Guest are able to ping Win7 x86 HOST (192.168.56.1).

However,
the Win7 x86 HOST (192.168.56.1) is able to ping Win7 x86 Guest.
the Win7 x86 HOST (192.168.56.1) is NOT able to ping WinXP SP3 Guest.


In Win7 x86 Guest, it is able to get HOST workgroup share by command
"net use y: \\192.168.56.1\wgshare password /user:userid"

In WinXP SP3 Guest, it is NOT able to get HOST workgroup share by command
"net use y: \\192.168.56.1\wgshare password /user:userid"

I've finally (tenatively) fixed my problems with this.

Host: Windows 7 Home Premium x64
Guest: Fedora 14 x86

At first, the guest was not getting an IPV4 address. The 4.0.3 pre-release resolved this problem. However, I could not communicate with the guest. Pinging the guest gave me "no route" errors, although I could ping the host from the guest by IP address.

I used Windows' network connectivity troubleshooter which noticed that the Host-Only adapter on the host did not have DHCP enabled. I allowed it to run the fixes, which the troubleshooter claimed didn't work but inspecting the Host-Only adapter afterwards revealed that DHCP was now enabled. IPCONFIG confirms an IPV4 IP address. I am now able to ping the guest.

I hope this helps others!

The patch below also worked for me:
> http://forums.mydigitallife.info/thread ... server-bug

I still didn' t try the alpha 4.0.3

I was having similar problems. I upgraded to 4.0.4 (released on Thursday) and now it's working perfectly.