filer join to a domain ,but have issus

[polystortech]

I have a netapp fas270,i want to the filer join to a domain,but there is a issue,following is the infomation,please help me!

Filer FAS270C-B is not a member of a domain.

fas270c-b> cifs terminate

CIFS local server is shutting down...

Sun Mar 16 13:38:13 CST : ALF: CIFS auditing stopped.

CIFS local server has shut down...

fas270c-b> cifs setup

This process will enable CIFS access to the filer from a Windows(R) system.

Use "?" for help at any prompt and Ctrl-C to exit without committing changes.

This filer is currently a member of the Windows-style workgroup

'WORKGROUP'.

Do you want to continue and change the current filer account information? : y

Your filer does not have WINS configured and is visible only to

clients on the same subnet.

Do you want to make the system visible via WINS? :

This filer is currently configured as an NTFS-only filer.

Would you like to reconfigure this filer to be a multiprotocol filer? :

The default name for this CIFS server is 'FAS270C-B'.

Would you like to change this name? :

Data ONTAP CIFS services support four styles of user authentication.

Choose the one from the list below that best suits your situation.

(1) Active Directory domain authentication (Active Directory domains only)

(2) Windows NT 4 domain authentication (Windows NT or Active Directory domains)

(3) Windows Workgroup authentication using the filer's local user accounts

(4) /etc/passwd and/or NIS/LDAP authentication

Selection (1-4)? : 2

What is the name of the Windows NT 4 domain? : poly.com

CIFS - Starting SMB protocol...

Sun Mar 16 13:38:26 CST : ALF: CIFS auditing started.

Sun Mar 16 13:38:49 CST : NBT: All CIFS name registrations have completed for the local server.

• CIFS Setup could not establish a connection with the Primary Domain

• Controller (PDC). Usually this happens when the 'FAS270C-B' account

• does not exist in the domain or must have it's password reset.

Once you have created and/or reset the 'FAS270C-B' machine account, press ENTER. :

• CIFS Setup could not establish a connection with the Primary Domain

• Controller (PDC). Usually this happens when the 'FAS270C-B' account

• does not exist in the domain or must have it's password reset.

Once you have created and/or reset the 'FAS270C-B' machine account, press ENTER. :create

• CIFS Setup could not establish a connection with the Primary Domain

• Controller (PDC). Usually this happens when the 'FAS270C-B' account

• does not exist in the domain or must have it's password reset.

Once you have created and/or reset the 'FAS270C-B' machine account, press ENTER. :

CIFS local server is shutting down...

Sun Mar 16 13:40:20 CST : ALF: CIFS auditing stopped.

CIFS local server has shut down...

[reinoud7]

It's a long time ago for me, but how can the filer find his domain controller without wins with a NT4 domain? I suppose that the domaincontroller is not on the same subnet as the filer, so I think you need wins in a NT4 configuration. If he don't need wins, check on the filer site if you can reach the dc by pinging poly.com.

[randyw]

Make sure the filer's time is no more than 5mins off from the DC. Even though the time make look like it is in sync, make sure you have selected the correct time zone as that will throw the time sync out of whack.

Hope that helps. Shout back if you're still having issues.

[adamfox]

If you're truly joining an NT4 domain, the time shouldn't matter. That's a kerberos thing that came into play with AD.

With NT4, you've got to worry about a couple things:

1. Your PDC (not a BDC) must either be on the local subnet so it can be found via broadcast or, more preferably, via WINS.

2. You must create the computer account manually. cifs setup will not do it for you, like it can wtih AD. If the account already exist, you must delete it and re-create it so it has no computer account password. One will be assigned when the filer connects.