<?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 not licensed but still able to access the c$ in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-not-licensed-but-still-able-to-access-the-c/m-p/17252#M1522</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Friends,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i found one of the filer is not licensed but still i'm able to access the c$.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Below is the information,i found from the log translator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="0" cellpadding="0" cellspacing="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="background: #999999; padding: 2.25pt 2.25pt 2.25pt 2.25pt;" valign="top"&gt;&lt;P&gt;&lt;STRONG style="color: #1f497d;"&gt;Description&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD style="background: white; padding: 2.25pt 2.25pt 2.25pt 2.25pt;" valign="top"&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;An attempt to access CIFS has been denied because CIFS is not licensed on this filer. In general, if CIFS is not licensed then client access of the filer using CIFS is denied. If some other protocols are licensed, then a limited subset of CIFS access is accepted by the filer as part of the support for those protocols. However, if access outside the range of accepted operations is attempted, then this event is generated.&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="background: #999999; padding: 2.25pt 2.25pt 2.25pt 2.25pt;" valign="top"&gt;&lt;P&gt;&lt;STRONG style="color: #1f497d;"&gt;Corrective Action&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD style="background: #FFFF99; padding: 2.25pt 2.25pt 2.25pt 2.25pt;" valign="top"&gt;&lt;P&gt;&lt;STRONG style="color: #1f497d;"&gt;Consider purchasing a license for CIFS protocol support.&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any suggestion, which other protocols supports CIFS access upto limited access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciated detailed information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Satish.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:53:52 GMT</pubDate>
    <dc:creator>SATISH_PAMARTHI1983</dc:creator>
    <dc:date>2025-06-05T05:53:52Z</dc:date>
    <item>
      <title>CIFS not licensed but still able to access the c$</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-not-licensed-but-still-able-to-access-the-c/m-p/17252#M1522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Friends,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i found one of the filer is not licensed but still i'm able to access the c$.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Below is the information,i found from the log translator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="0" cellpadding="0" cellspacing="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="background: #999999; padding: 2.25pt 2.25pt 2.25pt 2.25pt;" valign="top"&gt;&lt;P&gt;&lt;STRONG style="color: #1f497d;"&gt;Description&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD style="background: white; padding: 2.25pt 2.25pt 2.25pt 2.25pt;" valign="top"&gt;&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;An attempt to access CIFS has been denied because CIFS is not licensed on this filer. In general, if CIFS is not licensed then client access of the filer using CIFS is denied. If some other protocols are licensed, then a limited subset of CIFS access is accepted by the filer as part of the support for those protocols. However, if access outside the range of accepted operations is attempted, then this event is generated.&lt;/SPAN&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD nowrap="nowrap" style="background: #999999; padding: 2.25pt 2.25pt 2.25pt 2.25pt;" valign="top"&gt;&lt;P&gt;&lt;STRONG style="color: #1f497d;"&gt;Corrective Action&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;TD style="background: #FFFF99; padding: 2.25pt 2.25pt 2.25pt 2.25pt;" valign="top"&gt;&lt;P&gt;&lt;STRONG style="color: #1f497d;"&gt;Consider purchasing a license for CIFS protocol support.&lt;/STRONG&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any suggestion, which other protocols supports CIFS access upto limited access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Appreciated detailed information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Satish.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:53:52 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-not-licensed-but-still-able-to-access-the-c/m-p/17252#M1522</guid>
      <dc:creator>SATISH_PAMARTHI1983</dc:creator>
      <dc:date>2025-06-05T05:53:52Z</dc:date>
    </item>
    <item>
      <title>Re: CIFS not licensed but still able to access the c$</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-not-licensed-but-still-able-to-access-the-c/m-p/17257#M1523</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Satish,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Snapdrive products rely upon having some CIFS functionality in order to work with ONTAP.&amp;nbsp; This software facilitates easy LUN creation, connection, and snapshots for&lt;STRONG&gt; iSCSI, FCP, and FCOE &lt;/STRONG&gt;protocols.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Warm Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan Chilton&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Sep 2013 13:14:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-not-licensed-but-still-able-to-access-the-c/m-p/17257#M1523</guid>
      <dc:creator>dchilton</dc:creator>
      <dc:date>2013-09-18T13:14:04Z</dc:date>
    </item>
    <item>
      <title>Re: CIFS not licensed but still able to access the c$</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-not-licensed-but-still-able-to-access-the-c/m-p/17265#M1524</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dan Chilton,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for your reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;unfortunatly we're not using snapdrive products in our environment. Not sure what was the reason behind this type of functionality.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2013 17:12:14 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-not-licensed-but-still-able-to-access-the-c/m-p/17265#M1524</guid>
      <dc:creator>SATISH_PAMARTHI1983</dc:creator>
      <dc:date>2013-09-26T17:12:14Z</dc:date>
    </item>
    <item>
      <title>Re: CIFS not licensed but still able to access the c$</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-not-licensed-but-still-able-to-access-the-c/m-p/17270#M1525</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if one of the below licenses other than CIFS configured you can run CIFS setup and can access C$. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;iSCSI,&lt;/P&gt;&lt;P&gt;FC&lt;/P&gt;&lt;P&gt;NFS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But the functionality is limited. for full CIFS features you need CIFS license.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2013 19:04:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/CIFS-not-licensed-but-still-able-to-access-the-c/m-p/17270#M1525</guid>
      <dc:creator>kodavali</dc:creator>
      <dc:date>2013-09-26T19:04:47Z</dc:date>
    </item>
  </channel>
</rss>

