Unable to view CIFS/SMB shared files

[iainmacleod]

I have setup samba share from NAS4Free, I have defined users in NAS4Free the same as the user I have on Windows and Linux boxes. If I browse to a share where the folder, and the file inside that folder, have the permission 777 (Read, Write, Execute for Owner, Group, and Others) I can see the folder - but I do not see the file.

If I remove the execute permissions for Other, I can then see the file.

I am at a loss for why the files are visible without Other execute permission, but invisible when Other execute permission is set. Any help?

If I use root persmission in winSCP or SSH I can see the files.

I use Windows 10
I use Crunchbang
NAS4free 10.2.0.2 - Prester (revision 2067)

[iainmacleod]

Any hints?

[daoyama]

Sorry, this is my fault.

2067 (I don't remember other rev.) has "Mapping DOS attributes" is checked by default config.
This means you can not change UNIX permission by hand.
It affects NEW installation only. It was reverted on later rev.

If you want control UNIX permission, DO NOT USE "Mapping DOS attributes".
(or clean install 2118 or later without restoring your config)

[iainmacleod]

Thank you very much for the information. So I disabled mapping DOS attributes and it appears to be good now - the question is, what do I lose by disabling that feature?

What would happen if I upgrade and then re-enable this feature, would I lose seeing the info again? Was there a bug with this setting, or is that how it functions?

Thanks again.

[daoyama]

What would happen if I upgrade and then re-enable this feature, would I lose seeing the info again? Was there a bug with this setting, or is that how it functions?

This is a function, not a bug.
If it's enabled, UNIX permission is mapped to Windows attribute.

Code: Select all

  +------- archive attribute
  |  +---- system attribute
  |  |  +- hidden attribute
  |  |  |
rwxrwxrwx

As a result, you cannot change freely.

[iainmacleod]

Brilliant. Thank you very much. I guess I need to research windows attributes.

[JoseMR]

Hello, a little bit old, but maybe this can help others users running Windows 10 clients as me and facing the OP issue, I personally don't use "Mapping DOS attributes" and I have a client mixture on my network such as Windows 7/10 WinPhone8 and Linux, so my "Max Protocol" under NAS4Free is set to SMB2 and all the clients can access the Samba shares as expected.

However I never managed to see the shares under Windows 10(fresh install) file explorer, depicting all the registry hacks/workarounds I've tried with either "Max Protocol" set to SMB2/SMB3 under NAS4Free.

The solution is quite simple, I just added the server user credentials under Credential Manager on Windows 10(even if same as client), then manually entered the server share paths e.g: \\NAS4FREE\MyShare (case sensitive) and created shortcuts/mapped the network drives in order to access the shares.

This looks more like a Windows 10 bug/issue to me.
Regards

[Snapshot]

There is a well-reported W10 bug affecting network access. My two W10 test PCs cannot see anything on the LAN unless I reduce their SMB level to 2. They can then see other Windows devices but still not the non-Windows. I saw a post where an MS employee had reproduced the problem but there doesn't seem to be any resolution yet.

[Snapshot]

I've just accidentally discovered that this is browse master related. My W7 PC is usually browse master as it's on 24/7 but my W10 Insider PC became browse master when I rebooted the W7 one. Instantly it could see everything on the LAN, the shares on the non-Windows servers and the folders and files within the shares! The second W10 PC could now see everything on the LAN and the shares on the non-Windows servers but nothing within the shares.
So, progress of a sort although not a complete solution.