SMB1 has been disabled by default for security reasons. If legacy clients are no longer able to connect, type this command in the Shell, then restart the SMB service: ``
If that resolves the issue, you can make that setting permanent by going to System → Tunables →Add Tunable and creating a Tunable with these settings:
I was not able to get the FreeNAS SMB share to mount in Nextcloud, even with FreeNAS set to allow SMB1. It is still giving me an error. I ended up switching to NFS for the mount. I hope somebody can modify the External Storages plugin to use SMB2 or allow you to choose the SMB protocol, as using SMB1 is pretty insecure.
Thanks for the response. I did select the extra security options when setting up the VM. Do you know what I need to do to turn off ModSecurity on the Tech and Me VM?
I was also impacted by this error on Ubuntu 16.04 with Nextcloud 13.0.5. To fix the problem while keeping FreeNAS 11.1-U6 SMB1 disabled, I updated, installed smbclient and modified smb.conf like this:
sudo apt update
sudo apt install smbclient
add in global section smb.conf (/etc/samba/smb.conf):
client min protocol = SMB2
client max protocol = SMB3
@enoch85 I deployed a new instance of Nextcloud with the latest Tech and Me OVA and did not enable any of the security features or extras. It is still not able to mount an SMB share from FreeNAS.
This same problem of upgrading FreeNAS to 11.1-U6 affected my Nextcloud’s External Storages app, too.
I cannot use the workaround of installing smbclient as described by Raegedoc above, because of the SMB downloading of large files issue described in this github issue. It seems that the PHP implementation of SMB is preferred by Nextcloud.
I think I’ll downgrade the security of SMB on my FreeNAS server because the PHP implementation of SMB in Nextcloud is not keeping up.
@ShaunCurrier Please let me know if you are able to get it working with FreeNAS. I tried downgrading my SMB to allow SMB1 and I am still having the same problem.
SMB access has been partially broken for over a year- the last version that completely works is 10. @enoch85 has worked extensively with us on it and verified that it’s a bug.
Not stating that this is the cause of your issue, just that there are certainly some SMB issues with versions 11 and 12.
SMB all over Linux distros have been broken. I had an issue on CentOS and Fedora with Thecus NAS where system would hang with mass rename operations. Nothing pertaining to NC. Reverting and forcing SMB v1 protocol fixed it. So I don’t think this is specifically NC’s fault, the thing is broken everywhere.
