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.
Your feedback is much appreciated.
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.
Comments
SE Notebook
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
PING domain1.local on both computers and let us know the result.
All you said has already been checked, but I typed domain1 without .local and it accepted, but I want to know the reason it accepted domain1 and not accepting domain1.local.
The DNS suffix of both the server and client has domain1.local associated with the hostname.
Plans for 2010: MCITP:EA and CCNA
70-648 - Done
70-643 - In progress
70-647 - Still on my list
70-680 - Still on my list
www.coantech.com
www.thecoans.net
www.facebook.com/tylercoan
www.twitter.com/tylercoan
www.linkedin.com/users/tylercoan
-Always working on something...
-The RepAdmin Active Directory Blog
sometimes you can get away with just the name, others you need to add the extension. Something to do with DNS settings, but I'm not sure which ones.
STOP RIGHT NOW!!! This is a DNS issue and you are resolving the domain via netbios. There is something wrong and you need to figure it out.
If you proceded with something like this in a production environment you would be SOL in 6 mos when things start breaking and you cannot figure out why because the .local issue was forgotten.
You need to perform this lab properly. Check your zones in DNS and make sure you have all the required entries under _msdcs, etc. Try running NETDIAG /FIX to see if that helps.
Description of the Netdiag /fix Switch
I have personally had to redo the AD at 3 locations I can think of because the guy who installed it did so without DNS working properly.
I
+1
Has helped me out several times.
I've only used it in a lab environment. Basically it fixes any inconsistencies with DNS as it pertains to domains and domain controllers.