Add SMB share to SyncThing Folder Issue

chadilac

Dabbler
Joined
Dec 27, 2022
Messages
24
I've installed SyncThing on my TrueNAS Core server. Installed the Android App and files are syncing. Now I want to access them via an SMB share. I can see the top Share in windows Explorer I called Phone_Sync, but when I double click on it, it won't open....my other shares work fine.

1679885438880.png


I set the SyncMe dataset
Code:
everyone@ to have Full Control

1679884901796.png


The Share:

1679885010241.png


Share ACL
1679885054292.png


Share File ACL
1679885124283.png


I see `everyone@` is listed twice, one with what looks like full permissions and another without any, so assuming that may be the issue.
1679885231114.png


I found this link which seemed to explain this I think, and ran those commands for the syncthing user (983), no luck.

I'm a windows programmer with no unix experience, so speak to me slowly and like I'm 5 years old, lol.
 

Attachments

  • 1679884952886.png
    1679884952886.png
    4.5 KB · Views: 74

morganL

Captain Morgan
Administrator
Moderator
iXsystems
Joined
Mar 10, 2018
Messages
2,694
FYI, we're doing work with Synthing on TrueNAS SCALE to handle ACLs better.

Did you read this forum post?
 

chadilac

Dabbler
Joined
Dec 27, 2022
Messages
24
FYI, we're doing work with Synthing on TrueNAS SCALE to handle ACLs better.

Did you read this forum post?
Hi @morganL I'm talking about CORE not SCALE. Yes, I did see that post and did add that group as well, but forgot to explicitly mention I did that, which you can see in that prior screenshot which shows the builtin_users group having full control.

However, I see you also said to "Then make sure your SMB user is a member of that group." I don't want to have to connect to the SMB share with an explicit user, but rather just be open to all network users. So wasn't sure how to handle that aspect of your instructions from that post.

1679932651624.png
 

morganL

Captain Morgan
Administrator
Moderator
iXsystems
Joined
Mar 10, 2018
Messages
2,694
So it works for a built-in user but not for anyone else??

I'm not sure why everyone appears twice....once with zero permissions.. perhaps someone else has seen this.
Do any other datasets/shares have the same issue?
 
Top