virtualbox.org

Hi,

I have installed windows server 2012 r2 Domain Controller on my physical server, setup dns and dhcp with a scope, all seems well with the DC. On this server I have installed VirtualBox, and a new Windows 10 VM, The VM can connect to the Domain Controller, but dhcp isn't working, the VM wont get an IP address from the dhcp server. ipconfig wont show me the domain controller at all. I can however connect to the internet on the vm, and the DC can see the windows 10 vm. I have set the adapter setting to both NAT and bridged, neither seems to work. Am not sure if this is a Virtual Box problem, or a problem with my network configuration, but thought id check here for some advice, any guidance would be greatly appreciated, as I am very new to this. Thanks!

Bridged ought to work, if you are using a wired Ethernet adapter. Bridged doesn't always work with Wi-fi.

NAT behaves like a router. The guest can see the host & internet, but the host can't see the guest unless ports are opened.

See Virtualbox Networks: In Pictures

Set the Virtualbox network to Bridged, then run "ipconfig /all" in the host and guest, and post the text outputs of each command here in the forum, labeling which is which.

If you really want to run a domain of vms you should go about it just as you would set up a domain of physical machines. You should set them up in their own private network.

To emulate a domain environment, the best method is to to use an internal virtual network. See Internal Network in the guide Scott referred to. A Windows domain has special requirements, especially regarding DNS.

Hi scottgus1,

Thank you for the reply!, changed the vm network to bridged from NAT, and now its working, don't know why it didn't work first time round.

All the best,

Eden.

Hi BillG,

Have alot of reading to do with regards to vm's, thanks very much for the advice, have a great day!,

Eden.

Great! Glad you're up and running.