2015-12-21 05:01 PM
Forgive me, I am not a NetApp person. I'm setting up a virtual simulator for my developers to do their thing in creating functionality for their software...very simple setup for them...
The problem I am having is I cannot access my CIFS shares on the CIFS Server from anywhere on my network
External virtual systems are:
I've been successful with the following...
I cannot see the CIFS server nor it's shares...even the C$.
To me it appears the shares are not properly being shared out by Winders.
Any assistance would be appreciated...
CAMINO::> vserver cifs show
Server Status Domain/Workgroup Authentication
Vserver Name Admin Name Style
----------- --------------- --------- ---------------- --------------
camino-02 CDOT-HSM up SBC domain
CAMINO::> vserver cifs share show
Vserver Share Path Properties Comment ACL
-------------- ------------- ----------------- ---------- -------- -----------
camino-02 admin$ / browsable - -
camino-02 c$ / oplocks - BUILTIN\Administrators / Full Control
camino-02 eng /home/eng oplocks - Everyone / Full Control
camino-02 finance /home/finance oplocks - Everyone / Full Control
camino-02 home /home oplocks - Everyone / Full Control
camino-02 ipc$ / browsable - -
6 entries were displayed.
Solved! SEE THE SOLUTION
2015-12-21 11:54 PM
Difficult to figure out the problem unless we have more details.
I would recommend to follow the below guides provide in the link @ http://mysupport.netapp.com/documentation/docweb/index.html?productID=61689
The above link and guides are for 8.2. For 8.3, follow @ http://mysupport.netapp.com/documentation/docweb/index.html?productID=61885
These are express guides (which are few 10s of pages) which provide a quick n easy way to setup CIFS in clustered Data ONTAP.
2015-12-22 10:34 AM
A few things to check:
1. Make sure the time in the sim matches the time on your domain
2. Be sure you are using different names for each SVM you configure CIFS for when you join it to AD. A computer account is created for the SVM and they need to be unique.
3. You may need to create DNS entries so your clients can find the SVM.
2015-12-23 11:09 AM
Thanks for the suggestions...
I don't think I'm terribly off on this. But I did find an interesting "anomaly"
My developer creates his vserver with an "NIS Switch" (vserver create -vserver camino-02 -rootvolume root_vs0 -aggregate aggr1 -ns-switch nis -rootvolume-security-style ntfs -language C.UTF-8)
2015-12-23 11:42 AM
An incorrect NIS configuration can prevent CIFS from working. If NIS is configured on the SVM make sure the nis domain and nis server are valid, and the nis server is operational. If NIS is not in use, then either ommit nis from the ns-switch option or place it at the end of the list (file,nis). In this case the nisdomain should be blank.
2015-12-23 04:23 PM
Thanks for the help. I believe I got it. I compared the creation of the SVM via command line with the NIS options against the SVM creation via the OnCommand GUI and noticed a difference in the way the nis was being enabled. So I will revisit the nis options during creation on another lab simulator to determine the correct syntax.
All volumes/shares are now available on the network as expected.