Skip to main content
NetApp Knowledge Base

vserver cifs create command fails with No servers found in DNS lookup

  1. Last updated
  2. Save as PDF
Views:
421
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
NAS
Last Updated:

Applies to

  • ONTAP 9
  • CIFS

Issue

  • The vserver cifs create command fails with the following error
  • DNS server is able to find the domain controller but it fails to lookup Servnames
cluster::*> vserver cifs create -cifs-server CIFSVSERVER -domain domain.com -vserver svm
 
Enter the user name: user_name
Enter the password:
 
Error: Machine account creation procedure failed
[  0 ms] Trying to create machine account 'CIFSVSERVER' in 'domain.com' for Vserver 'svm'
[   235] Found 2 domain controllers through DNS
[   306] Successfully connected to ip xxx.xxx.xxx.xxx, port 389 using TCP
[   601] No servers found in DNS lookup for _ldap._tcp.dc._msdcs.domain.com.
[   762] No servers found in DNS lookup for _ldap._tcp.domain.com.
[   917] No servers found in DNS lookup for _kerberos._tcp.domain.com.
[   917] No servers available for MS_LDAP_AD, vserver: 4, domain: domain.com.
**[   917] FAILURE: Uncaptured failure while creating server account
Error: command failed: Failed to create the Active Directory machine account "CIFSVSERVER".
Reason: SecD Error: no server available.

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.