Skip to main content
NetApp Knowledge Base

NFS access to NTFS security style volume fails because name mapped default Windows user does not exist in AD

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

Applies to

  • ONTAP 9 and later
  • NFS
  • NTFS security style volume
  • Name mapping

Issue

  • NFS users are not able to access NTFS security style volume
  • The -default-win-user is set to a non-default value
    • The default value is blank.
  • At time of access failure, EMS says
    • [?] Mon Oct 30 11:30:45 +0100 [node1: secd: secd.nfsAuth.problem:debug]: vserver (vs1) General NFS authorization problem.
      Error: Get user credentials procedure failed
      [ 0] Mapping an unknown UID to default windows user
      [ 0] Trying to map user to the default Windows name 'windows-user'
      [ 0] Using a cached connection to dc1.domain.com
      [ 1] Could not find Windows name 'windows-user'
      **[ 1] FAILURE: Name mapping for UNIX user '12345' failed with transient errors.

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.