Contents Overview 1 Introducing WINS 2 Designing a Functional WINS Solution 8 Securing a WINS Solution 19 Enhancing a WINS Design for Availability 22 Optimizing a WINS Design for Performance 27 Lab A: Designing a WINS Solution 31 Review 38 Module 5: WINS as a Solution for NetBIOS Name Resolution Information in this document is subject to change without notice. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Complying with all applicable copyright laws is the responsibility of the user. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. If, however, your only means of access is electronic, permission to print one copy is hereby granted. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.  2000 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, ActiveX, BackOffice, FrontPage, JScript, MS-DOS, NetMeeting, PowerPoint, Visual Basic, Visual C++, Visual Studio, Win32, Windows, Windows Media, Windows NT, are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries/regions. Project Lead: Don Thompson (Volt Technical) Instructional Designers: Patrice Lewis (S&T OnSite), Renu Bhatt NIIT (USA) Inc. Instructional Design Consultants: Paul Howard, Susan Greenberg Program Managers: Jack Creasey, Doug Steen (Independent Contractor) Technical Contributors: Thomas Lee, Bernie Kilshaw, Joe Davies Graphic Artist: Kirsten Larson (S&T OnSite) Editing Manager: Lynette Skinner Editor: Kristen Heller (Wasser) Copy Editor: Kaarin Dolliver (S&T Consulting) Online Program Manager: Debbi Conger Online Publications Manager: Arlo Emerson (Aditi) Online Support: Eric Brandt (S&T Consulting) Multimedia Development: Kelly Renner (Entex) Production Support: Lori Walker (S&T Consulting) Manufacturing Manager: Rick Terek (S&T OnSite) Manufacturing Support: Laura King (S&T OnSite) Lead Product Manager, Development Services: Bo Galford Lead Product Manager: Ken Rosen Group Product Manager: Robert Stewart Other product and company names mentioned herein may be the trademarks of their respective owners. Module 5: WINS as a Solution for NetBIOS Name Resolution iii Instructor Notes This module provides students with the information and decision-making experience needed to develop a solution for resolving network basic input/output (NetBIOS) names by using WINS in Microsoft ® Windows® 2000. Students will evaluate and create WINS solutions for the name resolution of NetBIOS resources in Transmission Control Protocol/Internet Protocol (TCP/IP) networks. At the end of this module, students 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. Upon completion of the lab, students will be able to evaluate and design WINS solutions that meet the requirements for resolving NetBIOS names in a variety of organizations. Course Materials and Preparation This section provides you with the materials and preparation needed to teach this module. Required Materials To teach this module, you need the following materials:  Microsoft PowerPoint® file 1562B_05.ppt Preparation Tasks To prepare for this module, you should:  Review the contents of the module.  Be familiar with RFCs 1001 and 1002.  Review any relevant information in the Windows 2000 Help files, the Windows 2000 Resource Kit, or in documents provided on the Instructor CD.  Review the discussion material and be prepared to lead class discussions on the topics.  Complete the lab, and be prepared to elaborate beyond the solutions found there.  Read the review questions, and be prepared to elaborate beyond the answers provided in the text. Presentation: 45 Minutes Lab: 45 Minutes iv Module 5: WINS as a Solution for NetBIOS Name Resolution Module Strategy Use the following strategy to present this module:  Introducing WINS The use of NetBIOS names in a TCP/IP network requires resource names to be resolved into IP addresses. WINS provides an RFC-compliant NetBIOS Name Service (NBNS) to resolve resource names throughout a network infrastructure. In this section: • Reinforce the continuing need for WINS in networking environments that have NetBIOS resources. • Emphasize that the first steps in designing a WINS solution are to establish the need for WINS, and to identify the design decisions. The design decisions depend on the number of hosts, the number of resources, and the network configuration. • Review the four distinct phases of name resolution provided by the WINS service in Windows 2000: registration, resolution, renewal, and release. Mention that WINS removes names if the client fails to renew its entries. • Emphasize that the integration of WINS with DHCP and DNS solves a major networking issue by providing DNS name resolution for hosts with dynamic IP address allocations.  Designing a Functional WINS Solution A functional WINS solution supports both WINS and non-WINS clients in a local area network (LAN) or a routed network. A WINS solution can be designed to control replication of the WINS databases when multiple WINS servers are required. In this section: • Highlight that WINS uses a unicast protocol, thereby eliminating NetBIOS-related broadcast traffic in a LAN. Emphasize that client counts and response times depend on the configuration of the hardware. • Point out that the unicast protocol used by WINS meets the routed network requirement for a nonbroadcast-based NetBIOS name service. Emphasize that client performance issues, and the requirements for redundancy and replication, determine the number and placement of WINS servers. • Emphasize that all versions of Windows support a WINS client component. Explain that this component further reduces broadcast traffic. • Emphasize that non-WINS clients can be supported by including WINS Proxy Agents and static WINS or Lmhosts entries, and by enabling NetBIOS traffic across all routers. 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. [...]... redundancy in case a server or router fails Adding WINS Servers with Replicated WINS Databases You can configure multiple WINS servers to provide redundancy and load balancing When you use replication, all servers contain the same WINS database information Timely WINS Database Replication Highly available WINS implementation designs call for timely WINS database replication As the length of time for synchronizing... redundant WINS databases increases, the probability increases that a WINS server failure will result in the use of an outdated database by the remaining WINS servers For WINS servers that are experiencing a significant delay in database replication, consider: Reducing the length of time between WINS database replications Replacing the existing WINS server with a server that provides enhanced performance... 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 Module 5: WINS as a Solution for NetBIOS Name Resolution 9 Designing a WINS Service for a LAN Slide Objective To describe the factors to consider when designing a WINS solution for a. .. scenario describes an organization’s current network configuration Read through the scenario and then answer the questions Be prepared to discuss your answers with the class Scenario An organization has decided to restructure an existing network and include WINS as a solution for NetBIOS name resolution You are assigned the task of evaluating how WINS can be used to provide a solution for this scenario... configuration provides: Intranet access to all shared folders and Web-based applications Support for the existing infrastructure shown in the diagram Support for a mission-critical Web-based application that requires 24-hoursa-day, 7-days -a- week operation Support for a non -WINS compliant CD server by using NetBIOS access in Subnet 3 Support for non -WINS clients 18 Module 5: WINS as a Solution for NetBIOS. .. changes to the database Convergence Time Convergence time is the time it takes for a new entry in a WINS database to be replicated from the originating WINS server to all other partner WINS servers When planning placement and replication for WINS servers, you must decide an acceptable convergence time for your network 16 Module 5: WINS as a Solution for NetBIOS Name Resolution To minimize replication... file, or add a static entry to the WINS database Module 5: WINS as a Solution for NetBIOS Name Resolution 19 Securing a WINS Solution Slide Objective To describe strategies available in Windows 2000 that secure WINS traffic Internet WINS Server Lead-in Many multi-server WINS implementations may be required to operate across unsecured networks such as the Internet; therefore, you must give consideration... connections To allow NetBIOS operation through a firewall, enable these ports Refer to RFC 1002 for further details 22 Module 5: WINS as a Solution for NetBIOS Name Resolution Enhancing a WINS Design for Availability Slide Objective To provide an overview of design options that improve WINS availability Primary WINS Server Lead-in WINS Server Cluster Ideally, the WINS Service would be available whenever... Intranet access to all shared folders and Web-based applications at all locations Internet access to all locations Support for the existing infrastructure as shown in the preceding diagram Support for a remote access server in Subnet 3 that provides VPN access for the Internet Support for a mission-critical Web-based application that requires 24-hoursa-day, 7-days -a- week operation Isolation of the organization's... Non -WINS client registrations are not added to the WINS database automatically To resolve these resources network-wide, you must manually add the registrations as a static entry to the WINS database, or include them in client Lmhosts files Static name entries for non -WINS resources that are added to the WINS database allow WINS clients to resolve these resources In Windows-based computers that use TCP/IP, . students will be able to:  Evaluate WINS as a solution for NetBIOS name resolution.  Evaluate and create a functional design for baseline name resolution. . broadcast packets may not pass between segments, a nonbroadcast-based service is required to accommodate a dynamic NetBIOS name resolution and registration