topic Re: CIFS Authenication issues with AD in cDOT 8.3 version in Network and Storage Protocols

CIFS Authenication issues with AD in cDOT 8.3 version

frozen — Wed, 04 Jun 2025 23:32:39 GMT

Hello Experts,

We migrated one cDot array from one site to another, I configured everything as per new site and at last was performing " CIFS modify " for joining it to the particular domain and make shares accessible.

I got below error message while I did it.. Has someone come across simillar issues.

Error: Machine account creation procedure failed

[ 28964] Could not find Windows SID

[ 29118] Deleted existing account

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

Re: CIFS Authenication issues with AD in cDOT 8.3 version

shatfield — Thu, 13 Aug 2015 05:54:53 GMT

Did you update the DNS entries in the SVM to use the new domain controllers?

Re: CIFS Authenication issues with AD in cDOT 8.3 version

frozen — Thu, 13 Aug 2015 06:08:31 GMT

DNS is updated to SVM.

Re: CIFS Authenication issues with AD in cDOT 8.3 version

shatfield — Thu, 13 Aug 2015 06:15:41 GMT

Can you ping the domain controller/DNS server from the SVM's management lif?

Are the timezone and clock correctly set and in sync?

Re: CIFS Authenication issues with AD in cDOT 8.3 version

frozen — Thu, 13 Aug 2015 07:47:31 GMT

Hi ,

I am able to ping domain controller from vserver LIF's and ping returns alive.

I get errors only when I try to connect Netapp to AD.

Re: CIFS Authenication issues with AD in cDOT 8.3 version

frozen — Fri, 14 Aug 2015 18:48:56 GMT

We were to able fix this error by bypassing IP in proxy ( bluecoat ) WAN Accelerator.

CIFS joined after this change.

Re: CIFS Authenication issues with AD in cDOT 8.3 version

rajesharumugam — Mon, 01 Feb 2016 12:24:52 GMT

Check the Route show command and verify route created for the SVM or create the route create command.

route create -vserver (SVMNAME) -destination 0.0.0.0/0 -gateway xx.xxx.xxx.xx