Solved!
Go to SolutionD
DenverITSupport
2 Posts
0
2704
December 4th, 2017 08:00
ERROR_BAD_NET_NAME when attempting to join AD
When attempting to join our OneFS Cluster to an AD domain, the GUI and CLI return the error:
Your Active Directory provider was not created
Error #1: Failed to join domain 'contoso.COM' account 'hostname' user 'user@contoso.COM': ERROR_BAD_NET_NAME
I've verified that the cluster can do a SRV lookup for _ldap._tcp.contoso.com
Can't find any documentation on the ERROR_BAD_NET_NAME.
Some additional insight, the cluster was previously a member of the domain, but an admin mistakenly removed the membership via the OneFS GUI. I thought it might be related to the machine account existing in AD, so I've removed it to no avail. Any insight on the error would be appreciated.
DenverITSupport
2 Posts
2288
0
Posted December 6th, 2017 07:00
Phil Lam, thanks!
Yes, it turned out to be a DNS issue. We found in some of the debugs that an LDAP query response was returning a response host not in tree. I discovered that our _ldap._tcp.domain.com and _kerberos._tcp.domain.com dns entries had been changed. After correcting these DNS entries, we were successfully able to add the cluster back to the domain.
Phil.Lam
4 Apprentice
•
642 Posts
•
15 Points
2288
0
Posted December 5th, 2017 22:00
randyco
It's a Microsoft error.
System Error Codes (0-499) (Windows)
ERROR_BAD_NET_NAME
The network name cannot be found