virtualbox.org

Hello,

I am new here and somewhat new to VB and VMs. Last couple of weeks I have been trying different stuff and reading about VB.

Now, I have taken myself a task to build following:

- 3 Server VMs based on WinSrv2008R2, one for Domain Controller, one RDSH and one File Server
- 2 Clients based on Win7Prof/Ent
- the Virtualbox-Networking which is basically isolated from the rest of my network, BUT still has internet access

I am also kinda new to networking, so sorry if I ask stupid questions.

In a real world, I would set up the DC, set it to fixed IP, set the DHCP and DNS and be on my merry way. That is, if DC is still in the same network. If I wanted DC to be on a different network, I guess I would put it in a different subnet or VLAN?

What I want is following:
- I have a home network setup with the DHCP, DNS and all that, working normally - I want to keep that, without having any conflicts!
- now I want to set up a VM with a DC, which should but act as DC only for the Virtualbox-Network, not outside the Virtualbox (I guess the best setting would be intnet, to isolate the network), but:
- I also want a DC getting internet connection, so I can have internet on my whole network

Ultimately, my problem is, how to set up a DC on my existing home network, which has a SOHO router running in a typical 192.168.1.1, so that the DC only "acts" for the Virtualbox-Network, but still has internet and also provides DHCP and DNS for the VB-Network? What network card(s) do I need to enable and what IP? I tried couple of things but never could wrap my head around it...

Thanks a lot!
Kosta

The easiest and for most the best way to use and test Windows domains in VirtualBox
Setup Windows Domain in VirtualBox

Isn't there a way to do it without ics? VB offers so many options, I was under impression it must be possible by maybe using two adapters or something...?

Sure there is but this is by far the best.

Especially if you want it to be a functional Domain without going to the trouble of setting up a multi-homed network.
But that being said the only thing that VirtualBox really does is provide Virtual Hardware. Setup and config. are out of the scope.

And of course you can run a domain on an internal network without ICS/NAT if you don't need Internet access for the domain machines, but most people are not interested in doing that.

Even with physical machines you need NAT to run a useful domain. The domain runs on a private network and needs NAT for Internet access. There are a few other things you need to do to get a domain running successfully with Internet access (mainly to do with DNS) whether you use physical or virtual machines. These are Windows domain questions, not VirtualBox ones.

I took a shot at pfSense today evening, and I must say, thank you for the great advice! Probably the exact thing I was looking for! Very nice virtual router/fw.

Perryg wrote:The easiest and for most the best way to use and test Windows domains in VirtualBox

thanks. I am looking for this.