Skip to main content
NetApp Knowledge Base

secd.nfsAuth.noNameMap error because mapped Windows user does not exist

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

Applies to

  • ONTAP 9
  • NFS

Issue

NFS access to an NTFS security style volume/qtree fails and Event Management System (EMS) reports secd.nfsAuth.noNameMap:error

Example:

Thu Dec 12 13:01:17 +0100 [node1: secd: secd.nfsAuth.noNameMap:error]: 
vserver (svm1) Cannot map UNIX name to CIFS name. 
Error: Get user credentials procedure failed   [  4 ms] 
Determined UNIX id 123 is UNIX user 'user1'   
[     4] Mapping Successful for Unix-user 'user1' to Windows user 'DOMAIN1\user1' at position 10
[     5] Successfully connected to ip 10.1.2.3, port 445 using TCP  
[    13] Successfully authenticated with DC dc1.domain1.local   
[    17] Could not find Windows name 'DOMAIN1\user1' **
[    17] FAILURE: Name mapping for UNIX user 'applebsd' failed. Explicit Mapping failed and no default mapping found

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.