<?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 Re: DFS and CIFS shares in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/DFS-and-CIFS-shares/m-p/114328#M8152</link>
    <description>&lt;P&gt;If you are talking about masking the "real" name/location of an SMB share on a NetApp by using a DFS target defined in Active Directory, that can be done successfully. The main problems I encountered with that approach usually revolved around "weird" old SMBv1 clients (like a multifunction printer/scanner that scans a document and ships it to the SMB share). Also, there were sometimes issues with various flavors of Apple OS, but typically by mapping with cifs://my.dfs.example.com/share/sharename instead of smb://, that got it working. My understanding is that cifs:// forces the Mac OS to autonegotiate down to SMBv1, which apparently is less problematic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But the vast majority of clients, both Windows and Macs, worked just fine with a AD-based DFS target to a NetApp SMB share.&lt;/P&gt;</description>
    <pubDate>Wed, 06 Jan 2016 16:42:41 GMT</pubDate>
    <dc:creator>hanover23</dc:creator>
    <dc:date>2016-01-06T16:42:41Z</dc:date>
    <item>
      <title>DFS and CIFS shares</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/DFS-and-CIFS-shares/m-p/114153#M8146</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good morning,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We wanted to implement Microsoft DFS in place of CIFS that we currently have. Will the CIFS share support the DFS implementation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any thoughts would be appreciated.&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 22:25:44 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/DFS-and-CIFS-shares/m-p/114153#M8146</guid>
      <dc:creator>Tirthaghy</dc:creator>
      <dc:date>2025-06-04T22:25:44Z</dc:date>
    </item>
    <item>
      <title>Re: DFS and CIFS shares</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/DFS-and-CIFS-shares/m-p/114236#M8148</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes we can. Once DFS is installed on an NT server, using the DFS Administrator tool, you need to&amp;nbsp;make entries for the filer's Common Internet File System protocol (CIFS) shares in the DFS root tree.&amp;nbsp;Refer the following Kb for more details.&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.netapp.com/support/index?page=content&amp;amp;id=1010588&amp;amp;actp=search&amp;amp;viewlocale=en_US&amp;amp;searchid=1451899639226" target="_blank"&gt;https://kb.netapp.com/support/index?page=content&amp;amp;id=1010588&amp;amp;actp=search&amp;amp;viewlocale=en_US&amp;amp;searchid=1451899639226&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Jan 2016 10:30:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/DFS-and-CIFS-shares/m-p/114236#M8148</guid>
      <dc:creator>Renifa</dc:creator>
      <dc:date>2016-01-04T10:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: DFS and CIFS shares</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/DFS-and-CIFS-shares/m-p/114248#M8149</link>
      <description>&lt;P&gt;The KB was helpful, thank you!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, NetApp and windows are based on very differnt operating systems,&amp;nbsp; can you please elaborate as to how this is going to work. Will this involve any sort of data migration?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, how will the permission to affected on the shares?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 04 Jan 2016 14:01:00 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/DFS-and-CIFS-shares/m-p/114248#M8149</guid>
      <dc:creator>Tirthaghy</dc:creator>
      <dc:date>2016-01-04T14:01:00Z</dc:date>
    </item>
    <item>
      <title>Re: DFS and CIFS shares</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/DFS-and-CIFS-shares/m-p/114308#M8151</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is a link to a technical report that explains how to integrate CIFS shares within a DFS infrastrucutre&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A title="http://www.netapp.com/au/media/tr-3782.pdf" href="http://www.netapp.com/au/media/tr-3782.pdf" target="_blank"&gt;http://www.netapp.com/au/media/tr-3782.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;/matt&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jan 2016 02:38:05 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/DFS-and-CIFS-shares/m-p/114308#M8151</guid>
      <dc:creator>mbeattie</dc:creator>
      <dc:date>2016-01-06T02:38:05Z</dc:date>
    </item>
    <item>
      <title>Re: DFS and CIFS shares</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/DFS-and-CIFS-shares/m-p/114328#M8152</link>
      <description>&lt;P&gt;If you are talking about masking the "real" name/location of an SMB share on a NetApp by using a DFS target defined in Active Directory, that can be done successfully. The main problems I encountered with that approach usually revolved around "weird" old SMBv1 clients (like a multifunction printer/scanner that scans a document and ships it to the SMB share). Also, there were sometimes issues with various flavors of Apple OS, but typically by mapping with cifs://my.dfs.example.com/share/sharename instead of smb://, that got it working. My understanding is that cifs:// forces the Mac OS to autonegotiate down to SMBv1, which apparently is less problematic.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But the vast majority of clients, both Windows and Macs, worked just fine with a AD-based DFS target to a NetApp SMB share.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jan 2016 16:42:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/DFS-and-CIFS-shares/m-p/114328#M8152</guid>
      <dc:creator>hanover23</dc:creator>
      <dc:date>2016-01-06T16:42:41Z</dc:date>
    </item>
  </channel>
</rss>

