Siemens Unix V4.0 - Manual (Page 208)

Implementing WINS Planning for WINS Server Implementation
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
10
10.2 Planning for WINS Server Implementation
The number of WINS servers that an enterprise requires is based on the number of WINS
client connections per server and the network topology. The number of users that can be
supported per server varies according to usage patterns, data storage, and processing
capabilities of the WINS server computer.
Planning for WINS server implementation on the network typically requires consideration of
the issues presented in the following table:
Planning issue Guideline
How many WINS servers are
required to ensure distribution of
name query and name registration
loads throughout the network? The location of routers on the network and the
distribution of clients in each subnet should be
considered first when deciding how many WINS
servers are required. There is no builtin limit for the
number of NetBIOS names that one WINS Server
can handle.
See the following sections:
“Planning for WINS
Client Network Traffic” , “Planning for WINS Server
Performance” and “Planning Replication Partners
and Proxies” .
Is the WAN bandwidth sufficient to
support WINS server and WINS
client name registration traffic? See the next section, “Planning for WINS Client
Network Traffic” .
How many WINS servers are needed
for disaster recovery, backup, and
redundancy requirements? See the following sections: “Planning for WINS
Server Fault Tolerance” and “Planning for WINS
Server Performance” .
How can a planned distribution of
WINS servers throughout the
network be validated before instal-
lation? When planning a network configuration, a
generally accepted approach is to consider the
consequences of two simultaneous failures at
different points on the network.