<?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 Unrouted CIFS Share in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Unrouted-CIFS-Share/m-p/135509#M29763</link>
    <description>&lt;P&gt;Running cDOT 9.1 and have a Windows 2016 server accessing a NTFS vol over SMB3, both joined to a domain.&amp;nbsp; Can I create &lt;EM&gt;and safely utilize &lt;/EM&gt;a 2nd CIFS LIF&amp;nbsp;(unrouted and MTU9000) on the SVM hosting the NTFS vol?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Once or twice a year a domain change will occur that briefly (&amp;lt;5 seconds) disrupts our internal DNS resolution, when this occurs our Windows 2016 app&amp;nbsp;accessing its data over the SMB3 path&amp;nbsp;throws a bunch of errors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also we have had one or two occasions in a year where a brief network disruption (&amp;lt;5 sec) on the core breaks routing.&amp;nbsp; Same issue with errors occuring.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I'd like to do is join an SVM to a domain, then create a 2nd CIFS LIF (MTU9000) that is not routed and therefore not able to resolve the&amp;nbsp;CIFS name of the SVM, and then access that 2nd CIFS LIF's IP directly from the application server.&amp;nbsp; This seems risky to me since the 1st CIFS LIF is the one that is acutally bound to the domain.&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 14:26:55 GMT</pubDate>
    <dc:creator>hello-jon</dc:creator>
    <dc:date>2025-06-04T14:26:55Z</dc:date>
    <item>
      <title>Unrouted CIFS Share</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Unrouted-CIFS-Share/m-p/135509#M29763</link>
      <description>&lt;P&gt;Running cDOT 9.1 and have a Windows 2016 server accessing a NTFS vol over SMB3, both joined to a domain.&amp;nbsp; Can I create &lt;EM&gt;and safely utilize &lt;/EM&gt;a 2nd CIFS LIF&amp;nbsp;(unrouted and MTU9000) on the SVM hosting the NTFS vol?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Once or twice a year a domain change will occur that briefly (&amp;lt;5 seconds) disrupts our internal DNS resolution, when this occurs our Windows 2016 app&amp;nbsp;accessing its data over the SMB3 path&amp;nbsp;throws a bunch of errors.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also we have had one or two occasions in a year where a brief network disruption (&amp;lt;5 sec) on the core breaks routing.&amp;nbsp; Same issue with errors occuring.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I'd like to do is join an SVM to a domain, then create a 2nd CIFS LIF (MTU9000) that is not routed and therefore not able to resolve the&amp;nbsp;CIFS name of the SVM, and then access that 2nd CIFS LIF's IP directly from the application server.&amp;nbsp; This seems risky to me since the 1st CIFS LIF is the one that is acutally bound to the domain.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 14:26:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Unrouted-CIFS-Share/m-p/135509#M29763</guid>
      <dc:creator>hello-jon</dc:creator>
      <dc:date>2025-06-04T14:26:55Z</dc:date>
    </item>
  </channel>
</rss>

