Chapter 10: WINS in Name Resolution Design

1
Chapter 10 WINS in Name Resolution Design

• Designs That Include WINS
• Essential WINS Design Concepts
• Name Resolution Protection in WINS Designs
• WINS Design Optimization

2
WINS and Name Resolution

• Windows Internet Name Service (WINS) provides
  NetBIOS over TCP/IP (NetBT) name resolution.
• Other NetBIOS name resolution options include
• HOSTS
• LMHOSTS
• Domain Name System (DNS)

3
WINS and Microsoft Windows 2000

• NetBIOS process
• Name registration
• Name resolution
• Name release
• WINS Client
• WINS Proxy
• WINS Server

4
WINS Design Review

• Amount of data transmitted
• Segments requiring NetBIOS
• Current WAN connections
• Future growth plans

5
WINS Design Decisions

• How to integrate WINS into the network
• How to ensure NetBIOS availability
• How to optimize NetBIOS traffic

6
When WINS Is Required

• Users are running preWindows 2000 and require
  authentication in Active Directory directory
  service
• IP-routed segments require NetBIOS name support
• Applications require NetBIOS name support
• Users are running preWindows 2000 file and print
  services

7
Windows 2000 Without WINS

• WINS is not required for Windows 2000.
• You can eliminate WINS if
• All computers are running Windows 2000
• No applications require NetBIOS
• Active Directory provides authentication

8
Segments Requiring NetBIOS Name Resolution

• Required for
• NetBIOS-based file, print, and application
  servers
• Client computers accessing NetBIOS servers
• Not required for Internet users

9
WINS Client Proxy

• Supports non-WINS clients
• Is the non-WINS client resolution process
• May be required on some network segments

10
WINS Client Options

• Sequence of WINS servers
• WINS node types
• b-node
• p-node
• h-node
• m-node
• LMHOSTS lookup
• HOSTS lookup
• DNS lookup

11
Placing WINS Servers

• One server can support up to 10,000 clients.
• You can specify one or more WINS servers
• One server per location, to reduce WINS traffic
  between locations
• Multiple servers at a single location, to reduce
  traffic between network segments

12
Placing WINS Servers An Example
13
WINS Replication

• Replication is required for multiple WINS
  servers.
• You must determine
• Convergence time
• Replication topology

14
Hub-and-Spoke Replication Model
15
Calculating Convergence Time

• Determine the maximum convergence time.
• Determine the replication schedule.
• Add the cumulative replication hours.
• Identify the longest time between two servers.

16
WINS Replication Partner Types

• Pull partner replication
• Push partner replication
• Push/pull partner replication

17
Protecting the WINS Design

• Restrict the number of administrators.
• Isolate the server from public networks.

18
Improving WINS Availability

• Use Windows Clustering server clusters.
• Use multiple WINS servers with replication.
• Dedicate a computer to running WINS.

19
Improving WINS Performance

• Reduce WINS query resolution time.
• Load balancing
• Burst handling
• Dedicated WINS computer
• Reduce WINS replication traffic.
• Pull partner replication
• Change pull partner interval
• WINS persistent connections

20
Chapter Summary

• WINS services include Client, Proxy, and Server.
• Use WINS for many network designs.
• Use WINS Client options to specify how WINS
  resolves NetBIOS names.
• Use multiple WINS servers.
• Control the convergence time.
• Improve the availability and performance of your
  WINS design.