Hello!
I have been using my formerly FreeNAS, now "TrueNAS-12.0-STABLE - Release Train"-server for some years now.
Recently I had to use one old Windows PC with XP and wanted to make the shares available for the old PC.
so I enabled "SMB v1" in the options of the SMB service.
It all worked like. a charm. I also disabled SMB v1 afterwards, as I usually don't need v1 support.
But since then I have a weird problem: SMB shares cannot be accessed directly after booting the server.
I do actually power off the system after usage, as I normally need it just about twice a week and cannot afford the electricity needed for running the system 24/7.
And since that day, the SMB shares cannot be accessed after booting the TrueNAS server. The service is set to autostart and smbd is actually running though, as I can see using top through SSH, but it's not possible to access the shares.
But: When I simply disable and enable the SMB service, the shares are available again until the next boot. So SMB access just doesn't work after autostart, but it does work when restarting Samba later.
No changes have been made to the system for years, besides this recent Toggling of the "SMB v1" option and the regular stable train updates of course.
What could this be? Can someone help me finding and fixing the issue please? :)
Thank you in advance!
I have been using my formerly FreeNAS, now "TrueNAS-12.0-STABLE - Release Train"-server for some years now.
Recently I had to use one old Windows PC with XP and wanted to make the shares available for the old PC.
so I enabled "SMB v1" in the options of the SMB service.
It all worked like. a charm. I also disabled SMB v1 afterwards, as I usually don't need v1 support.
But since then I have a weird problem: SMB shares cannot be accessed directly after booting the server.
I do actually power off the system after usage, as I normally need it just about twice a week and cannot afford the electricity needed for running the system 24/7.
And since that day, the SMB shares cannot be accessed after booting the TrueNAS server. The service is set to autostart and smbd is actually running though, as I can see using top through SSH, but it's not possible to access the shares.
But: When I simply disable and enable the SMB service, the shares are available again until the next boot. So SMB access just doesn't work after autostart, but it does work when restarting Samba later.
No changes have been made to the system for years, besides this recent Toggling of the "SMB v1" option and the regular stable train updates of course.
What could this be? Can someone help me finding and fixing the issue please? :)
Thank you in advance!
Last edited: