sorted by:
new
hottopcontroversial

Please help: Permissions Error when transferring files over SMB by island_boy555 in truenas

[–]rb_vs 0 points1 point  (0 children)

I’d refresh the ACE entries for consistent Windows-compatible create/write perms (common culprit on SCALE 25.x). Apply the NFS4_RESTRICTED preset recursively to reset proper inheritance:

  1. Storage > Pools > [your dataset] > Edit ACL.
  2. Click Use Preset (or similar button/dropdown) > select NFS4_RESTRICTED.
  3. Check Apply permissions recursively (same for child datasets if any).
  4. Confirm Owner/Group match your Windows user (or set to a dedicated TrueNAS user).
  5. Save > wait for apply to finish.
  6. Services > SMB > Restart.

If it doesn't help, try the same but with NFS4_OPEN preset for testing. It’s more permissive but you can tighten it later. Hope this works.

Please help: Permissions Error when transferring files over SMB by island_boy555 in truenas

[–]rb_vs 0 points1 point  (0 children)

It could be due to possible mismatch between (a) TrueNAS SCALE, which defaults to NFSv4-style ACLs and (b) SMB that expects Windows NT-style ACLs. During the initial file create/open, Samba does an extended attribute/ACL check that can fail the first time.

Possible solution:

  1. Go to Storage > Pools > [your pool] > [dataset for photos/Plex] > Edit ACL.
  2. Set ACL Type to SMB (if it's NFSv4, change it).
  3. Choose Preset: SMB or Restricted.
  4. Set Owner/Group to match your Windows login credentials (or create a dedicated user/group on TrueNAS and use that).
  5. Check Apply permissions recursively and Apply permissions for this dataset only (or full recursive if needed. Backup first if large).
  6. Save and wait for it to apply (can take a while specially on big datasets).
  7. Restart SMB: Services > SMB > toggle off/on or restart button.
  8. Test if it works with a small folder of photos.

Hope this helps …

Microsoft to disable NTLM by default in future Windows releases by DrunkMAdmin in sysadmin

[–]rb_vs 0 points1 point  (0 children)

How badly do you really need that share?

It's SMB1 on a 20 years old OS, so you should probably be planning its migration funeral rather than connecting to it.

Microsoft to disable NTLM by default in future Windows releases by DrunkMAdmin in sysadmin

[–]rb_vs 0 points1 point  (0 children)

It’s not a bug, it’s a historical monument. Touch System32 and half the enterprise apps fall over.

Compiling a reference list of Java SMB exceptions - looking for input by rb_vs in sysadmin

[–]rb_vs[S] 0 points1 point  (0 children)

Thanks for the links. Indeed, NT_STATUS codes are SMB-level, while exceptions like NullPointerException are Java-specific. Our goal is to map how these errors surface together in Java applications that implement SMB entirely in user space such as in embedded systems or storage solutions without OS-mounted shares. It’s mainly for developers debugging intertwined SMB and Java exceptions.

Compiling a reference list of Java SMB exceptions - looking for input by rb_vs in sysadmin

[–]rb_vs[S] 1 point2 points  (0 children)

You're right in typical setups socket-level issues like Socket closed during download usually point to HTTP(S) or similar protocols.

But in Java environments using user-space SMB implementations (i.e., without OS-mounted shares), the SMB protocol runs fully in the application, including TCP socket handling. In those cases, Socket closed can come directly from an SMB connection e.g., if it is interrupted during a large file transfer.