UNSOLVED

dimch

updated

13 years ago

D

dimch

9 Posts

0

2895

January 10th, 2014 06:00

I am unable to create a writeable SMB share. What am I doing wrong?

Hello,

I have found that suddenly the usual procedure for creating SMB shares is not working on an Isilon cluster. I have found an excellent instruction on troubleshooting permission in an "Ask the expert" thread on this forum. However could not understand what is going on. Perhaps one of the reasons of my failing to spot the issue is that Ask the expert example is referring to OneFS 6.5 and I am on OneFS Version: 7.0.0.0.


My issue is that no SMB user seems to be able to write into shares that I am creating.

Here is what I do:

  1. Add a directory smb-test using the File System Explorer in the existing directory /ifs/other.
  2. Set owner user name to joe and group to staff
  3. Give all permissions to owner and group and read and execute permissions to everyone
  4. Create a new SMB share smb-test
  5. Changing Directory ACLs to Do not change existing permissions instead of Apply Windows Default ACLs
  6. Add Full access to user joe and read/write access to group staff.

Now I connect to the share using the credentials for joe with smbclient

smbclient -U joe //ds.domainname/smb-test

however I am unable to create a subdirectory or put a file onto the share, since I am getting

smb: \> mkdir test
NT_STATUS_ACCESS_DENIED making remote directory \test

The only way I could make it work was to allow write access to everyone by issuing a CLI command

isi-ds1# chmod +a everyone allow dir_gen_write smb-test

I have performed the usual diagnostics steps by issuing the CLI commands

1) isi-ds1# isi auth mapping token joe

2) isi-ds1# isi smb shares view --share=smb-test

3) isi-ds1# ls -led /ifs/other/smb-test

4) isi-ds1# ls -lend /ifs/other/smb-test

The output is attached.

  • I have tried also to create a share with Windows Default ACLs but that share also returned permission denied
  • I have tried to connect to the share from a genuine Windows machine to factor out possible issues with smbclient but received the corresponding "Try again" dialog box.

I am running out of ideas what else could be wrong and would welcome any feedback.

1 Attachment