Dear all,
I upgraded beginning of January from FreeNAS 11.3 to TrueNAS-12.0-U1 with no noticeable issue except the fact I destroyed the GELI encrypted pool to be compatible with the new encryption system.
I'm used to access SMB shares through the Netbios name of the TrueNAS server or one of its aliases.
My network clients are mostly Windows 10 plus several Linux clients (e.g. Raspberry Pi OS).
I upgraded few days ago from U1 to U1.1 and since this update (besides numerous reboots), I lost the ability to connect to the shares through its Netbios name.
It works by typing the IP address but not anymore through its Netbios name...
However, the TrueNAS CORE appears in the Network section of the Windows explorer.
When I'm clicking on it, it answers "Windows cannot access to \\ARIANE". I tried also its aliases but it doesn't work...
By typing \\10.0.0.5, I'm able to connect to shares once I provided the correct credentials.
I checked in Services > SMB > Configure that the option Local Master is enabled. The workgroup is correct too.
Here is the NetBIOS Name: Ariane
NetBIOS Alias: Ariane, ariane, ARIANE (the last alais is the one that is displayed in the network from Windows)
By reading different threads on NetBIOS issue, I added in the Auxiliary Parameters:
But it doesn't change anything.
I didn't change the default configuration of Network > Global configuration.
NetBIOS-NS is unchecked
mDNS and WS-Discovery are checked
Hostname is Ariane. Domain is local.
I tried with another Windows 10 machine, I'm able to access its shares by using its alias (here \\Ouranos) so the issue seems to be linked to TrueNAS CORE.
Any idea? What can I try?
Thanks a lot.
I upgraded beginning of January from FreeNAS 11.3 to TrueNAS-12.0-U1 with no noticeable issue except the fact I destroyed the GELI encrypted pool to be compatible with the new encryption system.
I'm used to access SMB shares through the Netbios name of the TrueNAS server or one of its aliases.
My network clients are mostly Windows 10 plus several Linux clients (e.g. Raspberry Pi OS).
I upgraded few days ago from U1 to U1.1 and since this update (besides numerous reboots), I lost the ability to connect to the shares through its Netbios name.
It works by typing the IP address but not anymore through its Netbios name...
However, the TrueNAS CORE appears in the Network section of the Windows explorer.
When I'm clicking on it, it answers "Windows cannot access to \\ARIANE". I tried also its aliases but it doesn't work...
By typing \\10.0.0.5, I'm able to connect to shares once I provided the correct credentials.
I checked in Services > SMB > Configure that the option Local Master is enabled. The workgroup is correct too.
Here is the NetBIOS Name: Ariane
NetBIOS Alias: Ariane, ariane, ARIANE (the last alais is the one that is displayed in the network from Windows)
By reading different threads on NetBIOS issue, I added in the Auxiliary Parameters:
domain master = Yes
preferred master = Yes
os level = 65
But it doesn't change anything.
I didn't change the default configuration of Network > Global configuration.
NetBIOS-NS is unchecked
mDNS and WS-Discovery are checked
Hostname is Ariane. Domain is local.
I tried with another Windows 10 machine, I'm able to access its shares by using its alias (here \\Ouranos) so the issue seems to be linked to TrueNAS CORE.
Any idea? What can I try?
Thanks a lot.