Could not convert sid S-0-0: NT_STATUS_NO_SUCH_USER

[2twisty]

I have 2 TrueNAS SCALE machines. Hardware and disks vary somewhat, but their networking and SMB service are configured identically.

On one of my servers, I am getting these errors in the log CONSTANTLY, and not at all on the others. Shares are working fine, and are configured for guest access.

Code:

Apr 19 14:06:40 truenas winbindd[23919]:   Could not convert sid S-0-0: NT_STATUS_NO_SUCH_DOMAIN
Apr 19 14:11:00 truenas winbindd[23919]: [2023/04/19 14:11:00.241306,  1] ../../source3/winbindd/winbindd_getpwuid.c:120(winbindd_getpwuid_recv)
Apr 19 14:11:00 truenas winbindd[23919]:   Could not convert sid S-0-0: NT_STATUS_NO_SUCH_USER

Attached is the debug package for the server that is malfunctioning.

I have searched and found similar references, but not my exact issue, and the fixes for those don't really apply to my situation.

Any idea what I've got misconfigured on one server and not the other?

Hardware of affected system:
SCALE 22.12.2
Ryzen 5 1600
32G ECC
8x 6TB hard disks in RaidZ2
Cache 120GB NVMe
SLOG 2x120GB NVMe in mirror (I know the size is huge, but you can't get small M.2 drives anymore)
Intel Dual 10G Nic
Some Cheapy Video card for console


Hardware of working system:

SCALE 22.12.2
Ryzen 3 3200G
32G non-ECC
5x 8TB hard disks in RaidZ1
No Cache
No SLOG (will be adding one soon)
Intel Dual 10G Nic
Integrated AMD graphics

 

[2twisty]

I see that many have viewed this thread, but no replies or comments. Does anyone have suggestions for my next diagnostic step?

 

[2twisty]

..... and just like that (snaps fingers), the problem has vanished. Go figure. I changed nothing.

 

[Kuro Houou]

I am seeing a ton of these errors in my logs actually, like multiple per second. This is all in the log.winbindd log. Not sure whats happening but I have started seeing issues with my shares where file copies will just stop, directories will take forever to load.. almost as if its trying to determine some permission or something is just preventing samaba from working.. processor is fine, not overutilized at all on any core... Just strange it only happens with my smb shares.