Windows 10: How do you download SMB2 protocol into Windows 11?

I am getting this Windows error message when I try to open up an external hard drive. "An error occurred while reconnecting Y: to \\MYCLOUDEX2Ultra\Public Microsoft Windows Network: You can't connect to the file share because it is not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack. Your system requires SMB2 or higher. For info on resolving this issue, see: https://go.microsoft.com/fwlink/?linkid=852747 This connection has not been restored."Microsoft helped me get rid of the SMB1 feature unchecking box, etc., but did

:)

 

The Mapped Network Drive could not be Created because:..obsolete SMB1 Protocol.. Needs SMB2?

:..obsolete SMB1 Protocol.. Needs SMB2? What do I need to do?

 

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.***

 

How to user SMB2 on Windows?

Hi,

I have a problem accessing my Synology DS218J NAS from my Windows 10 desktop. I get the following error when I try to access it.





The NAS is working fine, as I can access the web portal from the same desktop. I can also access the NAS from other laptops and mobile devices.

I tried using a Linux VM to connect to the NAS via smbclient: "smbclient-U galapogos -L <host>" and I get the error "protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE"

After googling on the Windows/Linux error codes, it seems to indicate a SMB1 error, but I didn't think it would be because both the Windows desktop and the NAS have SMB1 disabled.

But, just to confirm, I tried to force SMB2/SMB3 on Linux via smbclient: "smbclient -m SMB2/SMB3 -L <host>" AND BOTH SMB2/SMB3 WORKED!

So, it does seem that Windows is not using SMB2/3? How do I force it system wide? Or, is there an smbclient on Windows that I can try to use to confirm the problem?

I've already disabled SMB1 in Windows Features.





I've also disabled it in the registry via PowerShell commands and verified that it's not there in the registry.





So, does anyone know how to FORCE Windows to use SMB2/SMB3 like I can with smbclient in Linux?