ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Windows Domain join issue

    Scheduled Pinned Locked Moved IT Discussion
    domain
    28 Posts 8 Posters 10.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • dbeatoD
      dbeato @notverypunny
      last edited by

      @notverypunny Users are the ones with the limit up to 10 but admins do not have a limit.

      1 Reply Last reply Reply Quote 1
      • dbeatoD
        dbeato @AdamF
        last edited by

        @fuznutz04 said in Windows Domain join issue:

        It's been forever since I have worked with Windows domains. But today, I have to join a Windows 10 PC to a domain. I keep getting the error:
        "The specified network name is no longer available."

        Primary DNS is set to the DC IP on the PC .
        Pinging domain name gets a reply from the DC IP as expected.

        I know this is something simple, but I am not finding it.

        Any ideas?

        What is the secondary DNS on the network card?

        AdamFA notverypunnyN 2 Replies Last reply Reply Quote 0
        • AdamFA
          AdamF @dbeato
          last edited by

          @dbeato The secondary DNS is another domain controller on the domain. (backup)

          1 Reply Last reply Reply Quote 0
          • notverypunnyN
            notverypunny @dbeato
            last edited by notverypunny

            @dbeato said in Windows Domain join issue:

            @fuznutz04 said in Windows Domain join issue:

            It's been forever since I have worked with Windows domains. But today, I have to join a Windows 10 PC to a domain. I keep getting the error:
            "The specified network name is no longer available."

            Primary DNS is set to the DC IP on the PC .
            Pinging domain name gets a reply from the DC IP as expected.

            I know this is something simple, but I am not finding it.

            Any ideas?

            What is the secondary DNS on the network card?

            ^^ This -- make sure that there isn't an external DNS as backup on the machine you're trying to add to the domain, even if the DC is the primary it'll bork on joining if there's anything external to the domain as secondary / tertiary etc

            AdamFA 1 Reply Last reply Reply Quote 0
            • AdamFA
              AdamF @notverypunny
              last edited by

              @notverypunny said in Windows Domain join issue:

              @dbeato said in Windows Domain join issue:

              @fuznutz04 said in Windows Domain join issue:

              It's been forever since I have worked with Windows domains. But today, I have to join a Windows 10 PC to a domain. I keep getting the error:
              "The specified network name is no longer available."

              Primary DNS is set to the DC IP on the PC .
              Pinging domain name gets a reply from the DC IP as expected.

              I know this is something simple, but I am not finding it.

              Any ideas?

              What is the secondary DNS on the network card?

              ^^ This -- make sure that there isn't an external DNS as backup on the machine you're trying to add to the domain, even if the DC is the primary it'll bork on joining if there's anything external to the domain as secondary / tertiary etc

              OK, no longer getting the original error message. (I had an external dns set as a secondary on the PC I am trying to join). Now, I am gettiing "The target account name is incorrect"

              dbeatoD 1 Reply Last reply Reply Quote 0
              • dbeatoD
                dbeato @AdamF
                last edited by

                @fuznutz04 said in Windows Domain join issue:

                he target account name is incorrect

                Anything on the event logs?

                1 Reply Last reply Reply Quote 0
                • AdamFA
                  AdamF
                  last edited by

                  Nothing that stands out for this. I am getting replication errors that I need to solve. (having issues replicating to this DC to my COLO DC, but I wouldn't think that this would cause issues with me joining a PC to the domain at this location.)

                  DashrenderD 1 Reply Last reply Reply Quote 0
                  • DashrenderD
                    Dashrender @AdamF
                    last edited by

                    @fuznutz04 said in Windows Domain join issue:

                    Nothing that stands out for this. I am getting replication errors that I need to solve. (having issues replicating to this DC to my COLO DC, but I wouldn't think that this would cause issues with me joining a PC to the domain at this location.)

                    Yeah, your PC had flipped DNS to the external one - so no surprise on the replication errors.

                    Target account name is incorrect - huh..
                    not sure what would be about...

                    notverypunnyN 1 Reply Last reply Reply Quote 0
                    • notverypunnyN
                      notverypunny @Dashrender
                      last edited by notverypunny

                      @Dashrender said in Windows Domain join issue:

                      @fuznutz04 said in Windows Domain join issue:

                      Nothing that stands out for this. I am getting replication errors that I need to solve. (having issues replicating to this DC to my COLO DC, but I wouldn't think that this would cause issues with me joining a PC to the domain at this location.)

                      Yeah, your PC had flipped DNS to the external one - so no surprise on the replication errors.

                      Target account name is incorrect - huh..
                      not sure what would be about...

                      Hate to be the bearer of bad news but you might have to fix AD first...

                      https://support.microsoft.com/en-ca/help/2183411/active-directory-replication-error-1396-logon-failure-the-target-accou

                      EDIT: just came across this:
                      https://atherbeg.com/2017/01/04/error-while-joining-machine-to-domain-logon-failure-the-target-account-name-is-incorrect/

                      1 Reply Last reply Reply Quote 1
                      • ObsolesceO
                        Obsolesce
                        last edited by

                        First try another PC or a VM to quickly be sure it's not just that device.

                        Then if same issue, start troubleshooting the DC.

                        1 Reply Last reply Reply Quote 0
                        • AdamFA
                          AdamF
                          last edited by

                          OK, we have success!

                          Steps to resolve:

                          1. On the DC I was having issues with at the main site, I stopped the KDC Service (Kerberos Key Distribution Center Service)

                          2. Then I ran this:

                          NETDOM RESETPWD /Server: <Domain Controller Name> /UserD:<Domain Admin Username> /PasswordD:<Domain Admin Password>
                          1. Rebooted the server.

                          After this, all of the strange event viewer errors in the DNS log, AD log, etc were gone. I can now successfully replicate across sites as well as join PCs to the domain. I'm not sure why this happened in the first place, but this fixed it.

                          Thanks for all the help!

                          1 Reply Last reply Reply Quote 3
                          • 1
                          • 2
                          • 2 / 2
                          • First post
                            Last post