Domain Join failure RRS feed

  • Question

  • Hellow,

    When I try to join client machines to domain,  it shows the network path was not found.

    Please help me in solving the issue.

    What I have done already are as follows:

    1.Checked the DNS address in the adapter settings.It is found ok.

    2.I had done hardening sometime back. After that same thing is happening in joining the AD.

    • Edited by Ajoy_Assa Thursday, July 27, 2017 8:18 AM
    Thursday, July 27, 2017 8:17 AM

All replies

  • Hi, are you able to ping your domain name from your client machine? Is there local firewall enable? check if it blocking AD ports.
    Thursday, July 27, 2017 8:20 AM
  • Hi, aure youble able to resolve this domain ?

    • nslookup toto.lab
    • ping toto.lab


    Thursday, July 27, 2017 8:27 AM
  • Yup. 

    I can ping the AD and client machines vice versa. Local firewall is also off.

    Friday, July 28, 2017 8:51 AM
  • Nope.

    • nslookup toto.lab
    • ping toto.lab

    It shows DNS reqquest time out . It shows my DNS name when nslook command is executed.

    • Edited by Ajoy_Assa Friday, July 28, 2017 9:01 AM
    Friday, July 28, 2017 8:51 AM
  • Hello,

    • Do you have setup DNS address in the adapter(Active directory) on your computer ?
    • Your domain name is correct ? 

    Friday, July 28, 2017 10:52 AM
  • Hi, Is it just one computer or you see this issue in multiple clients? can you rename computer name and try to join domain again?
    Friday, July 28, 2017 11:35 AM
  • did it work?
    Monday, July 31, 2017 1:09 PM
  • Hi, Mr. Manoj,

    Computer name can be changed and it happens in all client machines, not in single machine. One more thing is that if we connect the DNS server and the clients pc's in a single hob(not switch), then it is able to join the clients in the domain.

    But the problem is still not rectified. We think that there is some issue at the switch level. Because we did hardening at the time of "Wanna Cry" attack.



    Tuesday, August 1, 2017 6:49 AM
  • Hi Ajoy

    You would need below firewall ports opened between domain controllers and client machine. Please check these are blocked. You can use PortQuery utility to test.

    LDAP TCP-in - 389
    LDAP UDP in - 389
    LDAP for Global Catalog TCP in - 3268
    NetBIOS name Resolution UDP in - 138
    SAM/LSA TCP in - 445
    SAM/LSA UDP in - 445
    Secure LDAP TCP in -  636
    Secure LDAP for Global Catalog TCP in - 3269
    W32Time NTP UDP in - 123
    RPC - RPC Dynamic
    RPC Endpoint Mapper
    DNS - TCP and UDP 53
    Kerberos V5 UDP in - 88
    Netbios Datagram UDP in - 137

    Thursday, August 10, 2017 8:17 AM
  • Please mark as answered if provided information helped you.
    Monday, August 14, 2017 5:55 PM