Setting up Samba as a Standalone Server — by SambaWiki

intermediatepageLink only (©)

SambaWiki guide to running Samba on a Linux box that is not in a domain, with one guest share and one password-protected share. It covers creating smb.conf, Samba users, groups, share permissions with setgid, validating with testparm and testing with smbclient. Guest shares are flagged as a security risk, and recent Windows clients may refuse guest access over SMB2/3.

Quick steps

Write smb.conf with server role = standalone server
Create the local user and add it with smbpasswd -a
Create the share directories and set group ownership and chmod 2770
Check the file with testparm -s, start smbd, then test with smbclient

Paraphrased from the source. Menus can differ by version, so check the original for full details.

Read the full article on wiki.samba.org

Source: Setting up Samba as a Standalone Server by SambaWiki. Licence: Link only (©).

Source reviewed: 2026-11-02
Link checked: Not yet
Tested hands-on: Not by Oddbyte.Me

sambasmblinuxnaspermissions

More in NAS & Network Shares

Can't connect to SMB share "Windows cannot access" — by Dan Jackiels on Microsoft Q&A

beginnerforum

A quick fix for a NAS share that Windows refuses to open: stale saved credentials. The answer deletes the NAS entries from Credential Manager and reconnects. One commenter says it fixed things in seconds, while another reports it did not work for them.

Detect, enable, and disable SMBv1, SMBv2, and SMBv3 in Windows — by Microsoft Learn

intermediatepage

Microsoft's reference for checking and changing SMB protocol versions on clients and servers. It says SMBv1 has serious security flaws and is not installed by default in Windows 11 or Server 2019 and later, so old NAS boxes should be updated rather than re-enabling it. It also warns that SMB signing is required by default on Windows 11 24H2 and Server 2025, which can block connections to some third-party servers.

Unable to connect to SMB1 NAS drives with NET USE after KB5065429/KB5065426 updates — by IGYQ on Microsoft Q&A

intermediateforum

A thread about a legacy NAS that stopped mapping after the September 2025 Windows cumulative updates. The answer explains the client now rejects SMB1 negotiation, offers re-enabling the SMB1 client as a not-recommended workaround, and advises updating the NAS firmware to SMB2/3. A second reply says Microsoft has begun blocking even manual re-enabling, and the original poster's NAS had no newer firmware, so replacing it may be the only fix.