Skip to main content
NetApp Knowledge Base

Windows to Unix same name mapping not working as expected

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

Applies to

  • ONTAP 9
  • Name mapping

Issue

  • The volume security type is Unix
  • Windows client fails to access the volume
  • Windows client can access volume successfully when volume Unix permission is 777
  • The file owner is nobody when creating files via Windows client.
  • Windows name map to Unix user: pcuser
  • NIS is missing in passwd database of ns-switch
::> vserver services ns-switch show -vserver vserver1
Source
Vserver         Database       Order
--------------- ------------   ---------
vserver1        hosts          files,dns
vserver1        group          files
vserver1        passwd         files
vserver1        netgroup       files
vserver1        namemap        files

 

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.