Why is one windows 11 PC unable to see all files on a samba share

TrueNAS General
,
1

I’ve got something quite weird happening with a SMB share and I was wondering if this community could help.

I have TrueNAS Scale sharing a SMB share which is mounted by three different machines. One machine is a linux container running syncthing and using the SMB share as storage. Two separate windows 11 PC’s mount the share using the same guest login. One of the W11 pc’s can see all the files in the syncthing folder (approx 2300 files) but the other W11 pc can only see some of the files (approx 1500).

Looking at Truenas SMB Status both pc’s are connected with the same user, group, uid, gid and session dialect. When I SSH into the truenas machine and look at the files in the storage directory using ls -ltn they all have the same owner and permissions.

I’m really confused why one W11 pc cannot see some files, can you suggest what might be causing this and how to allow both pc’s to see all the files?

I’m not sure this is a Truenas issue and appreciate it could be something weird with Windows 11, but I figured this might be a good place to ask.

2

Take a look at this. I had a similar issue and this fixed it.

https://www.reddit.com/r/truenas/comments/1fh3dqh/latest_windows_11_update_may_break_smb_shares/?rdt=55301

3

Both my win11 machines are Windows 11 Home, so the gpedit.msc setting suggested in that post isn’t relevant as gpedit.msc isn’t available in Win 11 Home.

4

In an admin powershell

Set-SmbClientConfiguration -RequireSecuritySignature $false

https://techcommunity.microsoft.com/blog/filecab/accessing-a-third-party-nas-with-smb-in-windows-11-24h2-may-fail/4154300

5

What version of TrueNAS is this? What is the output of testparm -s?

6

Running
Get-SmbClientConfiguration displays RequireSecuritySignature : False so this setting is already set.

7

The version of TrueNAS is TrueNAS SCALE 25.04. This has been happening for a while and it also happened on the previous version I was running (24.10.2)

The output of testparm -s is as follows:

root@nostromo[~]# testparm -s
Load smb config files from /etc/smb4.conf
Loaded services file OK.
Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback)

Server role: ROLE_STANDALONE

# Global parameters
[global]
        bind interfaces only = Yes
        disable spoolss = Yes
        dns proxy = No
        load printers = No
        logging = file
        map to guest = Bad User
        max log size = 5120
        netbios name = TRUENAS
        passdb backend = tdbsam:/var/run/samba-cache/private/passdb.tdb
        printcap name = /dev/null
        registry shares = Yes
        server multi channel support = No
        server string = TrueNAS Server
        winbind request timeout = 2
        zfs_core:zfs_block_cloning = False
        zfs_core:zfs_integrity_streams = False
        idmap config * : range = 90000001 - 100000000
        rpc_server:mdssvc = disabled
        rpc_daemon:mdssd = disabled
        fruit:zero_file_id = False
        fruit:nfs_aces = False
        idmap config * : backend = tdb
        create mask = 0664
        directory mask = 0775


[Media]
        guest ok = Yes
        path = /mnt/orville/Media
        posix locking = No
        read only = No
        smbd max xattr size = 2097152
        vfs objects = streams_xattr shadow_copy_zfs ixnas zfs_core io_uring
        fruit:resource = stream
        fruit:metadata = stream


[syncthing]
        guest ok = Yes
        path = /mnt/orville/syncthing
        posix locking = No
        read only = No
        smbd max xattr size = 2097152
        vfs objects = streams_xattr shadow_copy_zfs ixnas zfs_core io_uring
        fruit:resource = stream
        fruit:metadata = stream
8

You could try to create new User on your server with the same permissions, and use the new User to access the files on the Windows machine that doesn’t work.
You would need to go into the Windows credential manager to delete the current user though as Windows will have stored the log in information

1 Like