Hi,
Yes I agree to the problem you are facing. Try creating an account for
the filer in the domain. wait for the replication to happen and thenm run cifs
setup. You shd be fine. But i assume that the filer by running cifs
setting even when the account is not precreated has the ability to create a
computer account for itself. You can find that option in the gui mode of admin
http://<name_of_filer>/na_admin. Also pl check with
your admins if you are a member of account operators (just a guess).
FYI, If the win2k domain is in native mode, then your best bet would be to
downgrade to 6.3, run cifs setup, join the domain and reupgrade to 6.3.1.
Actually there is a i feel so, a bug in version prior to 6.3 in which the
filers cannot join to the native win2k domain using fqdn eg abc.rest.com. I
doesnt just understand the native doman properly. It shd be a problem. We have
done this on our couple of filers to make em properly talk to Win2k native
domain.
Hope this helps...
I think netapp shd do something about it. Right ..!
-----Original Message-----
From: John Stoffel
[mailto:stoffel@lucent.com]
Sent: Fri 1/31/2003 8:36 PM
To: toasters@mathworks.com
Cc:
Subject: OnTap
6.3.1 and cifs setup problems.
Hi,
I'm having a problem getting an F760 with NFS/CIFS
running OnTap 6.3.1
to actually talk to our Win2K domain properly.
I'm assuming it's a
priv problem on the PDC side, but I don't know enough
of how to fix
it.
Basically, whenever I try to run 'cifs setup', it
fails at the end
with the following message:
Could not create
Active Directory account for the filer: No such object
CIFS could
not create server machine account.
But I'm supposed to have the privs
with my account to add this machine
into ActiveDirectory.
Has
anyone else run into stuff like this? And does anyone have any
hints
on what I need to do on the Windows PDC to give myself the privs
I need to
get this done?
Thanks,
John
John Stoffel - Senior
Unix Systems Administrator - Lucent
Technologies
stoffel@lucent.com - http://www.lucent.com
- 978-399-0479