I’ve been running a server with Freenas/TrueNAS Core for the past 4,5 years. The server is only used as a storage server. I don’t have an IT background. So i’m doing things out of my comfort zone. I’ve never had any issues when installing a newer version of the OS. That is, untill now.
After I used the update file for Truenas Scale (first the 24.04 version and after that the most recent 24.10 version) my home network refuses to connect to the SMB shares. Before it was as simple as opening 'my network", click on the server and there was access to the shared folder.
In the past 3 weeks i’ve tried as much as i could in (re)creating groups & users
and messing around with several other settings to a point where i must conclude that the system is probably unreliable due to the many (unsuccesful) tries of getting the shares open in my home network.
Now it seems that the best option is to start with a clean install. Hopefully, with the assistance of some youtube tutorials, i’ll be able to make the shared folder on the pool reachable in my network. After that i won’t touch the settings ever again. That’s a promise and this time i mean it.
What do i need to do before a clean installation of Truenas Scale?
Is it only neccesary to use the export/disconnect function and re-import the pool after the new installation of truenas?
Perhaps this is a dumb question but i don’t want to loose the data on the drives and like i said i’m a bit out of my area of expertise.
TL:DR: Steps before re-installing Truenas?
Just as easy as disconnecting the pool and importing it after the clean installation?
No, none of the win10 and win11 system has access to the share. My best guess is that there must be an issue with permission.
Yes, serveral attempts in recreating groups, users and permissions. In some attempts I was able to access the server, but unable to access the shared folder. It failed on the windows credentials . Truenas didn’t accept the user and password.
Samba authentication is switched on.
I alsof tried to boot the still exciting core version but that didn’t work either. Nor uploading an older config file.
It’s probably a setting somewhere. But where… so I figured that trying again from scratch is perhaps a solution
You have to map every share, you can’t just share the pool root and navigate It. I was doing the same, but Is wrong.
Try enabling just for test the NTLMv1 support on the SMB share on TN, then restart the service, and try connecting again.
If work, you must enable NTLMv2 on clients (and obv remove the NTLMv1 support on TN).
I know, This is wat i had under CORE and that worked without flaws for about 4,5 years. Problem is that you can’t role back after an upgrade to scale so these settings can’t help me anymore.
on Scale under System → Services → click edit on SMB.
As i mentioned, enable that only for testing, is deprecated and have some security risk. But if you stop receive errors on credentials after enabling it, will be easy adapt the clients to use NTLMv2 and fix everything.
Hope this helps!
