Hey

 

I have a problem with the new version. After updating to 6.11 all my shares are invisible.

Navigating to my servers IP shows me this folder is empty message. But when I navigate to a specific folder the shares are there.

 

Basically:

\\192.168.0.250 - no shares shown

\\192.168.0.250\personal - opens folder normally

 

How can I get my folders to show up?

 

Edit: My phone also doesn't show the shares. No shares are set to Yes (Hidden).

Edited September 24, 20223 yr by gxs

It seems that something broke on the update. It doesn't like this setting anymore.

access based share enum = yes

 

Did something change?

Please attach your diagnostics to your next post.

and the output of

ls -la /mnt/user

 

Greetings,

I have since the 6.11 update exactly the same problem.

 

 

Edited October 8, 20223 yr by BuTscH

I had a similiar problem, rebooted the client computer (Windows 10) and I got immediate access to the server.

On 9/24/2022 at 3:47 PM, JorgeB said:

and the output of

ls -la /mnt/user

 

root@Tower:~# ls -la /mnt/user
total 1048596
drwxrwxrwx  1 nobody  users        234 Oct  4 17:04 ./
drwxr-xr-x 13 root    root         260 Oct  8 14:20 ../
drwxrwxrwx  1 nobody  users         48 Sep 22 22:02 ISOs/
drwxrwxrwx  1 nobody  users        126 Jun 27 21:47 Scans/
drwxrwxrwx  1 nobody  users         85 Aug 13  2019 Wii/
drwxrwxrwx  1 nobody  users        208 Dec 14  2019 apivk/
drwxrwxrwx  1 nobody  users        788 Oct  5 07:23 appdata/
drwxrwxrwx  1 nobody  users         26 Sep 25 15:17 bpivk/
drwxrwxrwx  1 nobody  users          6 Sep 29 19:50 dmz/
drwx--x---  1 root    root         254 Oct  4 17:06 docker/
drwxrwxrwx  1 printer users         16 Mar 17  2021 downloads/
drwxrwxrwx  1 nobody  users         52 Mar  3  2020 gpivk/
drwxrwxrwx  1 nobody  users         19 Jul 23 21:32 irena/
-rw-rw-rw-  1 nobody  users 1073741824 Feb 12  2021 libvirt.img
drwxrwxrwx  1       8 mem           44 Apr 12 11:02 mail/
drwxrwx---  1 nobody  users        148 Jun 20 21:10 nextcloud/
drwxrwxrwx  1 nobody  users         70 Feb 16  2021 paperless/
drwxrwxrwx  1 nobody  users       4096 May 12 11:28 programi/
drwxrwxrwx  1 nobody  users       4096 Feb  3  2019 roms/
drwxrwxrwx  1 nobody  users       4096 Sep 25 17:41 series/
drwxrwxrwx  1 printer users         16 Feb  2  2020 series-download/
drwxrwxrwx  1 nobody  users       4096 Jun  1 04:20 video/

On 9/24/2022 at 2:14 PM, ChatNoir said:

Please attach your diagnostics to your next post.

Attached

tower-diagnostics-20221008-1423.zip

I didn't get a reply notification so sorry for the late answer.

 

I also forgot to mention that this happens on all OS. I have tested it on two computers and one VM machine on Unraid and as soon as you set the parameter "access based share enum = yes" the folders are not shown.

 

Since I'm using a Windows 11 and an older Windows 10 VM it has to be the update as the old version worked fine and nothing changed in the meantime.

 

I basically want to hide folders from users that don't have access to them and this issue is holding me back from upgrading two company servers that use this parameter.

Edited October 8, 20223 yr by gxs

Permissions look fine, and if the problem is related to "access based share enum" I really cannot help, never used that option nor remember anyone else on the forum using it, possible it's broken or working differently with the new Samba release.

On 10/8/2022 at 3:09 PM, JorgeB said:

Permissions look fine, and if the problem is related to "access based share enum" I really cannot help, never used that option nor remember anyone else on the forum using it, possible it's broken or working differently with the new Samba release.

Any update on this issue ?

Nope, do you need to use access based share enum = yes ?

16 minutes ago, JorgeB said:

Nope, do you need to use access based share enum = yes ?

Well if there's any other way to hide shares to which other users have no access then no. If not then yes. 😁

Like mentioned I can't help with that setting, not sure if @dlandoncan.

On 9/24/2022 at 4:20 AM, gxs said:

It seems that something broke on the update. It doesn't like this setting anymore.

access based share enum = yes

 

Did something change?

The setting is described in this bug report.  It's not really a bug, but the response describes more about how the setting works.  You have to work with Windows Share Admin tool to get it to work properly.  I suspect Windows has made some changes that are affecting how this setting works in Samba now.