Unable to join a Domain

The only DNS server that should be configured on a Windows domain should be the DNS server hosting the domain, and if you've only got one server it should have DNS installed and configured on the domain controller. Using ISP DNS servers instead of the DNS server on the DC will cause your machines to not be able to find the domain controller.

Generally, when I set up a small domain, I install DHCP and DNS on the server to be the first domain controller, then install active directory. Once complete (it will configure DNS automatically during dcpromo), I configure a DHCP scope and options to be assigned via the DHCP management snap-in, authorize the DHCP server, and deactivate any other DHCP servers I might have on the network (home routers, etc). That way, all machines will get a DHCP address from the DC, and the options should only have the DC's IP address configured as the DNS/Name server. Things will work best that way.

Rick10 said:

I am running a windows server 2008 R2 server on a virtual machine (VM Ware) that is a domain controller running ADDS. I plan to connect my windows 7 Ultimate PC (which is installed on the Hard drive not on a virtual machine) to the W2K8 DC. I insist on doing this without the use of a router. The W2K8 computer receives dynamic updates directly from the ISP. On trying to join the Win 7 pc to the W2K8 DC, I receive the following error:Computer unable to find the Active Directory Domain Controller.
I do know that I need to change the DNS address of the client which should match that of the Domain Controller. But I want to know if this setup is possible without the use of router where the server receives IP address dynamically.
Could anyone help me on this??:)

As cluberti said, In order to provide the best compatibility you should add the DHCP service in server manager and then configure your home router (if enabling internet connectivity) so that DHCP is turned off. You should only have one DHCP service per network. When setting up you need to set the primary DNS as the Active Directory server itself and the secondary DNS as your router for internet connectivity.

If you have not done so, make sure that the DC has a static IP address stack and that the primary DNS server is set as its own IP address.

Josh

If the vm is attached directly to your network (no bridging or NATing being done), then yes.