External storage support with windows server 2022 showing not all files / folders

[wolftobias]

Describe the bug

I'm using Ubuntu 22.04 / ownCloud 10.13.4 (stable) in a docker container and mysql 8 in a docker container with enabled external smb storage.
The external storage became green after configuration, but when I login as the user itself in the user space, it shows only the root file share but not all sub files/folders! This happens for some user, but one user has some subfolders but not everthing is showing up.

I tried so far:

• smbclient from inside the owncloud docker container is fine, everything is browseable and like it should be.
• I have updated the docker container with apt-get and tried to update smbclient/php.
• I have disabled all unneeded apps like sharing, federation etc.
• Enabled "Windows Network Drive" Enterprise Feature is working, but it's not desired!!!

My Docker config
docker run --name owncloud --network="intern" --restart=always
-e OWNCLOUD_ADMIN_USERNAME=root
-e OWNCLOUD_ADMIN_PASSWORD=xxx
-e OWNCLOUD_DB_TYPE=mysql
-e OWNCLOUD_DB_NAME=owncloud_db
-e OWNCLOUD_DB_USERNAME=owncloud
-e OWNCLOUD_DB_PASSWORD=xxx
-e OWNCLOUD_DB_HOST=mysql
-e OWNCLOUD_SUB_URL=/owncloud
-e OWNCLOUD_TRUSTED_DOMAINS="xxx"
-d -p 8082:8080 owncloud/server

docker run --name mysql --network="intern" --restart=always -e MYSQL_ROOT_PASSWORD=xxx -v bind-address=0.0.0.0 -d -p 3306:3306 -p 33060:33060 mysql:latest

[iasdeoupxe]

Is this more a support question for https://central.owncloud.org/ ? e.g.:

https://doc.owncloud.com/server/10.15/admin_manual/configuration/files/external_storage/configuration.html#detecting-files-added-to-external-storages

10.3.4 now also a little bit outdated, maybe updating to https://owncloud.com/changelog/server/#changelog-for-owncloud-core-10150-2024-06-18 could help as well?

[DeepDiver1975]

🤖 Automated issue triage by Claude Code review agent.

Thanks for the detailed report. After reviewing the thread, this looks like an environment / SMB-stack issue rather than a located defect in ownCloud core code, so I want to be transparent about that and point at what would actually move it forward.

Why it points at the SMB layer, not core:

• You confirmed smbclient from inside the container browses everything correctly. The smbclient CLI binary and the PHP path ownCloud's free SMB external-storage backend uses (icewind/smb → libsmbclient via php-smbclient, falling back to the smbclient wrapper) are different code paths with different dialect/SUID/listing behavior. A working CLI but a failing PHP listing is the classic signature of an SMB protocol-negotiation / library mismatch, not a core bug.
• The fact that the Enterprise "Windows Network Drive" app works for the same share is another strong signal: WND uses a different connection/listing implementation, so the share, credentials, and network path are fine — the difference is in how the free SMB backend negotiates and lists.
• The behavior is inconsistent per user ("some subfolders but not everything"). A deterministic core bug would fail uniformly. Per-user/per-folder visibility differences point at SMB ACLs/permissions on the Windows Server 2022 host (the listing user can stat the share root but is denied or partially denied on specific subtrees), or directory entries the backend skips during enumeration.

Likely contributing factors on Windows Server 2022 specifically:

• SMB dialect negotiation (WS2022 prefers SMB 3.1.1; older libsmbclient builds negotiate differently) and SMB signing/encryption requirements.
• libsmbclient / php-smbclient version in the container vs. what WS2022 expects.
• NTFS ACLs on the subfolders that don't appear.

Information that would help confirm a root cause:

1. ownCloud log (data/owncloud.log, loglevel 0/debug) entries while a user opens the share where folders are missing — any Icewind\SMB exceptions or skipped-entry warnings.
2. php -m | grep smbclient and the libsmbclient/smbclient package versions inside the container.
3. Whether the missing subfolders share a common trait (special characters in names, different ACL owner, symlinks/DFS, very large directories).
4. The negotiated SMB dialect (e.g. smbclient -m SMB3 vs default) and whether forcing a dialect changes the result.
5. A test against current ownCloud 10.15.x — 10.13.4 is several releases behind and SMB-related fixes have landed since.

Given there's no reproducible, located core-code cause here and it depends heavily on the SMB stack and Windows Server 2022 configuration, the most productive venue is likely https://central.owncloud.org/ with the logs above. If the debug log reveals a specific enumeration/dialect bug in the icewind/smb path, please share it here (or open a fresh issue against a current release) and we can dig into the code path directly.

[dj4oC]

Before this can be acted on, the following needs to be resolved:

• No reproducible core defect located: smbclient from inside the container browses the SMB share correctly, and the Enterprise "Windows Network Drive" app works against the same share — both point at the free SMB external-storage backend's (icewind/smb) protocol negotiation/listing behavior on Windows Server 2022 rather than a bug in ownCloud core's file-listing logic.
• Missing diagnostic data: data/owncloud.log (loglevel 0/debug) entries during a listing that misses subfolders, the php-smbclient/libsmbclient version in use, and whether the missing subfolders share a common trait (special characters, distinct ACL owner, symlinks/DFS) have not been provided.
• The report is against ownCloud 10.13.4, several releases behind current — needs confirmation the issue still reproduces on a current release before further investigation.

🤖 Automated by Claude Code

---

Generated by Claude Code