Reconfiguring CIFS for the filer

Meaning of reconfiguring CIFS

Reconfiguring CIFS means running the cifs setup program again for CIFS settings. The CIFS configuration settings that you can change by running cifs setup are as follows:

WINS server addresses
Whether the filer is multiprotocol or NTFS-only
Whether the filer uses Windows domain authentication, Windows workgroup authentication, or UNIX password authentication
Domain or workgroup to which the filer belongs
Filer name

Prerequisites for reconfiguring CIFS

You must meet the following prerequisites before you can reconfigure CIFS:

CIFS service must be terminated.
If you want to change the filer's domain, the filer must be able to communicate with the primary domain controller for the domain in which you want to install the filer. You cannot use the backup domain controller for installing the filer.
If you want to change the name of the filer, you must create a new computer account on the domain controller. This is not necessary if you are using Windows 2000.

How the cifs setup program works

The cifs setup program prompts you for CIFS configuration information and writes the new information to the /etc/cifsconfig.cfg file and /etc/cifssec.cfg file. The following events take place after you start the cifs setup program:

The /etc/cifsconfig.cfg file is renamed to /etc/cifsconfig.bak.
The program prompts for the WINS server addresses.
The program prompts you to configure your filer to be NTFS-only or multiprotocol.
If the /etc/cifsconfig.cfg file exists but is corrupted, the program prompts you to create a new computer account for the filer on the domain controller.
If the /etc/cifsconfig.cfg file exists but is not corrupted, the program prompts you to delete the existing account. You delete the account if you are installing the filer into a new domain. The following list describes the result, depending on your response to this prompt:
- If you delete the existing account, Data ONTAP renames /etc/cifssec.cfg to /etc/cifssec.bak. When the filer restarts, it uses the new security information specified in the new computer account on the domain controller.
- If you do not delete the existing account, the filer restarts in the same domain, using the existing security information.
The program prompts you to install the filer in a domain or workgroup and prompts for the domain or workgroup name.
If all information you entered is valid, the program writes the configuration information to the /etc/cifsconfig.cfg file. Otherwise, it renames the /etc/cifsconfig.bak file to /etc/cifsconfig.cfg. When the filer restarts, it uses the previous information.
Note
If cifs setup fails, the /etc/cifssec.bak file is not renamed to /etc/cifssec.cfg.

Effects of changing an NTFS-only filer to a multiprotocol filer

Although you can change the filer from NTFS-only to multiprotocol using cifs setup, you can achieve the same effects by simply setting the wafl.default_security_style option to unix.

The following list describes the effects of changing an NTFS-only filer to a multiprotocol filer:

Existing ACLs remain unchanged.
The security style of all volumes and qtrees remains unchanged.
When you create a volume, its default security is unix.
The wafl.default_security_style option is set to unix.
Note
Because the security style of the root volume remains ntfs after you change the filer to multiprotocol, you might be denied access to the root volume from UNIX as root. You can gain access if the ACL for the root volume allows full control for the Windows user that maps to root. You can also gain access by setting the cifs.nfs_root_ignore_acl option to on.

Effects of changing a multiprotocol filer to an NTFS-only filer

The following list describes the effects of changing a multiprotocol filer to an NTFS-only filer:

If ACLs already exist on the filer root directory, /etc, and on files in the /etc directory, the ACLs remain unchanged. Otherwise, these ACLs are created such that the BUILTIN\Administrators group has full control.
ACLs on other files and directories remain unchanged.
The security style of all volumes, except read-only volumes, is changed to ntfs.
If the /etc directory is a qtree, its security style is changed to ntfs.
Security style for all other qtrees remains unchanged.
When you create a volume or qtree, its default security style is ntfs.
The wafl.default_security_style option is set to ntfs.

Effects of changing the filer's domain

After you change the filer's domain, Data ONTAP updates the membership of the BUILTIN\Administrators group to reflect the new domain. This change ensures that the new domain's Administrators group can manage the filer even if the new domain is not a trusted domain of the old domain.

Reconfiguring CIFS

To reconfigure a filer for CIFS, complete the following steps.

Step	Action
1	Enter the following command: cifs terminate Result CIFS service is disabled for the filer.
2	Enter the following command: cifs setup Result Data ONTAP runs the `cifs setup` program, which displays a list of prompts for you to reconfigure CIFS.

Step

Action

Enter the following command:

cifs terminate

Result

CIFS service is disabled for the filer.

Enter the following command:

cifs setup

Result

Data ONTAP runs the cifs setup program, which displays a list of prompts for you to reconfigure CIFS.

Aborting CIFS reconfiguration

To terminate the cifs setup program when it is in progress, complete the following step.

Step	Action
1	Press Ctrl-C. Result The cifsconfig.bak file is renamed to cifsconfig.cfg. You can restart CIFS using the configuration information that was used before.