virtualbox.org

Hi guys,
'cause I am from Germany, I've cetain diificult to express myself. So, cut me some slack
My problem:
I just have installed Microsoft Server 2012 and a Windows 7 client. So, I think, that client is called 'host' in oracle virtual machine. Correct??
Furthermore, I tried to connect to internet the server, which only did well by using "NAT" in the networking settings. All the other network settings refuses internet connection. WHY??
My very ,very big problem:
I used to enter the host to the specific domain, organized by the server as domain controller.
Now,I'm not able to connect the host to internet, if I use 'network bridge' as network setting, although the server connects to internet.
Whenever I change the settings of the host to 'NAT', I'm able to connect to internet ,too, but unfortunately, I'm not able to enter the domain any more.
So, I decided to use servers' network setting to 'NAT' and clients network setting to 'network bridge'. Now, server is connected to internet, and client connected to the domain, but unfortunately not connected to internet. So, how do I have to cease network settings in Oracle Virtual Box, in order to enter the domain AND to connect to internet???
Big thanks ex ante for each post, which could help me!!
Try to describe settings both for the server and the client, please!

In VirtualBox terminology, the physical machine is the host and the virtual machines are guests.

The best way to run a Windows domain on VirtualBox is to install both the server and the client(s) as virtual machines running on the same host. You then configure AD just as you would on physical machines connected to the same hub/switch. Most of the configuration is the same in both cases, so use a guide to setting up AD on physical machines if you cannot find one for vms.

Put all the vms in the same internal network (this emulates the switch). Give them all static IPs in the same private network (or give the DC a private IP and configure DHCP to provide IPs to its clients). Configure all machines to use the DC as their DNS server. (This is essential for AD to work.) Forget about Internet access until you have your domain working.

For Internet access you need a router in both cases. For virtual machines, the router can be another virtual machine linking the private (domain) network to the physical network. Use a routing appliance like pfsense and configure it as a NAT router. You would bridge the "public" NIC of the router vm to the physical network and the "private" NIC to the internal network.

If you can't work out how to do this, post back when you get to this stage.