Windows Server 2012 & VirtualBox

November 24, 2015 at 18:49:06
Specs: Windows 10, Intel Xeon E5420 | 8GB DDR3 ECC
I'm sure many have posted concerning this issue, but I'm using VirtualBox for my server, and have set it's IPv4 address to, and it's default gateway to I've bridged my network connection through Settings of VirtualBox; I've restarted the server and activated the scope of addresses to hand out.

The host machine workstation/Windows/client-side (same machine hosting the Server 2012 installation) is not pulling an IP from the DHCP server. The VirtualBox network adapter has an auto-configured IP address of 169.etc.etc.. I also have another workstation machine connected to the same switch as the server, and it also is not pulling IP addresses (same auto-resolved 169 address). The switch is not connected to any networks or the internet; it's simply connecting the server and the workstation together.

Do I need to set a static IP and other settings for the VirtualBox virtualized network adapter? Beforehand, the adapter was set to NAT in VirtualBox, but I've switched this to Bridged and pointed to the main Ethernet network controller appropriately.

Any help would be greatly appreciated from anyone, thank you!

Grand Commander
(712) 335-7123

See More: Windows Server 2012 & VirtualBox

Report •

November 24, 2015 at 19:33:31
In the host network adapter TCP properties, did you add/activate the virtualbox network adapter?
When bridged, the clients will get IP address form the router/modem DHCP IP pool.
When set to NAT, the host will act as a DHCP server and router. This means there need to be services running to make this work.

Report •

November 24, 2015 at 19:37:06
Sluc, thanks for your response. I've got the DHCP server running, with DNS setup as well. The DHCP server has a scope of for addresses to be handed out.

I've bridged the network adapter, but on the workstation-side (Win10 client) the Virtualbox network adapter is only obtaining an auto-configured address of 169.x.x.x... the server side is picking up an IP address no problem from the DHCP server, because it can see the domain. The workstation/Win10-side cannot see the domain.

Concerning the network adapter TCP properties, are you talking about the TCP/IP protocol settings from within the network adapter properties window?

Grand Commander
(712) 335-7123

message edited by TheWaNGeR

Report •

November 24, 2015 at 23:51:35
I'm confused as to which of the computers that you are referring to are real computers and which are VMs. Would it be possible to give a few more details - all the computers involved, host and VMS, the way that IP addresses are assigned on each of them, any DCHP servers on your network other than the Windows server. Is a router involved at all? And which device have you assigned the address to (your default gateway).

I get the impression that you have a host computer with the DHCP server running in a VM on it. You have configured the host to get an address from the server via DHCP. Is this correct? If so, it's not going to work. The host obtains it's address when it boots, before the VM and DHCP server are running so, without another DHCP server, the only address it can assign is one of the 169.x.x.x auto-configured ones.

Correct me if I am mistaken.

Report •

Related Solutions

Ask Question