Module 5: WINS as a Solution for NetBIOS Name Resolution v
• Explain that when using multiple WINS servers, the locally acquired
entries must be replicated to configured partners. Caution students that
multicast announcements between WINS servers add traffic to the
network.
• Make sure that students understand the scenario description and the
instructions for the Discussion. Direct them to read through the scenario
and answer the questions. Be prepared to clarify if necessary. Lead a
class discussion on the students’ responses.
Securing a WINS Solution
Because replication and client traffic often occur across public networks, the
security of the NetBIOS names and IP addresses of hosts within the
organization is at risk. A WINS solution can be secured by using Layer Two
Tunneling Protocol (L2TP)/Internet Protocol Security (IPSec) or Point-to-
Point Tunneling Protocol (PPTP)-based virtual private network (VPN)
tunnels. There may also be scenarios that would benefit from the integration
of WINS servers into screened subnets.
In this section:
• Stress that the decision whether to use L2TP/IPSec or PPTP VPN
tunnels must be based on the existing network configuration and the
public networks used to transfer data.
• Point out that screened subnets can be used to avoid exposing NetBIOS
names and WINS data to a public network. Suggest students consider
using pull replication only if replication is required from the WINS
server in the screened subnet to the WINS server(s) within the corporate
intranet. Remind students that a Common Internet File System (CIFS)
and WINS solution is simple by comparison to Web-based solutions.
Enhancing a WINS Design for Availability
Ideally, a WINS Service would be available whenever it is required. To
enhance the availability of the service, a WINS solution can be designed to
provide support for multiple WINS servers that use WINS replication, and
to include WINS servers that are configured to use Windows Clustering.
In this section:
• Emphasize that when using multiple WINS servers, the placement of
servers depends on the network infrastructure, service performance, and
location constraints. Point out that adding additional WINS servers to
remote locations provides name service redundancy in case a server
fails.
• Emphasize that installing WINS servers on a cluster provides immediate
recovery in the event of hardware or service failure.
• Make sure that students understand the scenario description and the
instructions for the Discussion. Direct them to read through the scenario
and answer the questions. Be prepared to clarify if necessary. Lead a
class discussion on the students’ responses.
vi Module 5: WINS as a Solution for NetBIOS Name Resolution
Optimizing a WINS Design for Performance
Reducing response times to client requests, and reducing the time taken to
replicate between servers, can maximize the performance of the WINS
service.
In this section:
• Emphasize that WINS in Windows 2000 supports the use of multiple
CPUs, an optimized database, burst-mode client registrations, and
multiple WINS servers to optimize the performance of the WINS
service.
• Point out that replication traffic between servers in a multiple-server
environment reduces the performance of the WAN links. Emphasize that
the replication schedule can be planned to minimize replication traffic
while meeting the goals for convergence time.
Lab Strategy
Use the following strategy to present this lab.
Lab A: Designing a WINS Solution
In the lab, students will design a WINS solution based on specific requirements
outlined in the given scenario.
Students will review the scenario and the design requirements and read any
supporting materials. They will use this information, and the knowledge gained
from the module, to develop a detailed design that uses WINS as a solution.
To conduct the lab:
Read through the lab carefully, paying close attention to the instructions and
the details of the scenario.
Divide the class into teams of two or more students.
Present the lab and make sure students understand the instructions and the
purpose of the lab.
Direct students to use the planning worksheet to record their solutions.
Remind students to consider any functionality, security, availability, and
performance criteria provided in the scenario, and how they will incorporate
strategies to meet these criteria in their design.
Allow some time to discuss the solutions after the lab is completed. A
solution is provided in your materials to assist you in reviewing the lab
results. Encourage students to critique each other’s solutions and to discuss
any ideas for improving their designs.
Module 5: WINS as a Solution for NetBIOS Name Resolution 1
Overview
Introducing WINS
Designing a Functional WINS Solution
Securing a WINS Solution
Enhancing a WINS Design for Availability
Optimizing a WINS Design for Performance
The use of network basic input/output system (NetBIOS) names in a
Transmission Control Protocol/Internet Protocol (TCP/IP) network requires
resource names to be resolved throughout a network infrastructure. WINS in
Microsoft
® Windows® 2000 implements an RFC-compliant NetBIOS name
service (NBNS).
At the end of this module, you will be able to:
Evaluate WINS as a solution for NetBIOS name resolution.
Evaluate and create a functional design for baseline name resolution.
Select appropriate strategies to secure a WINS solution.
Select appropriate strategies to enhance a WINS design for availability.
Select appropriate strategies to improve a WINS design for performance.
Slide Objective
To provide an overview of
the module topics and
objectives.
Lead-in
In this module, you will
evaluate and design WINS
solutions for locating
NetBIOS resources.
2 Module 5: WINS as a Solution for NetBIOS Name Resolution
Introducing WINS
Design Decisions
WINS Features
Integration Benefits
A
A
B
B
Share
Shared
Resource
Windows
Clients
Exchange
Server
Windows 95
Using NetBIOS
Client Running
Outlook
NetBIOS name resolution is
required by many clients
Within an organization’s intranet, the potentially large number of available
NetBIOS resources, such as file and print services, creates the need for
meaningful device and logical resource names to simplify the user’s access to
resources. WINS resolves NetBIOS resource names to IP addresses. WINS can
also integrate with other Windows 2000 services to extend name resolution
capabilities.
To design a strategy for locating NetBIOS resources by using WINS, you must:
Collect the network and host configuration data required to make the design
decisions necessary for developing a WINS solution.
Identify the features provided by WINS and how these features support the
design requirements.
Identify the benefits provided by integrating WINS with other services in
Windows 2000.
Slide Objective
To introduce WINS as a
solution for NetBIOS name
resolution.
Lead-in
NetBIOS permits client
computers to access
network hosts by using a
NetBIOS name instead of
the host’s IP address. WINS
translates the NetBIOS
name to the resource IP
address.
Explain that a network host
can be defined as any
device or computer that
participates in a TCP/IP
network. Host may describe
a client or server.
Module 5: WINS as a Solution for NetBIOS Name Resolution 3
Design Decisions for a WINS Solution
Establishing the Need for WINS
Identifying the Design Decisions
File
Servers
Exchange
Server
Broadcast
Domain
Broadcast
Domain
NetBIOS
CD Server
WAN Link
Router
Router
To successfully develop a WINS solution, you must assess the number of hosts,
the number of resources, and the routing or network configuration. When you
understand the configuration of the network, resources, and hosts for the
infrastructure, you can make decisions on the requirements for a WINS-based
NetBIOS name resolution service.
Establishing the Need for WINS
In a TCP/IP routed or switched network, where broadcast packets may not pass
between segments, a nonbroadcast-based service is required to accommodate a
dynamic NetBIOS name resolution and registration service. WINS meets this
service need by providing unicast NetBIOS name registration and resolution.
In a simple, nonrouted TCP/IP network, such as a single-segment local
area network (LAN), WINS may be optional. A non-WINS solution works in
those instances where the broadcast domain is small, broadcast traffic is
acceptable, and hosts are configured as b-node (broadcast nodes).
Identifying the Design Decisions
After you have established the network infrastructure requirements and
configuration, the design decisions you must make include the:
Number and placement of WINS servers within the network.
Plan for replication schedules, and architecture and configuration options
for multi-WINS server environments.
Configuration of WINS Client.
Placement of WINS Proxy Agents to ensure unique non-Windows host
names.
Slide Objective
To introduce the decisions
required for a WINS
solution.
Lead-in
The design of a NetBIOS
name resolution service
based on WINS depends on
the number of hosts, the
number of resources, and
the network configuration.
Use the slide to discuss the
decisions required to design
a WINS solution.
Explain that WINS is not
required in a single-segment
LAN within a single
broadcast domain, but is
beneficial in any
environment to reduce the
dependence on broadcast
traffic.
Note
4 Module 5: WINS as a Solution for NetBIOS Name Resolution
Features of a WINS Service
Name Resolution Services
RFC Compliance
DNS Integration
Burst-Mode Name Registration
Secure and Centralized
Administration
Multiple WINS Servers
WINS
Server
WINS Client
WINS Client
Register
Renew
Release
Resolve
WINS Database
Client1 10.0.1.11
Client2 10.0.3.12
Client3 10.0.3.13
Remove
When designing a WINS-based NetBIOS name resolution service, you must
understand the WINS features and how you can use these features to support
the needs of your network infrastructure.
Name Resolution Services
A WINS infrastructure builds and maintains a database of available NetBIOS
resources and resolves NetBIOS names to IP addresses based on client requests.
WINS accomplishes name resolution in four distinct phases:
Registers new network device names as they become available.
Resolves NetBIOS names to IP addresses for WINS clients.
Renews name registrations for WINS clients.
Releases NetBIOS names during normal WINS client computer shutdown.
And, in addition, the WINS service:
Removes names from the registration database if the client fails to renew its
entries.
RFC Compliance
WINS provides NetBIOS name service support that is compliant with RFC
1001 and RFC 1002. The implementation of WINS in Windows 2000 extends
the RFC-compliant NetBIOS name service by supporting multiple distributed
servers with replicated databases.
DNS Integration
To fulfill DNS client queries, the WINS service integrates with DNS in
Windows 2000 to allow forward and reverse lookup of NetBIOS resources by
DNS servers. You can also configure WINS clients to support name resolution
by using both DNS and WINS records.
Slide Objective
To introduce the features in
WINS.
Lead-in
To develop a WINS solution,
you need to understand the
WINS features.
Mention that this is not a
complete list of the WINS
features; additional features
will be discussed later.
Module 5: WINS as a Solution for NetBIOS Name Resolution 5
Burst-Mode Name Registration
When a large number of WINS clients simultaneously try to register their
NetBIOS names, the WINS server can become saturated. Burst-mode name
registration supports a high volume of WINS client name registrations.
By default, when the queue of registration requests exceeds 500, a WINS server
begins to positively respond to new registration requests with a shorter (5 – 50
minutes) Time to Live (TTL). The short TTL lease forces these WINS clients to
reregister after the excessive WINS registration traffic has subsided.
Secure and Centralized Administration
You can centrally administer WINS, thereby reducing name resolution–related
support issues. WINS clients automatically register and release their NetBIOS
names, so no other administration is necessary. Administration is secure
because only specific Windows 2000–based groups can modify a WINS server
configuration or database.
Multiple WINS Servers
WINS provides a critical service for the network, so availability and
performance are key design goals. Multiple WINS servers provide greater
availability and improve the performance of any WINS implementation. The
WINS architecture supports multiple servers that you can configure to replicate
their database information. In addition, you can configure WINS clients with a
list of available WINS servers that are sequentially referenced in the case of a
server failure.
6 Module 5: WINS as a Solution for NetBIOS Name Resolution
Integration Benefits
DHCP Integration
DNS Integration
DHCP
Server
DNS
Server
Name Registration
Name Resolution
WINS
Server
WINS clients that have DHCP-allocated IP addresses must be registered in
WINS to allow other clients to resolve resources. The integration of WINS with
other Windows 2000 networking services such as DHCP and DNS allows the
other services to use these dynamic registrations.
The integration of WINS with DHCP and DNS allows:
DNS servers to forward unresolved DNS queries to WINS servers for
resolution of host names that have dynamic IP addresses.
DNS resolution for resources located on other operating systems, such as
previous versions of Microsoft Windows.
In addition to the server-to-server integration, you can configure the
WINS client to query a DNS server with unresolved WINS queries.
DHCP Integration
The integration of WINS and DHCP allows client computer name registrations
to be updated in WINS for clients with dynamically allocated IP addresses. This
automated registration eliminates manual administration and configuration
errors.
You can select registration of the NetBIOS names in WINS to be completed by:
The DHCP Client.
The DHCP Server.
The DHCP Client and DHCP Server.
Slide Objective
To describe the benefits of
integrating WINS with other
services in Windows 2000.
Lead-in
WINS integrates with other
services in Windows 2000,
such as DHCP and DNS.
This integration allows the
other services to use
dynamic registrations.
Emphasize that the
integration of DHCP, WINS,
and DNS solves a major
networking issue by
providing DNS name
resolution for hosts with
dynamic IP address
allocations.
Note
Module 5: WINS as a Solution for NetBIOS Name Resolution 7
DNS Integration
The integration of WINS and DNS allows you to select whether DNS can use
WINS to resolve host names. This integration allows resources not registered in
DNS to be resolved in the WINS namespace. The DNS server then returns the
resource’s IP address to the querying DNS client.
8 Module 5: WINS as a Solution for NetBIOS Name Resolution
Designing a Functional WINS Solution
Designing a WINS Service for a LAN
Designing a WINS Service for a Routed Network
Supporting WINS Clients
Supporting Non-WINS Clients
Supporting Multiple WINS Servers
Discussion: Evaluating WINS Functional Requirements
You can create a WINS design for a LAN or routed network that supports both
WINS and non-WINS clients. If multiple WINS servers are required, you can
create a solution to control replication of the WINS databases between partners.
Slide Objective
To provide an overview of
the network configurations
in which WINS can be used
as a solution.
Lead-in
You can design a WINS
solution for a LAN or a
routed network that supports
WINS or non-WINS clients.
You can incorporate multiple
WINS servers if required.
Không có nhận xét nào:
Đăng nhận xét