virtualbox.org

Hello I'm trying to create a host only network for my two servers in virtual box. I have a windows 2012 server with the Active directory and DNS server roles and a second one just as a standalone server. When I created a new host only network adapter and I look at the adapter itself on my local machine , it is showing enabled but "not network access" then I have my local adapter which is connected. I was wondering if there are any requirements for my local machine which is a Lenovo Z370 which has a Realtek PCIe FE Family controller Adapter. I assume if the adapter is not connecting to internet locally...when I change the adapter to manual IP on IPV4 it wont make any changes. I tried that and in the server it self it shows as not connected. Would you have any suggestions or is my NIC card not supporting having multiple adapters connected to the same network? I have already isolated the issue is the new created adapter within Virtual box. When I disable this adapted and let the local adapter take place, intern resumes. Thanks!

Host Only does not reach out to the internet. It is, wait for it... "Host Only".
Host Only is a private network between the host OS and any guests attached to it. See Virtualbox Networks: In Pictures: Host-Only Adapter.

If you want to have a private internet-connected network for the guests to play with AD & such, see "Sandbox" in the tutorial above.

Why would you ever have multiple adapters connected to the same network (physical or virtual)? It makes no sense whatever (unless they are bridged to increase throughput).

Active Directory is very fussy about its networking. All machines in the domain should have one adapter only and need to use the local DNS server (on the DC) for AD to work properly. That rules out using NAT for Internet access (unless you manually change the DNS settings). A Scott said, Host Only never gives you Internet access. It doesn't even give you access to your local LAN (if the host is on a LAN.)

I always set up domain machines in their own local private network using the DNS server on the DC. For vms, that means using an internal virtual network. You also need to set up a virtual router for Internet access for the domain.

It is possible to use a NAT network for a domain, but it requires manually changing the DNS setting (because NAT will give them Internet access but the wrong DNS address for a domain to work). The DC should always have a static address.

If you want your standalone server to be able to communicate with the DC, put it in the same network and put it in a workgroup with the same name as your domain(without the extension at the end). For it to have Internet, you need to set it just as you do the domain members - same subnet and mask, same gateway and same DNS address (the IP of your DC).