Mount an SMB/CIFS Share in ownCloud Without a Linux Mount

To access a Windows or Samba share in ownCloud Server, enable the External Storage Support app and add an SMB/CIFS storage mount from the ownCloud administration page. Use the share’s server address, share name, and valid SMB credentials; you generally do not need to mount the share with Linux mount.cifs first.

This method exposes existing network files inside the ownCloud Files interface while preserving permissions enforced by the SMB server. The instructions below apply to the classic ownCloud Server external-storage interface documented for versions 10.16 and 11.0, not ownCloud Infinite Scale.

1. Check the SMB share and ownCloud prerequisites

You need administrator access to ownCloud, a reachable SMB server, a share you are authorized to access, and an SMB account with the necessary read or write permissions. Keep TCP port 445 reachable between ownCloud and the file server, preferably over a trusted private network or VPN rather than exposing SMB to the public internet.

For a concrete example, suppose the SMB server is files.internal.example, the share is Projects, and the service account is ACME\oc-share. The folder to display in ownCloud will be Team Projects. These are fictional values; substitute your real server details.

On a conventional Linux installation, the Samba client and the appropriate PHP SMB client extension may be required. For example, on a Debian-based host, install the command-line test client:

sudo apt update
sudo apt install smbclient

Check which PHP version and installation method ownCloud uses before installing an extension. ownCloud’s Server 10.16 Ubuntu installation instructions describe php7.4-smbclient for their PHP 7.4 setup; use that package only when it matches your actual supported PHP environment and repository. After enabling the extension, restart the PHP service or web server that runs ownCloud, and check module loading with php -m | grep -i smbclient. The command checks CLI PHP; the web process can have a separate configuration.

For the official ownCloud Server 11.0 Docker image, the SMB documentation says runtime SMB dependencies are included, although the image does not include the smbclient command for manual tests. Do not assume the same host-package commands apply inside every container image.

2. Test access from the ownCloud server

Before changing ownCloud settings, test name resolution, authentication, and the share itself from the ownCloud host or its network environment. On a host with smbclient, run:

smbclient -L //files.internal.example -U 'ACME/oc-share'
smbclient //files.internal.example/Projects -U 'ACME/oc-share' -c 'ls'

Enter the SMB account password when prompted instead of placing it in the command line. The first command lists available shares; the second checks access to the specific share. A listing is not proof of write permission. If the command fails, confirm the server name or IP, share spelling, credentials, domain, firewall rules, and effective permissions on the Windows or Samba server before proceeding. The ownCloud SMB/CIFS guide also recommends testing with smbclient before configuration.

3. Enable External Storage Support

1. Sign in to ownCloud with an administrator account.
2. Open Settings → Apps and ensure External storage support is enabled.
3. Go to Settings → Admin → Storage (the navigation labels may differ slightly between interfaces).
4. Enable External Storage if the page presents that checkbox, and use Add storage to select SMB / CIFS.

You do not need to enable Allow users to mount external storage merely to create an administrator-managed share. That separate setting allows users to create their own mounts, potentially including connections to network services the administrator would not otherwise expose. See ownCloud’s External Storage Configuration manual.

4. Configure the SMB/CIFS mount

In the new storage row, supply the connection information. The following example keeps the SMB share name separate from the folder name users see in ownCloud.

Enter oc-share as the username when you have supplied ACME in the separate Domain field. Do not put //files.internal.example/Projects into the Host field, and do not confuse the share name with an optional subfolder. For a remote subfolder, ownCloud supports $user to select an existing directory matching the current ownCloud username; it does not create that directory.

For a common service account, Username and password is straightforward, but its access applies according to that account’s SMB permissions. If users authenticate to SMB with their own matching ownCloud credentials, Log-in credentials, save in session may fit better. However, ownCloud documents important limits with session credentials: background scans and direct sharing of the mounted storage cannot work as they do with stored credentials. Choose based on the actual authentication and scanning requirements, not convenience alone. Refer to External Storage Authentication Mechanisms.

Restrict Available for to the intended ownCloud users or groups; an administrator-created mount is otherwise available to all users by default. If staff only need to browse files, turn on the mount’s Read Only option, and also enforce read-only access on the SMB server. Leave sharing from the mount disabled unless your access policy requires it.

5. Resolve an unavailable mount before using it

Once the required fields are entered, ownCloud automatically saves the storage row. Its green status indicator means the connection is ready; a red or yellow indicator calls for further investigation. ownCloud can mark a failed external storage as unavailable for ten minutes, so click its status indicator or reload the administration page after resolving the underlying problem.

• Authentication failed: Recheck the SMB password, domain, username format, account lockout state, and share permissions. Compare with the smbclient test using the same account.
• Connection timed out: Check DNS, routing, firewall access to TCP 445, and whether the SMB service is running. Test from the same container network if ownCloud is containerized.
• SMB/CIFS backend is missing: Confirm the External Storage Support app is enabled and the required SMB extension is loaded in the PHP runtime that serves ownCloud, where applicable.
• Some folders are absent: Verify the remote subfolder and SMB filesystem permissions. An ownCloud group assignment cannot grant access the remote server denies.
• Externally changed files do not appear: Review the mount’s filesystem check frequency, background jobs, and scanning mechanism. Session-only SMB credentials prevent background scans; avoid scheduling occ files:scan as a supposed fix for that limitation.

A kernel-level CIFS mount exposed back to ownCloud as Local storage is usually the wrong fallback. ownCloud warns that if such a filesystem mount disappears, it may see an empty local directory and propagate deletion events. Use the direct SMB/CIFS backend instead; refer to the official Local Storage warning.

6. Verify the share in Files

Sign in as a user permitted in Available for. Open Files and locate Team Projects. Browse an existing directory and open a small test file. If the SMB account and ownCloud mount both allow writing, upload a harmless test file and verify that it appears on the SMB server; delete it after the check. For read-only mounts, confirm that modification is blocked instead.

Finally, check the storage row stays green after a page reload and that another user outside the permitted group cannot see the mount. These checks establish that ownCloud can reach the correct SMB share, the remote account has the intended access, and the mount is exposed only to its intended audience.