Hi Milazzo,<br><br>
<div class="gmail_quote">On Thu, May 8, 2008 at 9:03 AM, Milazzo Giacomo &lt;<a href="mailto:G.Milazzo@sinergy.it">G.Milazzo@sinergy.it</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div lang="IT" vlink="purple" link="blue">
<div>
<p>Hi,</p>
<p>&nbsp;</p>
<p>this is a good question: must CIFS be licensed to use SnapDrive for Windows?</p>
<p>&nbsp;</p></div></div></blockquote>
<div>I am uncertain if it&#39;s a legal requirement, but technically it is not. You can set up CIFS in a &#39;limited mode&#39;, where the C$, ETC$ and RPC are available. RPC is what SnapDrive uses for interaction with the filer, in combination with the API, IIRC.</div>

<div>&nbsp;</div>
<div>This way you can access the C$ and ETC$ share, however it is limited to reading/writing config files, firmware updates etc.</div>
<div>&nbsp;</div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div lang="IT" vlink="purple" link="blue">
<div>
<p><span id=""></span></p>
<p>IIt's also true that there a limited CIFS that permit to access to the administrative share C$ but, as example, when I've tried to upgrade </p></div></div></blockquote>
<div>
<div>Use the &#39;software install&#39; or &#39;software upgrade&#39; command to upgrade in this way, that way you won&#39;t get any errors about CIFS being limited, and the &#39;software upgrade&#39; command adds in a package verification so that you know everything actually downloaded correctly before beginning the actual upgrade.</div>

<div>&nbsp;</div>
<div>HTH &amp; HAND,</div>
<div>&nbsp;</div>
<div>Nils</div>
<div><br>-- <br>Simple guidelines to happiness:<br>Work like you don&#39;t need the money,<br>Love like your heart has never been broken and <br>Dance like no one can see you. </div></div></div>