About a month ago I had been tortured by a CIFS NetApp issue for several days.
What was causing my issue is that though I was running the wizard to reset the Filer for domain operations I had not completed a CIFS terminate command. Once I had terminated the CIFS installation on my NetApp (and the filer had been removed from the domain for some time).
Windows 2000 Domain Name: DOMAIN1.local
OMAIN1.local
Now another key here is that I was interacting with my AD domain to first delete FILER’s computer record in the Computers OU in the target domain before going forward to add it to the domain.
If the log capture (with alt domain and IP addresses) does not help you to resolve your issue please post and let me know. I can provide it as steps instead if needed.
Hope my “brain fart” moment helps someone else that might also be needlessly banging their head on the wall. 
Another Eviserating Experiance
Thanks to the extended weekend I had I was finally able to have a clear mind when I came back into the office.
So here is a rundown and a look into what I had to accomplish:
FILER> cifs domaininfo
NetBios Domain: DOMAIN1
Type: Windows 2000
Filer AD Site: Default-First-Site-Name
Not currently connected to any DCs
Preferred Addresses:
10.1.1.20 DOMAIN1 PDCBROKEN
Favored Addresses:
10.1.1.76 DOMAIN1 PDCBROKEN
Other Addresses:
None
Not currently connected to any AD LDAP server
Preferred Addresses:
None
Favored Addresses:
None
Other Addresses:
None
FILER> cifs resetdc
Disconnecting from domain DOMAIN1…
Reconnecting to domain DOMAIN1…
Reconnection failed!
Connection to AD LDAP server failed!
FILER> cifs setup
CIFS Setup can not be run while CIFS is active
FILER> cifs terminate
CIFS local server is shutting down…
CIFS local server has shut down…
FILER> cifs setup
Enable CIFS access to the filer by a Windows(tm) PC
Your filer is visible to all systems using WINS.
The WINS name servers currently configured are:
10.1.1.20
Do you want to modify this list? [no]:
This filer is currently configured as a Multiprotocol filer.
Do you want to configure this filer as a NTFS-only filer? [no]: Yes
This filer is currently a member of the domain ‘DOMAIN1’
If you want to change the name of the filer, or change
the filer’s domain membership, you must delete its
existing account information.
Do you want to delete the existing filer account information? [no]: Yes
The default name of this filer will be ‘FILER’.
Do you want to modify this name? [no]:
CIFS supports three types of user authentication:
1. Windows Domain authentication.
2. Windows Workgroup authentication using the filer’s user accounts.
3. /etc/passwd and/or NIS/LDAP based authentication.
What type of authentication will this filer use? [1]:
The filer will use Windows Domain authentication.
Enter the Windows Domain for the filer []
DOMAIN1.LOCAL is a Windows 2000(tm) domain.
In order to create this filer’s domain account, you must supply the
name and password of an administrator account with sufficient privilege
to add the filer to the DOMAIN1.LOCAL domain.
Please enter the Windows 2000 user [Administrator@DOMAIN1.LOCAL]: Administrator@DOMAIN1.local
Password for Administrator@DOMAIN1.local:
CIFS – Logged in as Administrator@DOMAIN1.local.
By default, setup creates the filer account in the Active
Directory container named ‘Computers’. Alternatively, you can
install the filer in an organizational unit (OU) by specifying
the domain relative distinguished name of the OU, as in
‘ou=innerOU,ou=outerOU’.
Active Directory container for filer account? [cn=computers]:
CIFS – Connecting to domain controller.
Welcome to the DOMAIN1 (DOMAIN1.LOCAL) Windows 2000(tm) domain.
CIFS local server is running.
FILER>