virtualbox.org

Ya I've noticed this thing too. And I created another thread for it. In VirtualBox gui window, I have dhcp enabled. Whereas, when I do 'ipconfig /all', I see that dhcp is disabled. Not sure if its a known issue.

Ethernet adapter VirtualBox Host-Only Network:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-00-74-BF
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::7d41:c6e0:e4c:ecb1%20(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 721944615
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-80-91-EE-D4-BE-D9-48-26-C5

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

As I said the host side does not see nor use the VBox DHCP server it is a fixed address.

Perryg wrote:Actually the disabled on the host side is normal and expected since it would cause a conflict.

Isn't the OP question about the fact that he doesn't get an IP within the range of the VB DHCP server? If so, it would be an issue since the DHCP is disabled and no IP is handed out to the guest.
If it is about reaching the 192.168.0.x range from the guest, the host must be configured with appropriate routing functions and all the other PCs that need to be reached on the LAN must have a static route back to the host.

It would if it meant that.

If you look at the VBoxManage list hostonlyifs you will see the DHCP disabled. If you look at the host side ipconfig you will see the DHCP disabled.
That is the way it should show because it is static on the host side not dynamic.
Now you look at the VBoxManage list dhcpserver you see that the range is defined and the server is enabled.

At this point I must assume that everything is as it should be unless I see other information that shows me it is not working. It will be impossible to diagnose without the network information and we just assume too much.

Next point, the OP stated that it appeared that the VirtualBox DHCP server was handing out an address of 192.168.0.* which we see it isn't. At that point I suggested that this might be the OPs router, but nothing more was said on the OPs side about that.

We also don't know the NIC structure on the guest/s. For that we would need to see the VBoxManage showvminfo <guest> to see exactly how the network was defined in the settings.

You are indeed totally right.

@Krosty, could you show us the output of (replace VmName):