Configuring Advanced Server for UNIX
Configuring NetBIOS
Product Manual
U7613-J-Z815-6-76
©
S
iem
e
n
s
N
ix
dor
f
In
fo
rm
at
io
n
s
s
y
s
te
m
e
A
G
1
9
9
5
P
fad
: D:
\O
7
613
e6
\u
761
3e
.k
05
5.1.3.4
Guidelines for configuring name resolution
Since WINS is the preferred method of name resolution, it is recommended to use WINS
whenever possible. This section contains simple guidelines for configuring static name
mappings for a particular Advanced Server computer in situations where WINS servers are
not used. In what follows, “PDC” denotes a Primary Domain Controller and “BDC” denotes
a Backup Domain Controller.
Within a domain, a PDC must be able to find all BDCs:
Within a domain, each BDC must be able to find its PDC:
(Note that when installing a BDC, the local machine must already be able to find the PDC!)
Before setting up a trust relationsship between two domains, the two PDCs must be able to
find each other:
If Windows NT servers are part of your domain – either as PDC or BDC – and WINS is not
used, keep in mind that similar rules apply for LMHOSTS files. For more information about
the LMHOSTS file, see Windows NT Help and the “Microsoft Windows NT Resource Kit
Networking Guide”.
5.1.4
Configuring NetBIOS Tunable Parameters
On Advanced Server for UNIX computers, NetBIOS services are provided by two
STREAMS drivers which are linked to the UNIX kernel during NetBIOS installation.
Following is a list of tuning variables which are used to control the behavior of NetBIOS (for
the default values refer to the
/etc/conf/cf.d/mtune
file). Note that a NetBIOS upgrade instal-
lation may change the default values for a tunable parameter in the
mtune
file, but does not
change local settings in the
stune
file.
NBMAXNAMES
default: 140, min: 40, max: 4096
NBRFCCACHE
default: 16, min: 0, max: 4000
Template:
BDC
nnn.nnn.nnn.nnn UN #0,20
Template:
PDC
PDC.DOM
nnn.nnn.nnn.nnn UN #0,20
nnn.nnn.nnn.nnn UN #1b
Template:
OTHERPDC
OTHERPDC.DOM
OTHERPDC.DOM
nnn.nnn.nnn.nnn UN #0,20
nnn.nnn.nnn.nnn UN #1b
nnn.nnn.nnn.nnn GR #1c