<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic CIFS + Map Drive Letter Permission in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/CIFS-Map-Drive-Letter-Permission/m-p/14636#M3328</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think basically what you are doing is going to be a very painful experience, if you ever get it to work at all.&amp;nbsp; Sharing a single NetApp easily among different authentication domains is normally done by using (and buying) the Multistore license and splitting up your storage unit into multiple virtual filers (vfilers).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are going to have to do some reading on setting up local users and mapping them and somehow getting authentication to work on a filer that is already attached to a windows AD domain.&amp;nbsp; I'm not even sure if it is at all possible.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 May 2011 16:24:10 GMT</pubDate>
    <dc:creator>shaunjurr</dc:creator>
    <dc:date>2011-05-26T16:24:10Z</dc:date>
    <item>
      <title>CIFS + Map Drive Letter Permission</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/CIFS-Map-Drive-Letter-Permission/m-p/14631#M3327</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A have one FAS2050 model and i want to share this equipament with some different customer, using by CIFS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would link to create the volume as required by each customer and put one kind of secure that one customer don't map de volume from other ones. Is it possible?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All customers has access from same network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think that authentication maybe by owner netapp, bacause one customer has domain controller and others not...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have already tried to add ACL to one user customer_xxx with permission change (rwx) and other ACL for everyone with permission No Access and i tested to mount and nothing...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ricardo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:53:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/CIFS-Map-Drive-Letter-Permission/m-p/14631#M3327</guid>
      <dc:creator>ricardo_abreu</dc:creator>
      <dc:date>2025-06-05T06:53:55Z</dc:date>
    </item>
    <item>
      <title>CIFS + Map Drive Letter Permission</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/CIFS-Map-Drive-Letter-Permission/m-p/14636#M3328</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think basically what you are doing is going to be a very painful experience, if you ever get it to work at all.&amp;nbsp; Sharing a single NetApp easily among different authentication domains is normally done by using (and buying) the Multistore license and splitting up your storage unit into multiple virtual filers (vfilers).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are going to have to do some reading on setting up local users and mapping them and somehow getting authentication to work on a filer that is already attached to a windows AD domain.&amp;nbsp; I'm not even sure if it is at all possible.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 May 2011 16:24:10 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/CIFS-Map-Drive-Letter-Permission/m-p/14636#M3328</guid>
      <dc:creator>shaunjurr</dc:creator>
      <dc:date>2011-05-26T16:24:10Z</dc:date>
    </item>
  </channel>
</rss>

