SMBTREE(1)
π SMBTREE(1) π
okay so bestie, this is the manual page for smbtree, a User Commands situation, and it is so much less scary than it looks, i promise π«Ά
β¨ NAME β¨
smbtree β a text based smb network browser π¦
no cap, that's literally it. a browser. for smb. in text. slay.
β¨ SYNOPSIS β¨
smbtree [-D|--domains] [-S|--servers] [-?|--help] [--usage]
[-d|--debuglevel=DEBUGLEVEL] [--debug-stdout] [--configfile=CONFIGFILE]
[--option=name=value] [-l|--log-basename=LOGFILEBASE] [--leak-report]
[--leak-report-full] [-U|--user=[DOMAIN/]USERNAME[%PASSWORD]]
[-N|--no-pass] [--password=STRING] [--pw-nt-hash]
[-A|--authentication-file=FILE] [-P|--machine-pass]
[--simple-bind-dn=DN] [--use-kerberos=desired|required|off]
[--use-krb5-ccache=CCACHE] [--use-winbind-ccache]
[--client-protection=sign|encrypt|off] [-V|--version]
β¨ DESCRIPTION β¨
okay so first thing: this tool is part of the samba(7) suite π
like, it's one of the siblings, it knows people.
smbtree is a smb browser program in text mode. it's giving the "Network Neighborhood" you'd find on Windows computers β you know the vibe π it prints a tree with all the known domains, then the servers in those domains, then the shares on the servers. a whole little family tree of your network, adorable honestly π
β¨ OPTIONS β¨
-D,--domainsβ only print a list of all the domains known on broadcast or by the master browser πΈ-S,--serversβ only print a list of all the domains and the servers responding on broadcast or known by the master browser. so like, domains + servers, the little duo π-?,--helpβ print a summary of command line options. your lil cheat sheet π«Ά--usageβ display brief usage message. the even shorter version, iconic β¨-d,--debuglevel=levelβlevelis an integer from 0 to 10. the default value if this parameter is not specified is 1 for client applications.
the higher this value, the more detail will be logged to the log files about the activities of the server. at level 0, only critical errors and serious warnings will be logged. level 1 is a reasonable level for day-to-day running β it generates a small amount of information about operations carried out.
levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic π like bestie, do not.
note that specifying this parameter here will override thelog levelparameter in the/etc/samba/smb.conffile.
--debug-stdoutβ this will redirect debug output toSTDOUT. by default all clients are logging toSTDERR. lowkey a glow-up for your logs π--configfile=<configuration file>β the file specified contains the configuration details required by the client. the information in this file can be general for client and server or only provide client specific like options such asclient smb encrypt. see/etc/samba/smb.conffor more information. the default configuration file name is determined at compile time β--option=<name>=<value>β set thesmb.conf(5)option "<name>" to value "<value>" from the command line. this overrides compiled-in defaults and options read from the configuration file. if a name or a value includes a space, wrap whole--option=name=valueinto quotes π§-l,--log-basename=logdirectoryβ base directory name for log/debug files. the extension".progname"will be appended (e.g.log.smbclient,log.smbd, etc...). the log file is never removed by the client. it's permanent, it's committed, it's in it for the long haul π--leak-reportβ enable talloc leak reporting on exit π--leak-report-fullβ enable full talloc leak reporting on exit. the deluxe edition π-V,--versionβ prints the program version number π-U,--user=[DOMAIN\]USERNAME[%PASSWORD]β sets the SMB username or username and password.
if %PASSWORD is not specified, the user will be prompted. the client will first check the USER environment variable (which is also permitted to also contain the password separated by a %), then the LOGNAME variable (which is not permitted to contain a password) and if either exists, the value is used. if these environmental variables are not found, the username found in a Kerberos Credentials cache may be used.
a third option is to use a credentials file which contains the plaintext of the username and password. this option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables. if this method is used, make certain that the permissions on the file restrict access from unwanted users. see the -A for more details.
be cautious about including passwords in scripts or passing user-supplied values onto the command line. for security it is better to let the Samba client tool ask for the password if needed, or obtain the password once with kinit.
while Samba will attempt to scrub the password from the process title (as seen in ps), this is after startup and so is subject to a race π¬
-N,--no-passβ if specified, this parameter suppresses the normal password prompt from the client to the user. this is useful when accessing a service that does not require a password π
unless a password is specified on the command line or this parameter is specified, the client will request a password.
if a password is specified on the command line and this option is also defined the password on the command line will be silently ignored and no password will be used. ghosted. blocked. π
--passwordβ specify the password on the commandline.
be cautious about including passwords in scripts or passing user-supplied values onto the command line. for security it is better to let the Samba client tool ask for the password if needed, or obtain the password once with kinit.
if --password is not specified, the tool will check the PASSWD environment variable, followed by PASSWD_FD which is expected to contain an open file descriptor (FD) number.
finally it will check PASSWD_FILE (containing a file path to be opened). the file should only contain the password. make certain that the permissions on the file restrict access from unwanted users! π₯
while Samba will attempt to scrub the password from the process title (as seen in ps), this is after startup and so is subject to a race.
--pw-nt-hashβ the supplied password is the NT hash π-A,--authentication-file=filenameβ this option allows you to specify a file from which to read the username and password used in the connection. the format of the file is:
username = <value>
password = <value>
domain = <value>
make certain that the permissions on the file restrict access from unwanted users! π
-P,--machine-passβ use stored machine account password π€--simple-bind-dn=DNβ DN to use for a simple bind.--use-kerberos=desired|required|offβ this parameter determines whether Samba client tools will try to authenticate using Kerberos. for Kerberos authentication you should use DNS names instead of IP addresses when connecting to a service. by default Samba client tools will try to use the default Kerberos credential cache (ccache). in case the ccache does not exist or-U|--useroption was specified, clients will ask to enter a password and will obtain a Kerberos ticket (kinit) for you. if you want to use an alternative Kerberos credentical cache, use the--use-krb5-ccacheoption β¨
note that specifying this parameter here will override theclient use kerberosparameter in the/etc/samba/smb.conffile.
--use-krb5-ccache=CCACHEβ specifies the credential cache location for Kerberos authentication.
this will enforce --use-kerberos=required π
like, it's not asking.
--use-winbind-ccacheβ try to use the credential cache by winbind πΈ--client-protection=sign|encrypt|offβ sets the connection protection the client tool should use.
note that specifying this parameter here will override theclient protectionparameter in the/etc/samba/smb.conffile.
in case you need more fine grained control you can use: --option=clientsmbencrypt=OPTION, --option=clientipcsigning=OPTION, --option=clientsigning=OPTION. so many options bestie, it's giving β¨customizationβ¨
β¨ VERSION β¨
this man page is part of version 4.24.7 of the Samba suite π¦
β¨ AUTHOR β¨
the original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed π
the smbtree man page was written by Jelmer Vernooij π
and that's the whole thing bestie, tysm for reading, ilysm π
Samba 4.24.7 Β· 09/09/2026 Β· SMBTREE(1) β mwah, xoxo, go browse some shares ππ¦π
π¦ where this page comes from
- fedora 44: samba-client 2:4.24.7-1.fc44 Β· GPL-3.0-or-later AND LGPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms