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
3 Apprentice
•
636 Posts
0
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
DenverITSupport
2 Posts
0
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.