storto Posted June 23, 2023 Share Posted June 23, 2023 I have been on these forums for days trying to figure this out. windows machines return: cannot access //Tower, The remote device or resource won't accept the connection. mac machines return: This fileserver will not allow any additional users to log on. Here's what I got so far. I think it's a permissions problem. when i look at the log I see: Failed to open /var/lib/samba/private/secrets.tdb I tried deleting and renaming the secrets.tdb file, a new one gets created but still the same- Warning? As much as i want to say that the upgrade to 6.12.0 and 6.12.1 is the culprit, i don't think so. I'm a total noob at the command line, with a VERY basic understanding. I have used the tools>>Docker safe New Perms and the Tools>> New permissions to no avail. also with a run a: smbstatus i get: Samba version 4.17.7 PID Username Group Machine Protocol Version Encryption Signing ---------------------------------------------------------------------------------------------------------------------------------------- Service pid Machine Connected at Encryption Signing --------------------------------------------------------------------------------------------- /var/cache/samba/locking.tdb not initialised This is normal if an SMB client has never connected to your server. I have connected to the server using SMB. This is the first time i have posted asking for help. The problem is above my pay-grade. Any help would be greatly appreciated, even a point in the right direction..... Attached is my Diagnostics..... tower-diagnostics-20230623-1533.zip Quote Link to comment
trurl Posted June 23, 2023 Share Posted June 23, 2023 35 minutes ago, storto said: the upgrade Was it working before? Quote Link to comment
storto Posted June 23, 2023 Author Share Posted June 23, 2023 yes, but i did a bunch of stuff after upgrading. icluding: Added/replaced a drive. I mounted a shared drive on my network.(unassigned devices) and here's the unknown: i tried to set up an rsync file to "sync" one of the unraid shares to the freshly mounted unassigned device. i was following a video on youtube, but instead setting up a file and having it run in "cron" i just tried a single line command. it didn't work though. Quote Link to comment
trurl Posted June 24, 2023 Share Posted June 24, 2023 What do you get from command line with this? ls -lah /mnt and this? ls -lah /mnt/user Quote Link to comment
storto Posted June 24, 2023 Author Share Posted June 24, 2023 ls -lah /mnt: drwxr-xr-x 16 root root 320 Jun 23 15:07 ./ drwxr-xr-x 20 root root 440 Jun 23 15:34 ../ drwxrwxrwt 2 nobody users 40 Jun 23 15:07 addons/ drwxrwxrwx 1 nobody users 58 Jun 24 04:40 cache/ drwxrwxrwx 9 nobody users 158 Jun 24 04:40 disk1/ drwxrwxrwx 7 nobody users 118 Jun 24 04:40 disk2/ drwxrwxrwx 8 nobody users 136 Jun 24 04:40 disk3/ drwxrwxrwx 7 nobody users 118 Jun 24 04:40 disk4/ drwxrwxrwx 7 nobody users 118 Jun 24 04:40 disk5/ drwxrwxrwx 2 nobody users 6 Jun 24 04:40 disk6/ drwxrwxrwx 5 nobody users 69 Jun 24 04:40 disk7/ drwxrwxrwt 2 nobody users 40 Jun 23 15:07 disks/ drwxrwxrwt 3 nobody users 60 Jun 23 15:08 remotes/ drwxrwxrwt 2 nobody users 40 Jun 23 15:07 rootshare/ drwxrwxrwx 1 nobody users 158 Jun 24 04:40 user/ drwxrwxrwx 1 nobody users 158 Jun 24 04:40 user0/ ls -lah /mnt/user: drwxrwxrwx 1 nobody users 158 Jun 24 04:40 ./ drwxr-xr-x 16 root root 320 Jun 23 15:07 ../ drwxrwxrwx 1 nobody users 43 Nov 29 2019 .Trash-99/ drwxrwxrwx 1 nobody users 4.0K Jul 8 2020 Backups/ drwxrwxrwx 1 nobody users 77 May 2 2022 Documents/ drwxrwxrwx 1 nobody users 105 Oct 5 2020 Individual\ Folders/ drwxrwxrwx+ 1 nobody users 4 Jun 12 10:28 Media/ drwxrwxrwx 1 nobody users 322 Jun 14 11:44 appdata/ drwxrwxrwx 1 nobody users 28 Oct 13 2022 domains/ drwxrwxrwx 1 nobody users 53 Aug 15 2020 downloads/ drwxrwxrwx 1 nobody users 0 Oct 14 2021 isos/ drwxrwxrwx 1 nobody users 26 Oct 14 2021 system/ drwxrwxrwx 1 nobody users 6 Jun 23 14:44 testorama/ Quote Link to comment
storto Posted June 25, 2023 Author Share Posted June 25, 2023 i don't know if this is good or bad? should they be root? Quote Link to comment
itimpi Posted June 25, 2023 Share Posted June 25, 2023 3 hours ago, storto said: i don't know if this is good or bad? should they be root? NO! If they were root they would not be visible over the network. Quote Link to comment
storto Posted June 25, 2023 Author Share Posted June 25, 2023 28 minutes ago, itimpi said: NO! If they were root they would not be visible over the network. using this "query"?, here are the permissions of my secrets folder. Are these correct?: should the secrets file be root? drwx------ 3 root root 100 Jun 23 15:07 ./ drwxr-xr-x 4 root root 80 Mar 31 17:49 ../ drwx------ 2 root root 460 Jun 23 15:54 msg.sock/ -rw------- 1 nobody users 8.0K Jun 23 15:52 secrets.tdb -rw-r--r-- 1 root root 207 Jun 23 15:07 smbpasswd Quote Link to comment
storto Posted June 25, 2023 Author Share Posted June 25, 2023 I changed the permissions of the secrets.tdb to root, still failed to open error 13 Quote Link to comment
Solution storto Posted June 26, 2023 Author Solution Share Posted June 26, 2023 OK fixed it! so i've been trying to delete the secrets.tdb file and let the system recreate it. It would but i kept getting the same error (13) So i tried deleted the secrets.tdb file, then i created a blank file using nano secrets.tdb. then when i restarted samba using /etc/rc.d/rc.samba restart I got: [2023/06/25 21:52:19.709234, 0] ../../source3/passdb/pdb_smbpasswd.c:249(startsmbfilepwent) Jun 25 21:52:19 Tower smbd[22041]: startsmbfilepwent_internal: file /var/lib/samba/private/smbpasswd did not exist. File successfully created. Jun 25 21:52:19 Tower wsdd2[22054]: starting. So fixed! thank you for the help. Storto Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.