Skip to main content
NetApp Knowledge Base

Cifs check fails - SecD Error: no connections available due to dc timeouts

  1. Last updated
  2. Save as PDF
Views:
1,977
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • SMB/CIFS

Issue

  • cifs check shows DC server status as down
  • AD authentication is not working properly

::> cifs check -vserver svm1

Vserver : svm1
Cifs NetBIOS Name : svm1_cifs
Cifs Status : Running
Site :

Node Name DC Server Name DC Server IP Status Status Details
--------- -------------- ------------ ------ --------------
node-01 domain.local - down SecD Error: no connections available
node-02 domain.local - down SecD Error: no connections available
2 entries were displayed.

  • ACL creation on the cifs share with domain account fails with below error

::*> vserver cifs share access-control create -vserver <vserver_name> -share <share_name> -user-or-group <username> -user-group-type windows -permission full_Control

Error: command failed: Failed to resolve the security identifier (SID) for the account named "username". Reason: Object name either does not exist or could not be resolved using the available servers. Check the event log for additional information.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.