TrueNas scale cannot access SMB share

[NewToTrueNas]

As the title says.... I've some problems with getting an SMB share to work.
This is my first attempt at setting up a TrueNas installation, so please try to add a link or something pointing me in the correct direction.

What I've done so far:
- Install TrueNas (TrueNAS-SCALE-22.02.4)
- Setup a single storage pool with 6 drives as rz2
- Added local group
- Added local user and set the new group as primary user group
-- (Samba Auth enabled for both)
- Created new dataset with share type SMB
- Edited the ACL of the new dataset and added the user group with full control
- Created a new SMB share for the new dataset

I've documented all steps with screenshots (1-10).
When trying to access the share from my Win10 machine, get a Windows cannot access \\IP\name error message.

 

[Ericloewe]

What about the root of the server? \\192.168.1.118 without the share path?

 

[NewToTrueNas]

Just \\192.168.1.118 results in the same "windows cannot access" error but explorer does not show a login promt.

 

[winnielinnie]

Did you modify the permissions of the root dataset by any chance?

Code:

getfacl /mnt/Pool0

And,

Code:

ls -la /mnt/Pool0

 

[NewToTrueNas]

I thought about that. I did not (at least intentionally) change anything about the root/pool.

But I was not sure, so I reset my system and setup everything again (exactly the same as the first time). It still does not work. (Please note, I made as small "mistake" and gave the pool another name...)


I've run the commands you posted in the Shell (Web UI). The results are attached as screenshot. Sorry about that, I was not able to copy the output from the shell. Copy or paste requires a "insert key" which my laptop does not have :( and copy via F12 insect element is not en option since the output is rendered inside a canvas.

 

[NewToTrueNas]

Btw. here is the output from the client side:

> Test-NetConnection -ComputerName 192.168.1.118 -CommonTCPPort SMB

ComputerName : 192.168.1.118
RemoteAddress : 192.168.1.118
RemotePort : 445
InterfaceAlias : Wi-Fi
SourceAddress : 192.168.1.116
TcpTestSucceeded : True


> net view \\192.168.1.118
System error 5 has occurred.

Access is denied.

 

[winnielinnie]

What about on this newly reset system:

Code:

getfacl /mnt/Pool-0/d0

 

[NewToTrueNas]

Here the output.

 

[Ericloewe]

I've run the commands you posted in the Shell (Web UI).

You should probably set up SSH ASAP. The Web shell is terrible.

As for your immediate issue, make a (semi-)real user (not root!) the owner of any datasets that will be shared.

 

[winnielinnie]

Here the output.

That doesn't look right.

Is the ACL you configured in the GUI not being applied?

According to those permissions, it's no wonder your user cannot access the SMB share from Windows.

@anodos is more familiar with the ACL-side of things for TrueNAS.

 

[NewToTrueNas]

@Ericloewe I created a new user and assigned that user as owner of the dataset `d0`.

@winnielinnie I've run the command again after changing the user of the dataset. But it still looks the same (not that I expected any changes).

I've documented everything by screenshots...

 

[winnielinnie]

Wait, my bad, since you're on SCALE:

Code:

nfs4_getfacl /mnt/Pool-0

and

Code:

nfs4_getfacl /mnt/Pool-0/d0

 

[winnielinnie]

Can you try this?

From Windows 10, in the CMD or Powershell command-line:

Code:

net use /d /y *

Then even for good measure, reboot the computer and try to access the SMB share again?

 

[NewToTrueNas]

Can you try this?

From Windows 10, in the CMD or Powershell command-line:

Code:

net use /d /y *

Then even for good measure, reboot the computer and try to access the SMB share again?

 

[NewToTrueNas]

I run both commands.
The first one did not work; error: "Operation to request attributes not supported". I probably finally have to setup SSH and stop using the web shell (will try that tomorrow or more correct this morning).

On the Windows side: I do not have any network drives mapped or credentials stored for the share. I tried to reboot the client machine and also tried to access the share from 2 difference PCs Win10 and Win11. Nothing worked... BUT after running your script, I was able to access the share.
Thank you very much!