H
Hale_ru
A week or two ago (around NewYear 2019) my Win10 based laptop stopped seeing local network machines using SMB2 protocol. Accessing shares by explicit machine names works fine.
Before that I had no problems with listing active machine names. Nothing was changed from my side; but windows 10 updates itself without prompting, or telling what it plans to update... so probably it was damaged from Microsoft side.
SMB1 was disabled long ago.
There is a forced master browser NAS/Router with SAMBA working 24x7. SMB2 protocol is forced for shares. Higher SMB versions are not supported there. Domain controller features are not used - only master browser and WINS(nmbd). Access is based on user name/password in all the network. DNS (dnsmasq) is also configured for local network domain suffix. i.e. Both WINS and DNS fulfill dynamic LAN name resolution with no problems.
In windows 10 SMB2 seems enabled, but unable to get network resource listing from SAMBA master browser.
PS C:\windows\system32> Get-SmbServerConfiguration | Select EnableSMB2Protocol
EnableSMB2Protocol
------------------
True
All the firewalls are configured for private LAN with file sharing and I also tried disabling(opening) the firewalls inside the LAN.
When installing SMB1 client on WIn10, and allowing SMB1 in SAMBA, the network machine listing revives. But still, it is not correct, since SMB1 is deprecated and not supported by default in Windows anymore.
Is there a way to bring SMB2 LAN machine listing back to life on Windows 10?
Continue reading...
Before that I had no problems with listing active machine names. Nothing was changed from my side; but windows 10 updates itself without prompting, or telling what it plans to update... so probably it was damaged from Microsoft side.
SMB1 was disabled long ago.
There is a forced master browser NAS/Router with SAMBA working 24x7. SMB2 protocol is forced for shares. Higher SMB versions are not supported there. Domain controller features are not used - only master browser and WINS(nmbd). Access is based on user name/password in all the network. DNS (dnsmasq) is also configured for local network domain suffix. i.e. Both WINS and DNS fulfill dynamic LAN name resolution with no problems.
In windows 10 SMB2 seems enabled, but unable to get network resource listing from SAMBA master browser.
PS C:\windows\system32> Get-SmbServerConfiguration | Select EnableSMB2Protocol
EnableSMB2Protocol
------------------
True
All the firewalls are configured for private LAN with file sharing and I also tried disabling(opening) the firewalls inside the LAN.
When installing SMB1 client on WIn10, and allowing SMB1 in SAMBA, the network machine listing revives. But still, it is not correct, since SMB1 is deprecated and not supported by default in Windows anymore.
Is there a way to bring SMB2 LAN machine listing back to life on Windows 10?
Continue reading...
