none
Error While Joining Domain. RRS feed

  • Question

  • Hello!

    Hope everyone is doing fine.

     

    Could someone assist whereas have received error on joining domain as "Network Could not be found". On joining the domain it prompts for UID and Password but on entering details, it goes in loop for some minutes and return with the above specified error.

    The ping response between the client and server is fine. And DNS is also configured for the specified zone.

     

    Thanks in advance.

    Cheer,

    Ahin


    Thanks! Ahin
    Saturday, September 10, 2011 6:34 AM

Answers

  • Hello,

    please make sure that the server is pointing to its private IP address as primary DNS server and 127.0.0.1 as secondary one.

    Once done, run ipconfig /registerdns and restart netlogon on the server.

    For the client computers, make sure that they are pointing to this server as primary DNS server and make sure that needed ports for authentication are not blocked: http://msmvps.com/blogs/rexiology/archive/2006/04/05/89389.aspx

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator

    • Marked as answer by Kevin Remde Monday, October 31, 2011 12:59 PM
    Saturday, September 10, 2011 7:26 AM

All replies

  • Hello,

    please make sure that the server is pointing to its private IP address as primary DNS server and 127.0.0.1 as secondary one.

    Once done, run ipconfig /registerdns and restart netlogon on the server.

    For the client computers, make sure that they are pointing to this server as primary DNS server and make sure that needed ports for authentication are not blocked: http://msmvps.com/blogs/rexiology/archive/2006/04/05/89389.aspx

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator

    • Marked as answer by Kevin Remde Monday, October 31, 2011 12:59 PM
    Saturday, September 10, 2011 7:26 AM
  • Thanks!

     

    This is the same reply i suggested for solution to one of my colleague and it had worked. It was more on port blocking between VLANs as both are two different remote networks.

    Just wanted to be doubly sure in-case there was any other procedures.


    Thanks! Ahin
    Saturday, September 10, 2011 9:40 AM