+ Reply to Thread
Results 1 to 13 of 13
  1. Member
    Join Date
    Oct 2008
    Posts
    63

    Certifications
    CompTIA A+, N+, MCP 270, 290
    #1

    Default 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.
    Reply With Quote Quote  

  2. SS -->
  3. Solutions Architect gateway's Avatar
    Join Date
    May 2010
    Location
    Manchester, UK
    Posts
    232

    Certifications
    MCITP:EDA7, EDST7, MCSA 2003, MCSA Windows 7 NetApp NCDA-7 Mode VCP5-DCV, VCP6-DCV ITILv3-Foundation, ITILv3-Intermediate-OSA, AWS CSA
    #2
    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
    Reply With Quote Quote  

  4. Security Nut NightShade03's Avatar
    Join Date
    Mar 2009
    Location
    New York
    Posts
    1,379

    Certifications
    RHCSA, JNCIA-Junos, CCNA, CCENT, MCSA (2K3), MCP, Security+, Network+, A+
    #3
    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.
    Reply With Quote Quote  

  5. BOBBY_TABLES RobertKaucher's Avatar
    Join Date
    Dec 2007
    Location
    Lebanon, Ohio - USA
    Posts
    4,274

    Certifications
    MCSD Web Apps/SharePoint Applications, MCITP: DBA 2005/2008, EA, EDA7, Linux+, Sec+, MCSE, MCDST, MCTS
    #4
    Quote Originally Posted by dfjama View Post
    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

    PING domain1.local on both computers and let us know the result.
    Reply With Quote Quote  

  6. Member
    Join Date
    Oct 2008
    Posts
    63

    Certifications
    CompTIA A+, N+, MCP 270, 290
    #5

    Default Got it right

    Thanks Gateway...

    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.
    Reply With Quote Quote  

  7. 1337 H@X0R subl1m1nal's Avatar
    Join Date
    Jan 2009
    Location
    Iowa
    Posts
    177

    Certifications
    MCSA, STS, Security+, Net+, A+
    #6
    I've ran into that issue before too. I'm not sure what the cause of it is.
    Reply With Quote Quote  

  8. No Title:)
    Join Date
    Jul 2009
    Location
    San Diego, CA USA
    Posts
    189

    Certifications
    MCSE: DI, MCSE: PC; MCITP: EA + SA + VA + Dynamics CRM; MCBSP; MCTS: Hyper-V, SCCM, SCOM, SCVMM, SCDPM, Vista, 2008; MCDST; MCSA 2012
    #7
    I would recommend reviewing your DNS settings. And always make sure the client is using the DC as its primary DNS. And check out those logs mentioned earlier
    Reply With Quote Quote  

  9. Senior Member Devilsbane's Avatar
    Join Date
    Apr 2010
    Posts
    4,203

    Certifications
    MCSE:Security, MCDST, A+, Network+, Security+, ITIL V3 Foundations, ITIL 2011 Intermediate: Service Transition, MOS 2007 (MCAS) BAS Computer Forensics
    #8
    Quote Originally Posted by dfjama View Post
    Thanks Gateway...

    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.
    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.
    Reply With Quote Quote  

  10. BOBBY_TABLES RobertKaucher's Avatar
    Join Date
    Dec 2007
    Location
    Lebanon, Ohio - USA
    Posts
    4,274

    Certifications
    MCSD Web Apps/SharePoint Applications, MCITP: DBA 2005/2008, EA, EDA7, Linux+, Sec+, MCSE, MCDST, MCTS
    #9
    Quote Originally Posted by dfjama View Post
    Thanks Gateway...

    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.
    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.
    Reply With Quote Quote  

  11. Go ping yourself... phoeneous's Avatar
    Join Date
    Dec 2008
    Location
    Console.WriteLine("Yo");
    Posts
    2,316

    Certifications
    Pimp status
    #10
    Quote Originally Posted by RobertKaucher View Post
    NETDIAG /FIX
    I <3 that command
    Reply With Quote Quote  

  12. Solutions Architect gateway's Avatar
    Join Date
    May 2010
    Location
    Manchester, UK
    Posts
    232

    Certifications
    MCITP:EDA7, EDST7, MCSA 2003, MCSA Windows 7 NetApp NCDA-7 Mode VCP5-DCV, VCP6-DCV ITILv3-Foundation, ITILv3-Intermediate-OSA, AWS CSA
    #11
    Quote Originally Posted by RobertKaucher View Post
    Try running NETDIAG /FIX to see if that helps.
    +1
    Has helped me out several times.
    Reply With Quote Quote  

  13. Senior Member Devilsbane's Avatar
    Join Date
    Apr 2010
    Posts
    4,203

    Certifications
    MCSE:Security, MCDST, A+, Network+, Security+, ITIL V3 Foundations, ITIL 2011 Intermediate: Service Transition, MOS 2007 (MCAS) BAS Computer Forensics
    #12
    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.
    Reply With Quote Quote  

  14. Go ping yourself... phoeneous's Avatar
    Join Date
    Dec 2008
    Location
    Console.WriteLine("Yo");
    Posts
    2,316

    Certifications
    Pimp status
    #13
    Quote Originally Posted by Devilsbane View Post
    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.
    Reply With Quote Quote  

+ Reply to Thread

Social Networking & Bookmarks