Either enable plain text passwords on the Windows client and populate the filer's /etc/password file. Note that there is a DS client on the Windows 2000 server CD to fix this problem without lowering security by using plain-text passwords. Consult Windows support for details.

-Or-

In DATA ONTAP 6.1 through 7G, create user accounts with the useradmin command.

Creating local users on the filer:

Creating local user accounts with the filer's useradmin useradd command does not require that plain text passwords be enabled. Up to 96 filer local users can be created. See the useradmin man page for more details.

Note:
Currently User Manager cannot be used to manage filer local user accounts. User Manager in Windows NT 4.0 can only view the filer user accounts. However, User Manager in Windows 2000 cannot. Use the Group's menu to display local users.

Enabling plain text passwords:

Warning: When plain text passwords are enabled, passwords are no longer secure when they travel across the network during user authentication.

Enable plain text passwords by using the respective MS article for your Windows client. To use plain text passwords, user accounts must be created in the filer's /etc/passwd file or be authenticated using NIS. For more information on creating users in the the /etc/passwd file, see Article 3010502:What is the format for /etc/passwd entries?

Enabling plain text passwords on Windows 95 (Service Releases 1, 2 and 2.1):
See MS Article Q165403

Enabling plain text passwords on Windows NT 4.0 (Service Pack 3 and above):
See MS Article Q166730

Enabling plain text passwords on Windows 2000 clients:
See MS Article Q244627

Warning:
In step 1 of the article above, if you cannot access Administrative Tools directly, check if Administrative Tools exists in the Control Panel.

Note: The following registry setting can be set for Windows 2000 through Windows 7:

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkStation\parameters] EnablePlainTextPassword=dword:00000001

Disclaimer

NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of any information or recommendations provided in this publication, or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS, and the use of this information or the implementation of any recommendations or techniques herein is a customer’s responsibility and depends on the customer’s ability to evaluate and integrate them into the customer’s operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.

Here is the doc (below)

I don’t think that is a reasonable solution security-wise - not willing to do that

Symptoms

Cause

Solution