Subscribe
Accepted Solution

CIFS Authenication issues with AD in cDOT 8.3 version

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

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

DNS is updated to SVM.

Re: CIFS Authenication issues with AD in cDOT 8.3 version

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

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

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

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