I installed wireshark on the host and the guest and I can see the DHCP requests and offer on the host but the guest doesn't see the offer. I can self assign a fixed IP on the guest and everything works fine.
I can reproduce the issue with 5.1.14 r112924 and 5.0 but 4.3.40 works fine
BillG wrote:Why did you change the IP address range for the host only adapter? By default it uses 192.168.56.0/24 . Did you change the DHCP service as well?
I deleted my .virtualbox folder to reset the IP settings and there's no change. The guest still can't get an address.
I'm not clear on what you mean by "change the DHCP service". Do you mean change a setting on the guest? DHCP is supposed to be mostly plug and play and if I switch the virtual machine settings to provide a NAT network, the guest picks up that address just fine.
Question, Nanocyte, where is the text in the Code tags coming from? looks like the output of a command. If so, please state which OS it came from, host or guest, and what command.
Since you are experimenting with Linux (free except for download time), I would try downloading a normal Ubuntu to a new guest, or even make a new Lubuntu guest, and set the guest network card to your host-only network, and see what happens.
I did a test with an XP guest and a DSL guest, set to a host-only network with a DHCP server active, and got a DHCP-served IP address on the guest network adapter in both guests. I am only on 5.1.6, though.
I concur with Bill, sounds like a guest misconfiguration, or possibly a DHCP server misconfiguration in Virtualbox.
Here are my settings: (note the unusual third number was set by Virtualbox after I had made and deleted a few Host-Only networks in testing something else once.)
Adapter
IP address: 192.168.162.1
Network Mask: 255.255.255.0
DHCP server enabled
Server Address: 192.168.162.2
Server Mask: 255.255.255.0
Lower bound: 192.168.162.100
Upper bound: 192.168.162.150
I'm fairly confident it's not a guest misconfiguration because the Guest DHCP client is able to get an address if I select "NAT" or if I downgrade to 4.3. I'm guessing it's something weird in Windows 10 (the host) that conflicts with something introduced in Vbox 5.
Last edited by socratis on 25. Jan 2017, 22:11, edited 1 time in total.
Reason:Removed unnecessary verbatim quote of the whole previous message.
scottgus1 wrote:Could very well be a new issue. How did the fresh Ubuntu guest work?
So, I downloaded Ubuntu 16.04 64 bit and got the “this kernel requires an x86-64 CPU, but only detects an i686 CPU, unable to boot” error. So I went into the host bios and enabled virtualization. I also recreated the .vbox file and between those two actions I somehow fixed the DHCP issue.
Interesting! I wouldn't think the 64-bit problem would be important to DHCP, maybe it is. I suspect something slightly wrong with the guest that was fixed by re-doing the .vbox file.