Unable to join pc to doamin.

Hi,
I am going through the labs of MS press book, In Chapter 5 "Implementing a Network Infrastructure". on exercise 1 of Lesson 1, I have installed Active Directory on Computer1 but couldnt join computer2 into domain1.local as explained in Execrise 3.

Computer1 has the following roles installed: DNS, Domain Controller, with static IP address of 192.168.0.1/24.

Comments

Make sure you have dns suffix on client pc (if DHCP is not providing it), also ensure the client pc has the DNS servers IP in its TCP/IP config. Also and I'm guessing you have already done this, check connectivity between client and DC

There is a file in the system32 folder on the client machine (I believe it is netsetup.log) it will contain all the messages of your client trying to join to the domain and you can see exactly where it is failing out.

Hi,
I am going through the labs of MS press book, In Chapter 5 "Implementing a Network Infrastructure". on exercise 1 of Lesson 1, I have installed Active Directory on Computer1 but couldnt join computer2 into domain1.local as explained in Execrise 3.

Computer1 has the following roles installed: DNS, Domain Controller, with static IP address of 192.168.0.1/24.

Your feedback is much appreciated.

2 most common errors:

1. When you run IPCONFIG /ALL on PC1 is the DNS server entry set to 127.0.0.1 or to its own IP address?

2. When you run IPCONFIG /ALL on Computer2 is the DNS server entry set to the IP address of Computer1?

If the answer to either of these is "no" then fix that and try again. If the answer to both of these questions is yes then please run

I don't believe I have used this command before. I will have to give it a try sometime. Can anyone elaborate on how it works? The KB wasn't very descriptive.

I've only used it in a lab environment. Basically it fixes any inconsistencies with DNS as it pertains to domains and domain controllers.

Netdiag /fix switch is very useful tool to correct issues with DNS and domain controller tests. 1. DNS Test: If the computer is a domain controller, Netdiag verifies all the DNS entries in the Netlogon.dns file to determine if they are correct and updates the appropriate entries if there is a problem. 2. Domain Controller Test: If the domain GUID cached in a local computer on your primary domain is different than the domain GUID saved in a domain controller, Netdiag tries to update the domain GUID on the local computer.