topic Re: CIFS Server - Failed to join AD in Simulator Discussions

CIFS Server - Failed to join AD

MarkTayler — Wed, 04 Jun 2025 20:23:15 GMT

I am using the 8.3 Simulator in VMware 6

Configuration:

Cluster Name: cluster1

Node1 Name: node01 (cluster1-01)
Node Mgmt Port: e0c, 192.168.1.140, 255.255.255.0

Cluster Mgmt Port e0d, 192.168.1.160

Node2 name: node02 (cluster1-02)
Node mgmt Port: e0c 192.168.1.141, 255.255.255.0

SVM running on cluster1-01, e0c, 192.168.1.150

Windows 2012 Server: win2012s01: 192.168.1.131

DNS Server: domain mtlab.local

AD Controller: domain MTLAB

Ubuntu Machine (not VM) 192168.1.103

NTP time server

1) All IPs are pingable from all devices

2) Win 2012 nslookup works both forward and reverse

3) Nodes: name resolution works

4) All servers/nodes times are within a few seconds of each other

From cluster1-01 I run the command

cifs create -vserver itsusrasvm01 -cifs-server itsusrasvm01 -domain MTLAB -ou Computers

I am prompted for the credentials

I receive this message

Error: Machine account creation procedure failed
[ 0 ms] Trying to create machine account 'ITSUSRASVM01' in domain
'MTLAB' for Vserver 'itsusrasvm01'

[ 31058] Failed to connect to 192.168.1.131 for DNS: Operation timed out
**[ 31059] FAILURE: Failed to find a domain controller

[ 31059] Uncaptured failure while creating server account

Error: command failed: Failed to create the Active Directory machine account "ITSUSRASVM01". Reason: invalid
Pointer.

I am at a loss

Thanks for answers in advanced

Re: CIFS Server - Failed to join AD

MarkTayler — Thu, 16 Jun 2016 04:27:31 GMT

So it looks like my DNS config for AD is not right.

Did some research and made some changes.

Added the _msdcs stuff in DNS, now I am further along but not finished.

I know this is a DNS - AD thing, if someone can help, would apprecate it.

Here is the error message after running the command.

cluster1::vserver services name-service dns> cifs server create -vserver itsusrasvm01 -cifs-server itsusrasvm01 -domain mtlab.local -ou Computers

Error: Machine account creation procedure failed
[ 0 ms] Trying to create machine account 'ITSUSRASVM01' in domain
'MTLAB.LOCAL' for Vserver 'itsusrasvm01'
[ 9] Entry found for host-name: win2012s01.mtlab.local using
source: DNS
[ 9] Found 1 domain controllers through DNS
[ 13] Failed to initiate Kerberos authentication. Trying NTLM.
[ 15] Successfully connected to 192.168.1.131:389 using TCP
**[ 30] FAILURE: 'NisDomain' configuration not available
[ 30] NIS configuration not found for Vserver 7
[ 42] Entry found for host-name: win2012s01.mtlab.local using
source: DNS
[ 54] Entry found for host-name: win2012s01.mtlab.local using
source: DNS
[ 64] No servers found in DNS lookup for
_ldap._tcp.Default-First-Site-Name._sites.MTLAB.LOCAL.
[ 76] No servers found in DNS lookup for _ldap._tcp.MTLAB.LOCAL.
[ 85] No servers found in DNS lookup for
_kerberos._tcp.Default-First-Site-Name._sites.MTLAB.LOCAL.

[ 95] No servers found in DNS lookup for
_kerberos._tcp.MTLAB.LOCAL.
[ 97] 'CifsServerSecurity' configuration not available
[ 97] No servers available for MS_LDAP_AD, vserver: 7, domain:
MTLAB.LOCAL.
[ 97] Failed to find a domain controller
[ 97] Uncaptured failure while creating server account

Error: command failed: Failed to create the Active Directory machine account
"ITSUSRASVM01". Reason: SecD Error: no server available.

Thanks,

Mark Tayler

Re: CIFS Server - Failed to join AD

rymcc86 — Thu, 16 Jun 2016 06:52:18 GMT

Hi Mark,

This is looking very much like the filer cannot see the DNS server which you are specifying, from the cluster shell have you attempted to ping the IP of each DNS server?

You can do so using the Network Ping command and you may also find the Network Traceroute helpful in your diagnosis of this issue, details on those commands can be found on pages 266-267 of the below guide.

https://library.netapp.com/ecm/ecm_download_file/ECMP1196817

Assuming that all checks out, try re-running the CIFS setup wizard from the GUI. Ensure that all of the WINS/DNS server config is correct and check the syslog once done, you should see your filer attempting to make contact with the DNS server, attempting to register machine accounts etc...

Let me know how you get on.

Ryan