I used general settings, no change in ACLs.
When first logging in, I had, of course, to input my user name and password. I tick the box for permanent access. As a result, I was able to access the shared network folder as follows:
In a second step, I mapped the folder accordingly to drive “U” (not to drive “Z”, as shown in the sample picture below) to get immediate access from my Windows machine without logging in every time anew.
However, the network assignment seems to be not permanent: After a PC shutdown and restart, a fault message is shown (see attachment) and access to the shared folder is blocked.
Translation: “path not available. Cannot access U:\ - wrong user name or password”
As I could not find any related information or solution in the forum, I therefore asks my question here: What am I doing wrong? Any idea? link?
One reason for the malfunction may have been the case-sensitive servername. According my TrueNAS system info, there exist two different values:
TrueNAS hostname: Myserver-One
NetBIOS Name: MYSERVER_ONE
Windows 11 shows the NetBIOS Name and not the TrueNAS hostname. I tried to map the drive using the NetBIOS Name but that was obviously the wrong decision! The mapping requires the TrueNAS hostname and not the NetBIOS Name, right?
That might have been the reason why I had to login each anew each time after shutdown and restart of my PC. I think I should read about the differences between these two things
There is no Truenas hostname.
There is a NETBIOS name for the NETBIOS namespace, and there is a DNS name for IP name resolution. Both are case insensitive. However, DNS only allows letters, digits and the minus sign “-” in names, while NETBIOS allows some more special characters, e.g. the underscore “_”. You are STRONGY(!!!) advised to only use the DNS character set, i.e. change the _ to an -.
You need a working name resolution method in your network, i.e. DNS. All members of your LAN should be configured to use this. WINS is already obsolete, don’t use this.
Connecting using the numerical IP address should always work.
Try
net use x: \192.168.x.x\share
instead of using the GUI.
net use x: /d removes a share.
I fully agree with your proposal to use numerical IP addresses instead of names, but … why is “hostname” used here? IMHO, this leads to misunderstandings.
I wasn’t aware of the character set differences that fchk wrote about.
I will rework all my net device names in order to be consistent.
You never stop learning!
I get it. The string “hostname” is what the server believes is its DNS name. It’s nothing Truenas special. Your local DNS server should be able to resolve this name to the proper IP address in both directions.
Netbios name resolution is deprecated.
Btw.
C:\Windows\System32\drivers\etc\hosts is for DNS name resolution and uses DNS names.
C:\Windows\System32\drivers\etc\lmhosts is for NETBIOS name resolution and uses NETBIOS names.
This dates back to the mid-80’s. lm stands for the OS/2 LAN Manager, Mirocsoft’s and IBM’s fileserver solution at this time.
In case of Windows reporting an incorrect password, you might have to change your Windows security settings: Local Security Policy → Local Policies → Security Options → Network security: LAN Manager authentication level → Send NTLMv2 response only
This Worked for me Instantly.
It’s from the TrueNas Documentation Directly.
