Windows Domain join issue
-
Oh, I am attempting to join with domain admin account as well.
-
anything in the event logs?
-
@pirho99 said in Windows Domain join issue:
You may have to install the SMB v1 client - Control Panel -> Programs --> Turn Windows Features on or off --> SMB 1.0....and SMB 1.0 Auto Removal if SMB 1 isn't used for 15? days
You don't need to do that to join to a domain...
-
@Dashrender said in Windows Domain join issue:
@pirho99 's post makes me think... what version of Windows 10?
I noticed my recent install of 2004 has SMB v1 disabled, 1909 does not.
SMBv1 has nothing to do with joining to a domain...
-
@Dashrender said in Windows Domain join issue:
@IRJ said in Windows Domain join issue:
Is that DNS name already joined?
I would slightly change the DNS name, reboot, and try to join again.
never had that be a problem before - it just steals the slot, but then again, I'm using a domain admin account to do the join, if he's not, that could be the issue.
It's an AD issue that dates back to 2000 and maybe NT4. I figure it may have been resolved by now, but I remember having to slightly change PC names to get them to join in the old days, especially on the the tech side without access to remove duplicate entries.
-
@dbeato said in Windows Domain join issue:
@Dashrender said in Windows Domain join issue:
@pirho99 's post makes me think... what version of Windows 10?
I noticed my recent install of 2004 has SMB v1 disabled, 1909 does not.
SMBv1 has nothing to do with joining to a domain...
I wouldn't have thought so, but meh.. just checking
-
Has that admin account perhaps hit the threshold of allowed domain joins? There are a few ways to get around it if that's the case.
.... Googling really quickly leads me too believe that it should actually tell you if this is the case, but I'll leave this here just in case M$ is being difficult again...
-
@notverypunny Users are the ones with the limit up to 10 but admins do not have a limit.
-
@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?
-
@dbeato The secondary DNS is another domain controller on the domain. (backup)
-
@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
-
@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"
-
@fuznutz04 said in Windows Domain join issue:
he target account name is incorrect
Anything on the event logs?
-
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.)
-
@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... -
@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...
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/ -
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.
-
OK, we have success!
Steps to resolve:
-
On the DC I was having issues with at the main site, I stopped the KDC Service (Kerberos Key Distribution Center Service)
-
Then I ran this:
NETDOM RESETPWD /Server: <Domain Controller Name> /UserD:<Domain Admin Username> /PasswordD:<Domain Admin Password>- 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!
-
