Windows 10: Cannot access Win10 machine via local network

I am 'birthing' my first Win10 machine, OS V1809, and must have goofed something up...

All machines in my home belong to the same Workgroup and the users/passwords are consistent across all machines. From my Win7 desktop, I:

• Can access my Win10 machine, via Explorer, using its IP address
• Can ping the Win10 machine using both its name and IP address
• Cannot access the Win10 machine, via Explorer, using its name

From the Win10 machine, I can see all other computers on the network and access all of them.

I do not believe that this is a firewall issue as the issue persists when the firewall is disabled. I do believe that network and file sharing is enabled (but, I could be wrong). The issue exists with both the Ethernet and WiFi connections, so it is probably not interface-specific.

Please suggest what I can do to resolve this issue. Thx.

:)

 

Local network SNAFU

The XP machines still do not show, and I cannot access the Win10 machine from them. Although the Win10 m/c shows in the network list I get a similar 'you do not have access permissions to this computer' message

 

Cannot access 32 bit machines in Network

I recently upgraded to Win10 on 2 of my 32 bit machines and I cannot access them via the network.

My 64 bit machine is ok after the upgrade.

Therefore when will Microsoft issue an update to enable 32 bit machines to access the local network.

I would add that my Win7 and Win8.1 machines 32 bit all work ok on my network.

Deric

 

Unable to locate network machines while using SMBv2 protocol

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?

***Modified title from: Win10 stopped listing home network machines through SMB2 protocol.***