<?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: ftp to filer with no cifs in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3328#M330</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What version of Data ONTAP you have?&lt;/P&gt;&lt;P&gt;Maybe it worked on Data ONTAP 7, but does not work on Data ONTAP 8? In the moment I have no time to check it.&lt;/P&gt;&lt;P&gt;Anyway, I think that Netapp engineers should make some utility to create local users even if no SAN or NAS protocol is licensed (or at least document how to do it).&lt;/P&gt;&lt;P&gt;Netapp filer works very good as ftp server. In this case, that was the main reason why Netapp storage was chosen (and not some other storage). &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 17 Feb 2012 08:33:34 GMT</pubDate>
    <dc:creator>vlfabecic</dc:creator>
    <dc:date>2012-02-17T08:33:34Z</dc:date>
    <item>
      <title>ftp to filer with no cifs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3300#M318</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I want to configure ftp access to filer with no cifs license.&lt;/P&gt;&lt;P&gt;Users must be local.&lt;/P&gt;&lt;P&gt;Currently there is no /etc/passwd file.&lt;/P&gt;&lt;P&gt;I created user with useradmin but ftp login failes with "Login incorrect".&lt;/P&gt;&lt;P&gt;Should I create /etc/passwd with wrfile?&lt;/P&gt;&lt;P&gt;I must be able to set users "home" directory (for example /vol/vol1/files) because there will be file upload to that directory through some scripts from unix hosts.&lt;/P&gt;&lt;P&gt;Version:&amp;nbsp; NetApp Release 8.0.2P4 7-Mode: Tue Nov 15 16:16:47 PST 2011&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:34:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3300#M318</guid>
      <dc:creator>vlfabecic</dc:creator>
      <dc:date>2025-06-05T06:34:40Z</dc:date>
    </item>
    <item>
      <title>Re: ftp to filer with no cifs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3304#M320</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can still run a cifs setup and map to the c$ and etc$ shares on a controller without a CIFS license.&amp;nbsp; We use it for administration all of the time.&amp;nbsp; You only need the license if you are serving up data with CIFS, I beleive. That would be easier than FTP.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Feb 2012 17:05:19 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3304#M320</guid>
      <dc:creator>bsti</dc:creator>
      <dc:date>2012-02-15T17:05:19Z</dc:date>
    </item>
    <item>
      <title>Re: ftp to filer with no cifs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3309#M322</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here is the output:&lt;/P&gt;&lt;P&gt;netappxx&amp;gt; cifs&lt;/P&gt;&lt;P&gt;CIFS is not licensed.&lt;/P&gt;&lt;P&gt;(Use the "license" command to license it.)&lt;/P&gt;&lt;P&gt;netappxx&amp;gt; cifs setup&lt;/P&gt;&lt;P&gt;CIFS is not licensed.&lt;/P&gt;&lt;P&gt;(Use the "license" command to license it.)&lt;/P&gt;&lt;P&gt;netappxx&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not need cifs at all on this filer. It has to do ftp (read and write, and not anonymous), http get and nfs file serving later.&lt;/P&gt;&lt;P&gt;And no authorization to AD, NIS or LDAP.&lt;/P&gt;&lt;P&gt;In version 7.3 problem was fixed by creating entry in /etc/passwd (OK, I also had CIFS license, but did not use it).&lt;/P&gt;&lt;P&gt;Have no experience with ONTAP 8.&lt;/P&gt;&lt;P&gt;Authorization has to be local. And ftp service is primary job of this filer.&lt;/P&gt;&lt;P&gt;How to create functional /etc/passwd file?&lt;/P&gt;&lt;P&gt;Is there any other way?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Feb 2012 09:29:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3309#M322</guid>
      <dc:creator>vlfabecic</dc:creator>
      <dc:date>2012-02-16T09:29:04Z</dc:date>
    </item>
    <item>
      <title>Re: ftp to filer with no cifs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3314#M324</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;you can setup an anonymous FTP , without CIFS. Please try the follwoing &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) in option FTP enbale anonymous FTP ( when loigin from the client use the login mae: ftp , password : &amp;lt;blank&amp;gt;&lt;/P&gt;&lt;P&gt;2) In the anonymous FTP directory give the path of the qtree where the scripts needs to be put.&lt;/P&gt;&lt;P&gt;3) in ftpd.dir.override provide the same path as that of the anonymous FTP.&lt;/P&gt;&lt;P&gt;4) leave everthing else default.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check if the FTP works. if it fails please prove me the error message.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kumaresan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Feb 2012 11:27:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3314#M324</guid>
      <dc:creator>kumaraysun</dc:creator>
      <dc:date>2012-02-16T11:27:17Z</dc:date>
    </item>
    <item>
      <title>Re: ftp to filer with no cifs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3320#M326</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anonymous ftp must not be allowed.&lt;/P&gt;&lt;P&gt;But I fixed the problem with the following:&lt;/P&gt;&lt;P&gt;1. On the other filer (with CIFS) I did:&lt;/P&gt;&lt;P&gt;# cifs passwd somepassword&lt;/P&gt;&lt;P&gt;and copied hash to notepad.&lt;/P&gt;&lt;P&gt;2. Then I created /etc/passwd with:&lt;/P&gt;&lt;P&gt;# wrfile /etc/passwd&lt;/P&gt;&lt;P&gt;and added user entry manualy (with hash generated on the other filer) with home dir as it has to be.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After that ftp authorization worked as it has to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, thanks for your ideas and time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vladimir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Feb 2012 15:21:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3320#M326</guid>
      <dc:creator>vlfabecic</dc:creator>
      <dc:date>2012-02-16T15:21:37Z</dc:date>
    </item>
    <item>
      <title>Re: ftp to filer with no cifs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3325#M328</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I apologize for that.&amp;nbsp; For some reason, for us, we can do this even though CIFS is not licensed.&amp;nbsp; I assumed that is the case for everyone.&amp;nbsp; I think in our case we re licensed for FCP, so we get some cifs functionality as a result. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Feb 2012 16:36:58 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3325#M328</guid>
      <dc:creator>bsti</dc:creator>
      <dc:date>2012-02-16T16:36:58Z</dc:date>
    </item>
    <item>
      <title>Re: ftp to filer with no cifs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3328#M330</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What version of Data ONTAP you have?&lt;/P&gt;&lt;P&gt;Maybe it worked on Data ONTAP 7, but does not work on Data ONTAP 8? In the moment I have no time to check it.&lt;/P&gt;&lt;P&gt;Anyway, I think that Netapp engineers should make some utility to create local users even if no SAN or NAS protocol is licensed (or at least document how to do it).&lt;/P&gt;&lt;P&gt;Netapp filer works very good as ftp server. In this case, that was the main reason why Netapp storage was chosen (and not some other storage). &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Feb 2012 08:33:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3328#M330</guid>
      <dc:creator>vlfabecic</dc:creator>
      <dc:date>2012-02-17T08:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: ftp to filer with no cifs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3333#M332</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you try “cifs passwd” command?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 18 Feb 2012 03:28:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3333#M332</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2012-02-18T03:28:47Z</dc:date>
    </item>
    <item>
      <title>Re: ftp to filer with no cifs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3338#M334</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As I said, no cifs command works, but once again:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;netappxx&amp;gt;&lt;/P&gt;&lt;P&gt;netappxx&amp;gt; cifs passwd&lt;/P&gt;&lt;P&gt;CIFS is not licensed.&lt;/P&gt;&lt;P&gt;(Use the "license" command to license it.)&lt;/P&gt;&lt;P&gt;netappxx&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Feb 2012 09:15:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3338#M334</guid>
      <dc:creator>vlfabecic</dc:creator>
      <dc:date>2012-02-21T09:15:41Z</dc:date>
    </item>
    <item>
      <title>Re: ftp to filer with no cifs</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3343#M336</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Okay, you were on the right track with the passwd file.&amp;nbsp; Here is your issue:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.netapp.com/support/index?page=content&amp;amp;id=2011031&amp;amp;actp=LIST_RECENT&amp;amp;viewlocale=en_US&amp;amp;searchid=1329871738158" target="_blank"&gt;https://kb.netapp.com/support/index?page=content&amp;amp;id=2011031&amp;amp;actp=LIST_RECENT&amp;amp;viewlocale=en_US&amp;amp;searchid=1329871738158&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was confused because apparently ifyou have FCP or ISCSI licensed, you get partial CIFS functionality per below.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.netapp.com/support/index?page=content&amp;amp;id=2012847&amp;amp;actp=LIST_RECENT&amp;amp;viewlocale=en_US&amp;amp;searchid=1329870988100" target="_blank"&gt;https://kb.netapp.com/support/index?page=content&amp;amp;id=2012847&amp;amp;actp=LIST_RECENT&amp;amp;viewlocale=en_US&amp;amp;searchid=1329870988100&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You need to add passwd entries into the /etc/passwd file to get FTP access.&amp;nbsp; The trick is generating the password.&amp;nbsp; Aborzenkov listed the most likely solution, which is to use CIFS passwd.&amp;nbsp; Since you don't have CIFS, you can't use that.&amp;nbsp; Another option (and probably your ONLY option) is below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://kb.netapp.com/support/index?page=content&amp;amp;id=1011368&amp;amp;actp=search&amp;amp;viewlocale=en_US&amp;amp;searchid=1329871738158" target="_blank"&gt;https://kb.netapp.com/support/index?page=content&amp;amp;id=1011368&amp;amp;actp=search&amp;amp;viewlocale=en_US&amp;amp;searchid=1329871738158&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Specifically, near the bottom:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;For UNIX operating systems, a normal UNIX crypt(3) password entry can be used &lt;BR /&gt;in the NetApp filer's &lt;CODE&gt;/etc/passwd &lt;/CODE&gt;file. This can be done using the &lt;BR /&gt;filer's &lt;CODE&gt;wrfile &lt;/CODE&gt;command to rewrite the /etc/passwd file. Note that &lt;BR /&gt;without an NFS or CIFS license, the only way to manage &lt;CODE&gt;/etc&lt;/CODE&gt; files &lt;BR /&gt;would be through telnet (wrfile/rdfile) or FTP.&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would do this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Add a new passwd entry in the file for your FTP user. &lt;/P&gt;&lt;P&gt;Generate the password using the crypt function from one of your linux/unix workstations in your environment.&lt;/P&gt;&lt;P&gt;Make sure FTP is enabled:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;options ftpd.enable on &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And I think you should be set.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Feb 2012 01:09:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/ftp-to-filer-with-no-cifs/m-p/3343#M336</guid>
      <dc:creator>bsti</dc:creator>
      <dc:date>2012-02-22T01:09:01Z</dc:date>
    </item>
  </channel>
</rss>

