How to Configure CIFS  Shares
+++++++++++++++++++++++++

myfiler> 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.

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? [n]:

A filer can be configured for multiprotocol access, or as an NTFS-only
filer. Since multiple protocols are currently licensed on this filer,
we recommend that you configure this filer as a multiprotocol filer

(1) Multiprotocol filer
(2) NTFS-only filer

Selection (1-2)? [1]:

CIFS requires local /etc/passwd and /etc/group files and default files
will be created. The default passwd file contains entries for 'root',
'pcuser', and 'nobody'.

Enter the password for the root user []:

Retype the password:

The default name for this CIFS server is 'myfiler'.

Would you like to change this name? [n]:

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)? [1]: 1

What is the name of the Active Directory domain? [ad1-WIN.COM]: ad1-win.com

In Active Directory-based domains, it is essential that the filer's
time match the domain's internal time so that the Kerberos-based
authentication system works correctly. If the time difference between
the filer and the domain controllers is more than 5 minutes,
authentication will fail. Time services are currently not configured
on this filer.

Would you like to configure time services? [y]: n

In order to create an Active Directory machine account for the filer,
you must supply the name and password of a Windows account with
sufficient privileges to add computers to the AD1 -WIN.COM
domain.
Enter the name of the Windows user [Administrator@AD1 -WIN.COM]: user@ad1 -win.com ---- Following steps can be done with the help of Windows team.

Password for user@ad1 -win.com: xxxxxxx

CIFS - Logged in as user@ad1 -win.com.
Setup was unable to retrieve a list of joinable containers
(organizational units) from Active Directory, therefore a list of
selectable options cannot be provided. Please enter the distinguished
name of the container that you would like the filer to join below.
There is no need to add the domain name portion,
'DC=ad1,DC=odss,DC=ora-win,DC=com', of the distinguished name.
Enter the name of the organizational unit [CN=Computers]:
CIFS - Starting SMB protocol...
It is highly recommended that you create the local administrator
account (myfiler\administrator) for this filer. This account allows
access to CIFS from Windows when domain controllers are not
accessible.

Do you want to create the myfiler\administrator account? [y]: n

Welcome to the AD1 -WIN.COM (AD1) Active Directory(R) domain.

CIFS local server is running.
myfiler>

Now Add CIFS shares --- 

Create CIFS share with Below Command

[root@myhost ~]# ssh myfiler cifs shares -add myshare /vol/my_volume/

Add comment to New share

[root@ myhost ~]# ssh myfiler cifs shares -change myshare  -comment myshare_imp

1 share(s) have been successfully modified

List Shares

[root@ myhost ~]# rsh myfiler cifs shares

Name         Mount Point                       Description

----         -----------                       -----------

CRMdepot     /vol/my_volume/      crmod_sldc

                        everyone / Full Control

Enable below Options on Volume to give better performance

convert_ucode=on

create_ucode=on

Also,  enable below option in Multiprotocol Filer

[root@ myhost ~]# rsh myfiler options |grep -i syml|grep enable

cifs.symlinks.enable         on

Now try Accessing  your share from win server for which u added in CIFS setup