Network Appliance(TM)

Manual Pages

Table of Contents

NAME

cifs setup - setup CIFS service

SYNOPSIS

cifs setup

DESCRIPTION

The cifs setup command performs the initial configuration of the filer for CIFS. The license for CIFS must be installed before entering this command. The cifs setup command must be run from the console or from a telnet connection; it cannot be run over rsh. The following shows the setup dialog: 

  Enable CIFS access to the filer by a Windows(tm) PC

The first prompt will vary depending on the current settings. If no WINS server(s) have been configured, as would be the case the very first time cifs setup is run, the prompt would be: 

  Your filer is only visible to PCs on the same net.
  Do you want to make the filer visible via WINS? [no]:

If a WINS server(s) was configured, the prompt would be: 

  Your filer is visible to all systems using WINS.
  The WINS name servers configured are:
   xxx.xxx.xxx.xxx
   xxx.xxx.xxx.xxx
  Do you want to modify this list? [no]:

If the user answers ``yes'', they will be prompted for the address(es) of the WINS servers: 

  Please enter next WINS IP address (or return to end list):

They should type, in response to each prompt, the IP address of the next WINS server to use, and just type a blank line to end the list.

Next, the name of the host will be entered. The default will be a CIFSized version of the filer's host name, but the CIFS name has restrictions that the host name does not. 

  The name of this filer will be 'HOSTNAME'.
    Do you want to modify this name? [no]:

The user will probably not want to change this name. If they say ``yes'', they will be asked: 

  Enter the CIFS name for the filer:

Next, the name of the workgroup or domain to which the host should belong will be entered. Normally, this should match an existing workgroup or domain in the client's network. If the filer will be using a domain controller to authenticate users, then this must match the domain controller's domain name. 

  This filer will be a member of the workgroup or domain 'WORKGROUP'.
    Do you want to modify this name? [no]:

The user will probably change this name. If they say ``yes', then they will be asked: 

  Enter the workgroup or domain name for the filer:

WORKGROUP is the same default that Microsoft uses. If cifs setup has been run before, then WORKGROUP will be replaced by the name the user selected.

Next, if an password file is not present on the filer, then one will be created; the user will be asked for the password for the super-user account: 

  CIFS requires local /etc/passwd and /etc/group files.
  Default files will be created containing 'root'
  Enter the password for root:
  Retype the password:

Next, the filer will ask if it should authenticate users with an automatically-chosen domain controller, a specific domain controller, or a local /etc/passwd file: 

  The filer can authenticate users by using a domain controller chosen
  automatically, or by using a specific machine as a domain controller, or
  by using the "/etc/passwd" file.

  Do you want to use a domain controller chosen automatically? [yes]:

If the user answers ``no'', they will be asked for the name of a domain controller or an indication that /etc/passwd should be used: 

  Enter either the name of a domain controller, or / to force use of
    "/etc/passwd":

If the user answers with /, then /etc/passwd will be used; otherwise, the name the user types in will be used as the name of a domain controller.

Finally, the user will be asked which security model to use: 

  By default CIFS accesses use PC style semantics.
    Do you want to enforce UNIX semantics instead? [no]:

This is described in the section on Share Level ACLs.

In addition, two shares will be created. The C$ share will be at the root of the file system. The HOME share will be in the /home directory. Each will be created with full root access and no Everyone rights. This is sufficient to allow an administrator to completely set up a filer without having to rely on an NFS connection.

Table of Contents