A practical Samba setup problem for a home file server
A Debian 12 server is sharing several network folders and whole drives through the official Samba package. Windows, Android, and Linux devices all connect to those shares. The basic setup works, but the first was hard because the available felt scattered, repetitive, and mixed with old settings.
Sometimes all connections drop, and the Samba daemon has to be restarted by hand. Windows user access is also troublesome, because Samba-created users are not working as expected, so access is handled by forcing one user in the config or allowing guest access. A separate file browser and sync system are already in place, so the need is only a simple UI for managing Samba shares, not a large all-in-one server platform.
The practical question is whether to keep running Samba directly on the server or move to a management UI or another tool.
Key points
- The server runs Debian 12 with the official Samba package.
- It shares whole drives and folders with Windows, Android, and Linux devices.
- Samba setup feels difficult because the is hard to follow and includes outdated material.
- Connections sometimes drop until the Samba daemon is manually restarted.
- The desired tool is a simple UI for Samba shares, not a full file manager or sync platform.