▶ Support intro Nextcloud version (eg, 12.0.2): 13.0.5.2 Operating system and version (eg, Ubuntu 17.04): Ubuntu 18.04.1 LTS (Tech and Me Appliance) Apache or nginx version (eg, Apache 2.4.25): 2.4.29 PHP version (eg, 7.1): 7.2.7 The issue you are facing: I am using the Tech and Me appliance and …

Hi oRAirwolf, Today I got the newly released 18.04/Nextcloud 14.0 1TB from Tech and Me and retried without changing anything to the default configuration and it worked! I didn’t have to install smbclient like I previously did in my 16.04/NC13 version. Instead, I played around and changed the way …

Hi oRAirwolf, 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 …

Thank you for the response. I am running the Tech and Me Ubuntu 18.04 VM. That is good to know that it fixed it for Ubuntu 16.04, though.

@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 implem…

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

@oRAirwolf I followed your steps by adding the Tunable to FreeNAS, and after stop/start of SMB service I am now able to access my CIFS shares.

Are you using the Tech and Me appliance? I tried with mine and I am still getting diddly.

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.

For you to know, I had to revert to SMB1 since my HP printer scan2folder “feature” stopped working because of SMB2. I am not in the mood of buying a new printer for now :frowning: