i am Building up an test environment in virtualbox that works as an active directory and domain controller.

My problem is that I can’t connect to the domain controller from another computer (virtualbox computer on same machine) and can’t install windows updates on the server. (later in this text I will set the error code when trying to join domain)

Here is my network setting on virtualbox (I have also put my static ip address in the windows server 2008 behind this adapter 4): “see adapter4.jpg for more information”

The problem I see here is that SERVER01 and DESKTOP101 are on two different networks. Check the IP configuration for each in your VBox settings and make sure that both machines will be on the same subnet.

Something that i probably good to mention now is that I travel between 2 to 3 location with my laptop and which why I using wlan when I plugged in to the internet, this should probably don’t matter when building a local computer test domain network that has 1 computer in the domain.

By the way here is my roles and features that are installed on my windows server 2008:

I mentioned earlier that I was trying to join the virtual machine windows 8 to my domain but I think the problem I am having that I have wrong configured the domain controller/virtualbox.
Still I am going to type in here the error message I get when trying to join the domain.
[quote]“
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "contoso.com":

The error was: "This operation returned because the timeout period expired."
(error code 0x000005B4 ERROR_TIMEOUT)

The query was for the SRV record for _ldap._tcp.dc._msdcs.contoso.com

The DNS servers used by this computer for name resolution are not responding. This computer is configured to use DNS servers with the following IP addresses:

10.0.0.11

Verify that this computer is connected to the network, that these are the correct DNS server IP addresses, and that at least one of the DNS servers is running. [/quote]

Hopefully I have provide all the required information of my problem if something is missing don’t hesitate to ask, and I will provide more. Thanks in advance for the help

The problem here seems that your Windows 8 box is not seeing the network. The WU error (8024402C) and the issue with not finding the relevant SRV record is that you can't get to the 'right' network. Some things to try.

1. From CMD or PowerShell: type IPCONFIG /ALL - what output do you get? does it seem like there's a network configured at all?

2. From the CMD Prompt, try pinging the DNS Server that is configured and you can see in step 1.

3. Repeat this from the DC - and compare.

Consider posting the outputs form these steps for 2nd opinions...

Before Windows 8 came around, with Hyper-V, I used Virtual Box a lot and managed to do just what you are trying to do, so I know it works!!

Host-Only will not allow your VirtualBox guest to access the network - it will only allow it to communicated with the host.

Bridged will place your VirtualBox guest on the same network as the adapter you are binding it to. So, if your host is configured as 111.222.33.44, the VirtualBox guest will be IP 111.222.33.xx and act as though it was a physical host on your network.

NAT will give your VirtualBox guest an address of 10.x.0.y, where 'x' is the adapter number on the virtual host, starting at 2. A VBox host with NAT networking can access anything its physical host can access, BUT nothing can access the VBox host. A guest with NAT can surf the web and even access your company's network - but unless you set up port forwarding nothing can contact the virtual box.

I think the reason you can't join a domain is because the DC can't contact the virtual host. You may need to change the networking to bridged to place the virtual host on the same network as your domain.

In order for two VirtualBox VMs to talk to eachother, you'll need to do one of the following.

1) Host-Only Network: First, from the File menu in VirtualBox, you'll need to open Network and add at least on Host Only Network. Each Host Only network is kinda like a "virtual" VLAN. Machines connected to the same host-only network will be able to talk to eachother (and the host) as would machines on the same VLAN. Normal IP addressing rules still apply, though, the host, and the VMs need to have IP addresses in the same subnet. The host will provide DHCP addresses. Once the Host-Only network is added, you'll need to configure each of the VMs (server and client) to have a host-only network adapter, check the "Cable Connected" box, and select the new host-only network from the drop down. I believe access to the outside world is possible - contingent upon the host's firewall settings.

2) Internal Network: Simple, configure the Internal Network, and then ensure that both VMs are using the same Internal network name. No traffic will leave the host....ever. If you do this, give up any dreams of Windows Updates and internet access from the guests.

3) NAT: Simple. VMs can talk to eachother and the host acts as a rudimentary firewall providing basic NATing from the guest network to the network the Host resides. External and Internet access are possible - again contingent upon the host's firewal settings.

4) Bridged Mode: VMs and the host "share" the host's physical network adapter. All of them reside on the same network with the rest of the host's LAN. Other machines on the LAN can see the VMs and vice-versa (provided you let them obtain the address through DHCP). You can configure a separate address space for the two VMs, but they won't be able to access the network/internet if you have a separate namespace, unless you are multi-homed. In this case, the host's firewall settings may not actually matter (been a while, don't remember).

My recommendation? If you want internet access and want to keep your test/development network separate from production, the easiest method is to set both adapters to NAT.

I think the reason you can't join a domain is because the DC can't contact the virtual host. You may need to change the networking to bridged to place the virtual host on the same network as your domain.

I think OP is trying to join a second VM to the vDC's domain; not trying to join the host.

I think the reason you can't join a domain is because the DC can't contact the virtual host. You may need to change the networking to bridged to place the virtual host on the same network as your domain.

I think OP is trying to join a second VM to the vDC's domain; not trying to join the host.

And so it would seem. Thanks for pointing that out. I think that's why I missed the Cable Connected setting. I was stuck thinking it couldn't connect to a DC outside the VBox host.

The problem I see here is that SERVER01 and DESKTOP101 are on two different networks. Check the IP configuration for each in your VBox settings and make sure that both machines will be on the same subnet.

vDC: 10.0.0.11/24 -> Change this to 10.0.2.11, change the DNS to point to 10.0.2.11. if you've got the right type of network setup, change the gateway to 10.0.2.2, and you'll be able to access the internet

The problem I see here is that SERVER01 and DESKTOP101 are on two different networks. Check the IP configuration for each in your VBox settings and make sure that both machines will be on the same subnet.

The problem I see here is that SERVER01 and DESKTOP101 are on two different networks. Check the IP configuration for each in your VBox settings and make sure that both machines will be on the same subnet.

As you have it, SERVER01 is 10.0.0.11/24 and DESKTOP101 is 10.0.2.15.

Damn it, I thought I hit refresh before I sent mine.

Not a contest. I save that for "special" people on this thing. Sadly, there's a lot of those ;)

Sal8273 and Semicolon thanks for the help, the problem was that it was not in the same network both machines witch why it didin’t work. Thanks for pointing out to the right direction.

I was using earlier in virtualbox for windows 8 the nat setting and the ip was 10.0.2.15. I tried changing the ip address for 10.0.2.11 and dns, tried connecting to the domain but it was not again able because I was not in the same subnet.

So the next thing I did was change the virtualbox network settings for dc server, for Bridget adapter “Intel pro/1000 MT server” after this i run ipconfig /all and I noticed that I was in the network 192.168.0.18 and understood immediately that it’s not again in the same network.

So I changed the virtualbox network settings for the win 8 machine using bridget adapter “Intel Pro 1000 MT server”. Started up the virtual machine and run ipconfig /all the ip was 192.168.0.17 finally in the same network both machines.

Next thing I put the static ip for dc 192.168.0.18, subnet 255.255.255.0 default gateway 192.168.0.1 and the dns server 192.168.0.18.

Next thing I tried pinging the server for win 8 finally and answer, the next thing I did change the dns settings in the win 8 machine for 192.168.0.18, after this tried connecting to the domain and didin’t have problems finding the domain. Happily connected to the domain and started using it.

Thanks again for sal8273 and semicolon for pointing me out to the right direction of my problem.