Joining a VirtualBox VM to a Domain

[angrycomputingteacher]

I've downloaded the Creators Update and installed a VM for it in VirtualBox. I'm trying to connect it to my domain but I get this error.

I think it's something wrong with the Network settings so here they are if you need them. I'm using all of them and I still can't connect.

The VM has a dynamic IP and the server is static on 192.168.0.110. Not sure what I need to do to my VM to make it work.

[RJohnson91]

I've downloaded the Creators Update and installed a VM for it in VirtualBox. I'm trying to connect it to my domain but I get this error.

[ATTACH=CONFIG]42589[/ATTACH]

I think it's something wrong with the Network settings so here they are if you need them. I'm using all of them and I still can't connect.

[ATTACH=CONFIG]42590[/ATTACH]

The VM has a dynamic IP and the server is static on 192.168.0.110. Not sure what I need to do to my VM to make it work.

 

 

I've noticed you're only using "Mcclean", have you tried using the FQDN ?

 

Ryan

[angrycomputingteacher]

Yep. It displays another error.

When I ping it using it, it does not know it. However I can ping mcclean-dc.

[SHimmer45]

can you ping the server, is the VM client connected to a network switch/connection within Virtual box which will allow it to talk to the outside world (IE not just the computer it is hosted on) on Virtual box i believe this is "bridged network"

if you are using Private / Internal it wont talk onto your network via the Host network card

 

check your netbios and FQDN as well as it might be different to your DC's name

[angrycomputingteacher]

I can ping it by the domain controllers IP and host name (mcclean-dc).

[SHimmer45]

do you have netbios over tcpip enabled in your DHCP. (ignore if you join domain with the nebios name on none vmmachines)

which network adapter is assigned the guest machine you are trying to join to the domain

[angrycomputingteacher]

I've just changed the network settings to Bridged and nothing else. Still having issues.

[Jamo]

You need to be able to resolve the DNS name for the domain as well as the dc itself. Can you nslookup the domain name itself? Also try setting the DNS server to the same as the DC it may be that the DNS forwarder in VB isn't dealing with the SRV and other records that AD uses

[angrycomputingteacher]

I know I might sound stupid. But do I need the DNS Server installed on my Domain Controller?

[RJohnson91]

I know I might sound stupid. But do I need the DNS Server installed on my Domain Controller?

 

Only if you want devices on your network to see local DNS names, oh and it is to my knowledge devices need to query the DNS to join a domain...

 

 

[Guest MD5T]

Does sound like a DNS problem.

[SHimmer45]

I know I might sound stupid. But do I need the DNS Server installed on my Domain Controller?

as long as you have a DNS server on your network which has the correct entries for your domain controller it doesnt need to be on the DC

[Davit2005]

Active Directory relies on DNS, as long as the DNS can resolve the domain name then it should be no problem. Try pinging the domain by name and see what it returns. Edited April 10, 2017 by Davit2005

[MrKJLS]

Active Directory relies on DNS, as long as the DNS can resolve the domain name then it should be no problem. Try pinging the domain by name and see what it returns.

What happens if you try and change your DNS severs to your domain controllers?

[angrycomputingteacher]

I've managed to connect it to the domain by adding the DNS role on the Domain controller and setting the DNS server to the DC. Finally!