Windows 10: NetBios names in Windows 11

I have a NAS named BlackArmor with IP address 192.168.4.150. My hosts and lmhosts files contain the mapping blackarmor = 192.168.4.150 and using lmhosts for NetBios names is enabled. Prior to the upgrade from Windows 10 to Windows 11, I could map folders on my NAS to drives using \\blackarmor\foldername. After the upgrade, if I use that reference I get an error message that the network name is no longer available, but if I use \\192.168.4.150\foldername, it works, and what is displayed for the drive mapping is \\blackarmor\foldername. Why can't the system find \\blackarmor when setting up the

:)

 

Netbios and resolving local DNS names

Yes. I was only suggesting that you to edit the LMHosts file rather than the Hosts file.

 

Netbios and resolving local DNS names

The aforementioned registry locations and netstat results apparently indicate that Windows has lost the connection between the network adapters and the netbios function. Windows apparently can't resolve ip to names when there is no connection to the LAN for that function to obtain the required information.

 

Netbios

I've seen lots of problems with Windows 10 and Netbios. I am unable to netbios from a win 10 machine to any other. Works fine from a Windows 7 machine. I've tried every single change I could find for the registry, firewall, hosts, lmhosts, you name it and
I've tried it. Still I cannot netbios from Windows 10 to any other machine, regardless of OS.

I'd love a fix/solve for the problem but there does not seem to be one. I have a need to access machine via the \\machinename\c$ (or IP\c$) method. However, if I am unable to get this to work and if the future has no ability to do the above, then the next
question is - what is the replacement?