coral python
Hi! My colleague and I are trying to get to a newly created volume named like \\172.16.15.105\Protein from Windows File Explorer and Windows is insisting on the error message below
We've checked the firewall/network carefully, and we know those well, but we're both new to NetApp. What settings or permisisons have we likely overlooked within NetApp here?
teal lantern
Do you see the share listed when browsing to \\ip? If not, a new share will need to be created pointing to the junction path of the new volume.
red jungle
please show us the output from network interface show and cifs share show from a SSH session to the cluster
brittle osprey
also vserver cifs show
coral python
Thank you! Browsing to \ip produces the same error as \ip\share - I'm not confident this entire NetApp is set up correctly, and I will need to find time to coordinate with my colleague to get SSH to it. I'll update again when I have more info, which might be a few days or longer, we're really swamped right now. I really do appreciate the guidance
brittle osprey
I assume that simply the CIFS setup was not done. You can creaet shares etc. even without vserver cifs create and then it will not work with a similar (or even the same) error
mortal wyvern
when we were moving from 7 mode to Cluster mode, a common mistake every one in our group used to do was to not giving read right to the SVM's root vol. all the vols are mounted on top of the root vol of the SVM and if that is restricted no cifs shares will be visible to anyone. Let me know if you need more details
brittle osprey
when we were moving from 7 mode to Cluster mode, a common mistake every one in o...
I would think that this would give a different error message (like "access denied" or perpetual login windows or things like that) but that's just a guess
mortal wyvern
I would think that this would give a different error message (like "access denie...
don't remember the exact error, but the shares were not visible until the export policy for the root vol was modified
brittle osprey
don't remember the exact error, but the shares were not visible until the export...
good thing export-policies for CIFS are now disabled by default... it was a constant source of issues
mortal wyvern
good thing export-policies for CIFS are now disabled by default... it was a cons...
That's good to know. I didn't know about that change. Thanks!
brittle osprey
it's a cifs option now. -is-export-policy-for-cifs-enabled or something like that.
mortal wyvern
it's a cifs option now. `-is-export-policy-for-cifs-enabled` or something like t...
yep, found it Thanks again!. -is-exportpolicy-enabled.. available only under advanced priv though