Windows server 2008 join domain

Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page. After receiving the same replies from all domain controllers located using DNS, it falls back to performing a NetBIOS name query for the FQDN domain name to locate a domain controller, however this gets no response and the join operation fails.

However it receives no adequate response and fails with the second error. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. After restart we have the option to log on to the domain, and if you go in the Server Configuration menu you can see the domain name instead of the workgroup. Your email address will not be published. Notify me of followup comments via e-mail.

Want content like this delivered right to your email inbox? You may want to put a fixed IP address on that server, too. Let's do that for this example, and say you give it the address of In other words, primary DNS would be Alternatively, you could set up your router to hand out DHCP addresses in the It's your choice.

That means you don't have to manually configure every single server you put up. There are trade offs to each method, but I'm not going to get into that.

Join this new machine to your domain. Now you can continue this process for as many servers as you want. The key to this whole thing is that you need to set up a DNS so that you have the ability to get the machines in your domain registered into the DNS. It sounds like you don't have your DNS defined correctly. The error message is telling you that the DNS server that the second machine is pointing at does not know of your domain controller.

How do you have DNS defined on both of these systems? How did you define DNS for the domain when you built it? The first one Domain controller in that one there is no Dns configuration.

I set it as automatic dns configuration in network connections ipv4. In the second one also i. I tried by putting manual dns configuration which is given by My ISP people. Even though no use. Run: netsh int ipv4 set dns "Local Area Connection" static " However, in case your DC is not pointing to itself for some reason..

If you did not install DNS in your first domain controller Unless you made some sort of previous arrangement with your ISP, I doubt very much that his DNS would be configured in a way that would support you putting Active Directory onto it. You may want to do a bit of reading to understand how to set up a Domain within Active Directory.

It can be a bit overwhelming, because there is a lot of information that should be known before you start building a domain. Once you understand it, it is pretty simple, but there are some basics, such as setting up the right DNS environment, that you need to understand first. There are several documents at that link that should help you get started. May know how to join in the domain. Also, please run the following command on your first domain controller and share its output.

I got the same output in the first domain controller and also inthe second one and also windows xp also. Dns servers Your command included unnecessary quotemarks and used the dns instead of dnsserver commands. By look up purposes only, I mean that the ISP provides a way for you to look up things on the internet, but it does not provide any DNS service within your local environment.