set up a samba share on Ubuntu 20-04

 

https://www.techrepublic.com/article/how-to-create-a-samba-share-on-ubuntu-server-20-04/

--30--

Error 53, or not available error on Windows 10

Microsoft in their infinite wisdom have horribly broken SMB1 functionality on Windows 10.  No simple way to turn it back on, nor any explanation of why it is broken.

When you try to connect to a share via the protocol \\192.168.1.1\share you get an error not available, or an error 53.

The page below is an extended explanation of the justification, FWIW.  If there was a comprehensible error or change there would be less sarcasm and criticism here,  but just removing an insecure and broken protocol that they invented which was wrong and not putting in a way to recover when a release upgrade is made is just nuts.

When you upgrade to the 1709 creator release, or so, you will see this happen with your shares that have SMB1 and no SMB2 version support.  FWIW, I believe the latest and approved SMB is 4. 

https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-windows-10-and-windows-server-version-1709

Knowledge base workaround to re-enable it or get it back

https://support.microsoft.com/en-us/help/2696547/how-to-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and-windows-server

seems to be in the same spot you enable and install the Ubuntu shell support

Windows server





Windows 8 and 10



-30-

Workaround for when windows shares have bad credentials

Not sure if this is the correct way to remove badly credentialed shares, but a start

When you have a device on a network share and get the login incorrect, there seems to be no way to remove the bad "guess" or login so you can retry or correctly enter a password.  This is via the GUI access to shares.

This may be a way to force the credential to go away, by using a command line net command to remove it.  Untried thus far, but may work.

Execute "net use" in windows cmd box.
It will display all the links.
Run following command to remove your PI's link:

net use /D \\192.168.0.165\share

Then retry the access.
30