The
file contains information about the computers, users, and shares
or mount points for the
SMB
network protocol.
The configuration hierarchy is made up of several sections,
each section containing a few or several lines of parameters
and their assigned values.
Each of these sections must begin with a section name enclosed within
square brackets, similar to:
The end of each section is marked by either the start of a new section,
or by the abrupt ending of the file, commonly referred to as the
EOF
Each section may contain zero or more parameters such as:
where
key
represents a parameter name, and
value
would be the parameter's assigned value.
The
SMB
library uses the following information for section names:
A)
Bq Li default
B)
Bq Ar SERVER
C)
Bq Ar SERVER : Ns Ar USER
D)
[SERVER : USER : SHARE
]
Possible keywords may include:
KeywordSectionComment
A B C D
addr Ta - + - - Ta IP or IPX address of SMB server
charsets Ta - + + + Ta local:remote charset pair
nbns Ta + + - - Ta address of NetBIOS name server (WINS)
nbscope Ta + + - - Ta NetBIOS scope
nbtimeout Ta + + - - Ta timeout for NetBIOS name servers
password Ta - - + + Ta plain text password used to access the given share
retry_count Ta + + - - Ta number of retries before connection is marked as broken
timeout Ta + + - - Ta SMB request timeout
workgroup Ta + + + + Ta workgroup name
FILES
/etc/nsmb.conf
The default remote mount-point configuration file.
EXAMPLES
What follows is a sample configuration file which may,
or may not match your environment:
# Configuration file for example.com
[default]
workgroup=SALES
# The 'FSERVER' is an NT server.
[FSERVER]
charsets=koi8-r:cp866
addr=fserv.example.com
All lines which begin with the
`#'
character are comments and will not be parsed.
The
``default
''
section describes the default workgroup or domain, in this case
``SALES
''
The next section depicted here as
``FSERVER
''
defines a server section and then assigns it a charset which is only
required when Cyrillic characters are not used.
The hostname value,
``fserv.example.com
''
is also assigned in this section.
COMPATIBILITY
At the time of this writing, the
IPX
protocol remains unsupported.
Future
Fx releases are expected to support this.
