Why does Windows 10 2004 not open a network folder by PC name, but opens by IP?

Question

Computer networks

Situation: there is a simple network, without domains, all in one workgroup, a simple router (Mikrotik =)).
The network is a simple NAS (NetGear ReadyNAS Pro 2), network having, unexpectedly, nas.
Computers on the network are different, operating systems from WinXP to Win 10.
Dozens have support for older versions of SMB (nas does not see it without it).
Everything worked fine.

But then the WIn10 PCs that got the latest big update (2004) stopped accessing nas.
At the same time, they do not enter by network name, but come by IP. Also, the network printer connected to nas does not work by name from these PCs, but works by IP.
Interestingly, the NAS pings by name, you can also enter the web interface by name.
Here are the tips -https://winitpro.ru/index.php/2018/05/16/0x8007003... - I tried it, but it works, then no.

The problem is only on a PC with Win10 version 2004, on other dozens everything is fine.
I also noticed that nas network folders open if you plug in not \\nas, but \\nas.local, but if it suddenly opens along the first (without locale) path, it does not open along the second.
Access to other PCs from normally problematic

ones UPD: It's funny, after some of the NAS's manipulations over the network, the PC stopped opening by IP, but opens by the name 0_0

Answer 1

https://support.microsoft.com/en-us/help/3181029/s...

To resolve this issue on a file server that is running the SMB version 1 protocol, add the DisableStrictNameChecking value to the registry:
Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
DWORD name: DisableStrictNameChecking
DWORD value: 1

In short, the SMB 1 protocol that yours uses is outdated and netbios does not work correctly.
What can be done
- go by IP
- register a DNS name in hosts on this computer
- raise your DNS on the network
- try updating the NAS, disable support for outdated SMB

Answer 2

Set up a normal dns server in LAN and go through dns names

Answer 3

In a similar situation - access to Ubuntu via SMB 1.0 was lost after updating to Windows 2004 - manual setting of the parameter in the registry helped: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth=1. Interactively in gpedit.msc Enable insecure guest logins was set, but the registry didn't seem to be set.

Answer 4

Enable support for legacy versions of the SMB protocol.
https://winitpro.ru/index.php/2018/01/24/ne-otkryv...

Answer 5

And it helped me just to add .local to the storage network name. That is, \\n2310.local - and it worked.