Hi.
I reinstall TrueNAS and import pool then follow this video
but always I have this error :
Windows cannot access \192.168.8.10\tst
You do not have permission to access \1925.168.8.10\tst . Contact your network administrator to request access .
Hi and welcome to the forums.
Have you assigned your user ACL access to the dataset?
Check if dataset is not read-only = “on”.
Without the link of the video he followed we can only guess, and my guess is that, as he said, he reinstalled truenas and imported his pools, without restoring his old config. So the most likely problem is that he’s trying to connect with a user that was present in the old install, but not in the new, or he created a new user and didn’t give that user the right permissions.
Thank you
sorry I can’t upload pic
this is user
1000
/nonexistent
/bin/sh
N/A
false
false
false
false
true
yes the user is the owner
thank you
Inherit (off)
thank you
sorry I found the video in another post .
I created new user and new dataset based on YouTube explanation ( [Lawrence Systems] video
And did you edit the Dataset ACL’s so that your new user has permissions to access the Dataset?
So contrary to the video I’m going to suggest leaving ‘User’ and ‘Group’ alone which on CORE I believe is root and wheel but on SCALE is root and root.
I would also remove the owner@ and group@ entries unless you know you need them and then simply add in your user or group with whatever access is desired Modify / Full Control etc.
Finally if you already have data in the dataset then you will need to check the box that says ‘Apply Permissions Recursively’.
There are some remarkably incompetent howto videos floating around youtube that advise users to chmod 770 /mnt/tank from shell, which of course breaks permissions for everyone. So maybe also post output of stat /mnt/Temp from shell.
Thank you
Windows cannot access \192.168.8.10\tst
You do not have permission to access \1925.168.8.10\tst . Contact your network administrator to request access .
You probably mistyped the IP in the second part of the error message there, that’s fine and unlikely to be a tributing issue. But I also note that you used a single preceeding backslash in both instances. In Windows, a valid network path looks like so: \\<IP>\sharename, or using your IP and share as a reference: \\192.168.8.10\tst
Doublecheck what you are using. The above may at least be one contributing factor, you may have multiple issues at the same time.
There’s your problem. You ran chmod 770 on /mnt/Temp. Incompetent youtube influencers FTW. Run the command chmod 755 /mnt/Temp.
When you remove the other execute bit (like the video you followed suggested for “security reasons”) it prevents all users who aren’t a member of the wheel group from being able to traverse the mountpoint for your pool. It basically breaks everything for non-root users.
Thank you
sorry my mistake , yes its \192.168.8.10\tst
Thank you
So to confirm, are you typing a single backslash at the start, or two?
You should use two when entering the network path in Windows.
What is the origin of this pool? What is output of getfacl /mnt/Temp?
Thank you
yes two backslash
