Hi @Krisztian.Lamar ,
NA9D is right — running an older release leaves you exposed to issues that have already been fixed upstream, so moving off 5.1.3 is worth doing regardless of the Samba question. QTS 5.1 reached end of support in November 2024, so for stability and security we’d recommend moving to a current, supported release. (You can cross-check the lifecycle status for any release on QNAP’s Product Support Status page: Product Support Status | QNAP)
On the Samba version specifically, here’s the honest picture so you can plan around it:
-
QTS 5.1.x and QTS 5.2.x both run on the Samba 4.15 line. What 5.2 adds is our maintenance approach: when a CVE or a Samba security fix appears, we back-port it onto that stable 4.15 branch rather than jumping the whole package, so it stays aligned with the surrounding toolchain and libraries. That gets you the security fixes, but it stays on 4.15 — so upgrading 5.1 to 5.2 won’t get you to 4.17.
-
The newer Samba release (4.20, comfortably above the 4.17 you’re after) ships with the QTS 6.0 line, which also moves to kernel 6 and a refreshed toolchain / rootfs / glibc.
On your specific model: we’re confirming with our development team, and the current plan is for the TS-133 to pick up Samba 4.20 through the QTS 6 release targeted for Q4.
In the meantime, one thing that would genuinely help: you mentioned needing the changeable SMB volume serial number in smb.conf. Could you tell us a bit more about what depends on it in your setup — the software or workflow that keys off that serial number? That helps when we take this request back to the team.