Comment 45 for bug 1778322

Your reference to the Linux Samba Server command: smbstatus got me thinking what would happen if I disabled NT1 on a Linux Samba server by stipulating "server min protocol = SMB2" and using Windows Network > ... to connect.

The exact same thing happens as when trying to connect to a Win10 machine that's disabled SMBv1.

It a different error message: Invalid Argument ( Linux Server ) vs Network dropped connection on reset ( Windows Server ) but the affect is the same. Connection to the host isn't possible through gvfsd-smb-browse. If I reset the Linux server by removing server min protocol = SMB2 it all works because now NT1 was restored.

Maybe I'm reading too much into your quote:
"Let's force NT1 using the
newly added smbc_setOptionProtocols API if available. But force this
only when neither hostname, nor IP address is used. This among others
prevents complete breakage if NT1 is disabled on server."

Is it possible they knew this would happen?

Linux doesn't disable SMB1 by default in its server but Windows 10 does on new builds.