Today i did upgrade my TrueNas Scale 24.04.2.2 to 24.10.0.2
before the update all smb connections from my 5 Windows PC´s worked fine
now i can not connect from my 5 Windows PC´s via smb to my TrueNas
EDIT:
tested with fresh install of Win11 no connection same error on TrueNas Scale 24.04.2.5 and TrueNas Scale 24.10.0.2
On TrueNas Scale 24.04.2.2 all SMB Connections work from all Windows clients
Access to \\STORAGE is not possible. You may not have permission to use this network resource. Contact the server administrator to find out if you have the necessary permissions.
No valid sequence for updates was found
from my linux servers i do not have this problem, i can connect just fine
here is my smb.conf from my TrueNas
[global]
disable spoolss = True
dns proxy = False
load printers = False
max log size = 5120
printcap = /dev/null
bind interfaces only = True
fruit:nfs_aces = False
fruit:zero_file_id = False
restrict anonymous = 2
winbind request timeout = 2
passdb backend = tdbsam:/var/run/samba-cache/private/passdb.tdb
workgroup = WORKGROUP
netbios name = STORAGE
netbios aliases =
guest account = nobody
obey pam restrictions = False
create mask = 0664
directory mask = 0775
ntlm auth = True
server multichannel support = False
unix charset = UTF-8
local master = True
server string = TrueNAS Server
log level = 1
logging = file
server smb encrypt = default
server min protocol = NT1
idmap config * : backend = tdb
idmap config * : range = 90000001 - 100000000
registry shares = True
include = registry
I’m having somewhat the same issue with my upgrade from Core to Scale. It looks like it could be related to having the “root” of the dataset shared (SMB) from previous version. It was “allowed” (but frowned upon) before, but now I believe Kubernetes doesn’t like it shared. I’m still trying to figure out my issue…
with TrueNAS Scale 24.04.2.2
all worked fine and then after the Update to TrueNas Scale 24.10.0.2
i cant connect from any windows Pc´s (Windows 10 Pro Win10 Ent Windows Server 2019)
Interesting that you’re getting an error which makes no sense in this context (ERROR_PATCH_NO_SEQUENCE is usually only encountered when installing something).
I have attached my testparm -s output below. It was created on on TrueNAS Scale 24.10.0.2. No issues on my end, however I did a fresh install on version 24.10.0.0.
You seem to have NTLMv1 Auth enabled, maybe that causes issues?
Otherwise maybe one of the samba logs may have some clue (maybe try tail /var/log/samba4/log.*).
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
max log size = 5120
netbios name = TRUENAS
passdb backend = tdbsam:/var/run/samba-cache/private/passdb.tdb
printcap name = /dev/null
registry shares = Yes
restrict anonymous = 2
server multi channel support = No
server string = TrueNAS Server
winbind request timeout = 2
idmap config * : range = 90000001 - 100000000
fruit:zero_file_id = False
fruit:nfs_aces = False
idmap config * : backend = tdb
create mask = 0664
directory mask = 0775
[family]
ea support = No
path = /mnt/tank/family
posix locking = No
read only = No
smbd max xattr size = 2097152
vfs objects = streams_xattr shadow_copy_zfs ixnas zfs_core io_uring
tn:vuid = 2d2108ea-0844-41cf-aa8a-c4bf3c39eae2
fruit:time machine max size = 0
fruit:time machine = False
nfs4:chown = True
tn:home = False
tn:path_suffix =
tn:purpose = DEFAULT_SHARE
I’m experiencing a comparable issue since the update when trying to connect from my Proxmox VE server to a SMB share.
Nothing has changed at the Proxmox side.
I’ve already enabled audit logging for the SMB share and debug logging for the SMB service on the NAS but there are not relevant logs created. Not even an attempt of logging in with any user from the Proxmox host.
I’ve checked with tcpdump if packets are going in and out between the two servers. So far I’ve only seen packets flowing from Proxmox to the NAS but not the other way around.
Does anyone have got further information to troubleshoot the SMB service builtin?
I don’t know about this particular error, but have found that Electric Eel SMB shares don’t always play nice with:
Shares previously exported as home directories.
Various states of enumeration bring checked/unchecked.
Guest users unless you explicitly create a user actually named guest.
In all cases, stripping the ACLs, deleting the SMB share, and then recreating the SMB share (with or without filesystem permission changes, depending on what you’re doing) have fixed the problems for me. In a few edge cases I had to reset user passwords, or enable client-side SMB v2/3 support or encryption explicitly, to get everything ship-shape but it’s been somewhat of a trial-and-error process for me as I never got anything useful from the audit logs when this happened. The full reset I just outlined (even with the data in place) seemed to fix it for me, though.
I tried all that i could think…
deleting all smb shares and creating new = same problem
resettiing all acl´s and creating new = same problem
tried fresh install of Truenas 24.10.0.2 and applying my backup config = same problem
what worked is installing Truenas 24.10.0.2 fresh and adding all my shares and other things back manually …
it would be really cool for the future to export just parts of the config or get a checkbox what to import when you apply the backup
I am a bit frustrated with Truenas Scale i had to reinstall it since i moved from Truenas Core a couple of times because things broke
Freenas and Truenas Core was rock solid i was using it since i think 2010 when Open ZFS support was added and i think i reinstalled it maybe 4 or 5 times in 13 years…
I hope Truenas Scale will get as stable as Truenas Core was
i don´t want to offend the devs of Truenas, in fact i am really happy and thankfull for their work, this is just my oppinion
I took some time to perform some research in my environment and I’ve found out what is causing the problem.
The problem when migrating from 24.04 to 24.10 is the network docker is using by default. It is using the following address pool:
172.17.0.0/12
The address pool of my internal network is 172.16.0.0/12 so they are overlapping. So when Proxmox is talking to the SMB share on TrueNAS the answer gets sent out to the docker0 interface which belongs to the docker bridge created automatically.
So it was not a problem with permissions, SMB parameters or something like that. It was just a plain old routing problem.
I am having the same problem and really don’t want to have to install and configure TrueNAS from scratch in order to fix it. I have too much data and too many ZFS snapshots I need to keep.
I can’t get any useful information from the audit logs and there are no IP address/subnet conflicts. SMB usage is essentially unusable and has been for a while now. I’m at my wits end, please could anyone help suggest how I can resolve the problem?
