Configuring Advanced Server for UNIX Configuring NetBIOS
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k05
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 co nfiguring 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, t h e loca l m ac hi n e mu st al re a dy b e a bl e t o f in d t h e PD C! )
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 Ki t
Networking Guide”.
5.1.4 Configuring NetBIOS Tunable ParametersOn Advanced Server for UNIX computers, NetBIOS services are provided by two
STREAMS drivers which are linked to the UNIX kernel during NetBIOS install ation.
Following is a list of tuning variables which are used to control the behavior of Net BIOS (for
the default values refer to the /etc/conf/cf.d/mtune file). Note that a NetBIOS upgrade insta l-
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