Samba 4.16 Released For Improving Windows File/Print Server Interoperability

[phoronix]

Phoronix: Samba 4.16 Released For Improving Windows File/Print Server Interoperability

Samba 4.16 is out as the newest feature release for this leading SMB / CIFS implementation for improving Windows file/print interoperability with Linux-based systems...

https://www.phoronix.com/scan.php?page=news_item&px=Samba-4.16-Released

[aufkrawall]

They practically made SMB1 unusable in smbclient long before this release, which also affected KIO or GvFS. Really annoying when you just want to use your old NAS in a private, isolated network. Pretty much worse than Microsoft...

[RahulSundaram]

They practically made SMB1 unusable in smbclient long before this release, which also affected KIO or GvFS. Really annoying when you just want to use your old NAS in a private, isolated network. Pretty much worse than Microsoft...

Wouldn't an older and long term supported distro be suitable for this purpose? Samba is always going to be distinctly better because they had to reverse engineer much of that protocol and made the corresponding details including the source code entirely freely available.

[numacross]

Wouldn't an older and long term supported distro be suitable for this purpose? Samba is always going to be distinctly better because they had to reverse engineer much of that protocol and made the corresponding details including the source code entirely freely available.

I thought Samba didn't reverse engineer the protocols since Microsoft was forced to share the details in the 2007 EC settlement. Microsoft also routinely hosts SMB interoperability labs, but I don't know if Samba developers attend those.

[david-nk]

They practically made SMB1 unusable in smbclient long before this release, which also affected KIO or GvFS. Really annoying when you just want to use your old NAS in a private, isolated network. Pretty much worse than Microsoft...

You can easily access SMB1 shares by passing -o vers=1.0 to the mount command (although that doesn't use Samba). Windows 10 meanwhile straight out refuses to access SMB1 shares.

[onlyLinuxLuvUBack]

You can easily access SMB1 shares by passing -o vers=1.0 to the mount command (although that doesn't use Samba). Windows 10 meanwhile straight out refuses to access SMB1 shares.

If you have problems with accessing network files, your device may still be using the SMB version 1 protocol, which may have been automatically uninstalled on Windows 10 due to its security concerns. For issues in Windows 10 versions ,please check the Microsoft Support Site. This might be the reason why you can no longer connect to routers, Network-Attached Storage (NAS) via SMB.

Here we provide you a temporary solution which allows you to enable the SMBv1 protocol to regain access to files stored within the network.
If you do not have the direct access to the device running the SMB service, please follow the steps below to temporarily enable the SMBv1 protocol for the purpose of retrieving your files:
Step 1. Open Control Panel in your PC/Notebook.
Step 2. Click on Programs.
Step 3. Click on Turn Windows features on or off link.

Step 4. Expand the SMB 1.0/CIFS File Sharing Support option.
Step 5. Check the SMB 1.0/CIFS Client option.

Step 6. Click the OK button.
Step 7. Click the Restart now button.
After completing the above steps, you will be able to connect to network devices running the SMBv1 protocol on your local network by your Windows 10 computer.

[ermo]

They practically made SMB1 unusable in smbclient long before this release, which also affected KIO or GvFS. Really annoying when you just want to use your old NAS in a private, isolated network. Pretty much worse than Microsoft...

FWIW, if you can install wsdd[1] and avahi on your NAS, KIO and GvFS will be able to discover the smb service via avahi and Windows will be able to discover the smb service via wsdd. I've tested it to work with SMB_2.02 (Vista era) and up across several distros and Windows 10.

SMB1 is deprecated for good reason, even if you personally find those reasons burdensome.

[1]: https://github.com/christgau/wsdd

[numacross]

[...]

Or in an administrative PowerShell:

Enable-WindowsOptionalFeature -FeatureName SMB1Protocol,SMB1Protocol-Client -Online

We do love CLIs on Phoronix

[RahulSundaram]

I thought Samba didn't reverse engineer the protocols since Microsoft was forced to share the details in the 2007 EC settlement. Microsoft also routinely hosts SMB interoperability labs, but I don't know if Samba developers attend those.

The settlement came in much after Samba was already established and all that initial effort was based on reverse engineering.

[illwieckz]

The ability to add ports to DNS forwarder addresses in the internal DNS back-end.

Unfortunately the opposite missed the merge, the ability for an internal DNS to forward to Samba by customizing Samba DNS port, this is much wanted:

https://gitlab.com/samba-team/samba/-/merge_requests/2185