Skip to main content
NetApp Knowledge Base

secd.ldap.noServers and secd.conn.auth.failure after LDAPS is mismatched

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

Applies to

  • ONTAP 9
  • LDAP
  • CIFS

Issue

  • After a mismatch in the environment if LDAPS is required by AD (Active Directory) but set to false on the SVM or set to true on the SVM, but not required by AD,  the following errors are observed in EMS:

[node1: secd: secd.conn.auth.failure:notice]: Vserver (SVM1) could not authenticate over the network to server (DC1). Error: Local error (Service: LDAP (Active Directory), Operation: SiteDiscovery).

[node1: secd: secd.ldap.noServers:EMERGENCY]: None of the LDAP servers configured for Vserver (SVM1) are currently accessible via the network for LDAP service type (Service: LDAP (Active Directory), Operation: SiteDiscovery).

  • Folder NTFS permissions will not be allowed to be modified as the user cannot be successfully authenticated when secd.ldap.noServers error is present. The following error may also be displayed when attempting this:

The program cannot open the required dialog box because it cannot determine whether the computer named "host's FQDN" is joined to a domain.

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.