Samba File Server Configuration (SMB/CIFS)
The Windows Network Drive Listener only supports version 1 of the SMB protocol with earlier Samba versions.
A Samba server, often a Microsoft Windows Server, can enforce the minimum and maximum protocol versions used by connecting clients. However, in light of the WannaCry ransomware attack, Microsoft patched Windows Server to only allow SMB2 protocol by default (as SMB1 is insecure).
The ownCloud windows network drive listener utilizes the SMB notification feature which works well with SMB1 in conjunction with most Samba versions. However, when the minimum protocol a server accepts is SMB2, ownCloud require Samba 4.7.8+ (4.8+ etc.) to be able to properly work, as prior versions of Samba had a bug that break this feature.
There are two dependencies to connect to your ownCloud installation to Windows file servers,
ownCloud’s SMB/CIFS backend requires either the libsmbclient-php module (version 0.8.0+) or the smbclient command (and its dependencies) to be installed on the ownCloud server.
We highly recommend
libsmbclient-php, but it isn’t required.
If it is installed smbclient won’t be needed.
Most Linux distributions provide
libsmbclient-php and typically name it
The Samba client must be installed on your Linux system.
It is included in all Linux distributions; on Debian, Ubuntu, and other Debian
derivatives this is
On SUSE, Red Hat, CentOS, and other Red Hat derivatives it is
You also need
stdbuf, which should be included in most Linux distributions.
When configuring it, you will need the following information:
The folder name, which will be your local mount point.
The URL of the Samba server.
The username or domain/username used to login to the Samba server.
The password to login to the Samba server.
The share name to mount on the remote Samba server.
The remote subfolder inside the remote Samba share to mount. This is optional, as it defaults to
To assign the ownCloud logon username automatically to the subfolder, use
$userinstead of a subfolder name.
The ownCloud users and groups who get access to the share.
Optionally, you can specify a