SMB problems after update to 12.0-release on ONE computer
Description
Problem/Justification
Impact
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Lack of SMB access with root account is known impact of 12.0.
Yes, I was using root to log int o the SMB shares.
both machines have multiple shares on the primary pools and secondary pools.
I was able to log into one machine with root, but not my secondary. I guess my question is why I am able to log in as root on one machine, but not the other..
I will create the proper login credentials and log in with alternate users.
Is there a good link that shows the "proper" method of creating user accounts with file sharing.
Note: The two servers are used for Plex, and home storage. About 20TB total for each server.
Secondary server is simply a "backup" server that I robocopy files to periodically and then shut down between updates.
drwxr-xr-x+ 11 root wheel 15 Aug 17 12:34 /mnt/NAS
# file: /mnt/NAS
# owner: root
# group: wheel
group:90000004:rwxpD-aARWc---:fd-----:allow
user:root:rwxpDdaARWcCo-:fd-----:allow
everyone@:r-x---a-R-c---:fd-----:allowIt appears that there are two possible issues here:
1. root is no longer a permitted SMB user starting in 12
2. group 90000004 may not exist. This is in the range automatically allocated by winbindd, and is non-deterministic. Specifically, it is non-deterministic in the sense that different servers may end up with different values for the WELL-KNOWN / BUILTIN groups as they are generated. The same applies in the case that /var/db/system/samba4/winbindd_idmap.tdb is ever removed / rebuilt.
Which share is the one having issues?
Details
Details
Assignee
Reporter
Labels
Components
Fix versions
Affects versions
Priority
LowMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
I have two fairly identical servers. 32GB dual Xeon CPU X5355.
I updated both to TrueNAS-12.0-Release.
Now the primary system will allow SMB logons from Windows 10 devices, but the SECONDARY server refuses logons.
No changes were made to any login or passwords on either system
Since this is a method to compare what could have gone wrong with the second system, and what differences could have been created during an update, I am notifying support.
Is there anything obvious that could have caused this? My primary system works find, secondary is no longer accessible via SMB.
LOGON to web UI using same credentials works fine, Both systems WERE working normally, now only one is.