Skip to main content
NetApp Knowledge Base

Multiprotocol name mapping is incorrect despite explicit name mapping rule

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

Applies to

  • ONTAP 9
  • Multiprotocol NAS
  • LDAP

Issue

  • A UNIX user maps to the wrong Windows user, or vice versa
  • A name mapping rule was explicitly created for the user, e.g.:

cluster1::> vserver name-mapping create -vserver svm1 -direction unix-win -position 1 -pattern root -replacement domain\\Administrator

cluster1::> vserver name-mapping show -vserver svm1

Vserver:   svm1
Direction: unix-win
Position Hostname         IP Address/Mask
-------- ---------------- ----------------
1       -                 -                   Pattern: root
                                          Replacement: domain\\Administrator

cluster1::> set advanced

cluster1::*> access-check authentication show-creds -node cluster1-01 -vserver svm1 -unix-user-name root
  (vserver services access-check authentication show-creds)

UNIX UID: root <> Windows User: domain\some_other_user(Windows Domain User)
...

 

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.