Module 3: Configuring and Managing WINS

8/14/2019 Module 3: Configuring and Managing WINS

1/35

Module 3: Configuring

and Managing WINS


2/35

Module Overview

Overview of the Windows Internet Name Service

Managing the WINS Server

Configuring WINS Replication

Migrating from WINS to DNS


3/35

Lesson 1: Overview of the Windows InternetName Service

When Is WINS Required?

Overview of WINS Components

WINS Client Registration and Release Process

What Is Burst Handling?

WINS Server Name Resolution Process What Are NetBIOS Node Types?

Demonstration: Installing and Configuring a WINS Server


4/35

When Is WINS Required?

WINS is required for the following reasons:

Older versions of Microsoft operating systems rely onWINS for name resolution

Some applications, typically older applications, rely onNetBIOS names

When you need dynamic registration of single-label names

If users rely on the Network Neighborhood or My NetworkPlaces network browser features

If you are not using Windows Server 2008 as your DNS

infrastructure


5/35

Overview of WINS Components

Subnet 1

Subnet 2

WINSServer

WINSServer

WINSDatab

ase

WINSDatab

ase

WINSProxy

WINSProxy

WINSClient

WINSClient


6/35

WINS Client Registration and Release Process

WINS Client

WINS Client WINS Server

WINS Server

NameRegistered

NameRegistered

NameReleased

NameReleased

WINS client sends request to register

WINS server returns registration message with TTL value,indicating when the registration expires

1

WINS client sends request to release name

WINS server sends a positive name release response

2


7/35

What Is Burst Handling?

WINS clientregistrations exceedthe burst queue threshold

1 WINS acknowledgesregistrations with a shortrenewal interval

2

Burst handling allows a WINS server to handle a high

number of simultaneous name registration requests

Burst handling allows a WINS server to handle a high

number of simultaneous name registration requests


8/35


9/35

What Are NetBIOS Node Types?

Node type Description Registryvalue

B-node Uses broadcasts for name registrationand resolution

1

P-node Uses a NetBIOS name server, such asWINS, to resolve NetBIOS names

2

M-node Combines B-node and P-node, butfunctions as a B-node by default

4

H-node Combines P-node and B-node, butfunctions as a P-node by default

8

A NetBIOS node type determines the method that acomputer uses to resolve a NetBIOS nameA NetBIOS node type determines the method that acomputer uses to resolve a NetBIOS name


10/35

Demonstration: Installing and Configuring aWINS Server

In this demonstration, you will see how to install the

WINS server feature and configure burst handling


11/35

Lesson 2: Managing the WINS Server

Overview of Client Records

Demonstration: Filtering and Viewing Recordsin WINS

How Scavenging Works

Deleting WINS Records

Backing Up and Restoring the WINS Database

Compacting the WINS Database

Demonstration: Managing the WINS Server Database


12/35

Overview of Client Records

The service that registeredthe entry, including thehexadecimal type identifier

The IP address that corresponds to theregistered name

Displays x to indicate whether theentry is static and displays null oris blank if the entry is not static

The WINS server from which theentry originates

The registered NetBIOS name, which canbe a uniquename, or a group, internet group, ormultihomed computer

The state of the databaseentry, which can be active,released, or tombstoned

A unique hexadecimal numberthat the WINS server assignsduring name registration

Shows when the entrywill expire

A WINS client record includes the following information:A WINS client record includes the following information:


13/35

Demonstration: Filtering and Viewing Recordsin WINS

In this demonstration, you will see how to filter and

view records in the WINS database


14/35

How Scavenging Works

Scavenging removes extinct entries from the WINS databaseScavenging removes extinct entries from the WINS database


15/35

Deleting WINS Records

To delete obsolete records, you can update theWINS database by:

Simple deletion. Records selected by using the WINSconsole are removed from the current localWINS server

Tombstoned deletion. Records are marked fordeletion, replicated to other WINS servers, and thenremoved during the next scavenging operation


16/35

Backing Up and Restoring the WINS Database

You can restore the WINS database torecover from a corrupt databaseYou can restore the WINS database torecover from a corrupt database

To back up a WINS database:

To restore a WINS database:

Specify a backup directory

Back up manually or configure automatic backups

Stop the WINS service

Manually delete and restore database files


17/35

Compacting the WINS Database

Maintain WINS database integrity by using:

Dynamic compacting. Automatically occurs while the

database is in use

Offline compacting. Administrator stops the WINS serverand uses the Jetpack.exe command-line tool

Compacting recovers unused space in a WINS databaseCompacting recovers unused space in a WINS database

D t ti M i th WINS S


18/35

Demonstration: Managing the WINS ServerDatabase

In this demonstration, you will see how to configure

a WINS Backup and compact a WINS Database


19/35

Lesson 3: Configuring WINS Replication

What Is Push Replication?

What Is Pull Replication?

What Is Push/Pull Replication?

Demonstration: Configuring WINS Replication PartnerProperties

Checking WINS Database Consistency


20/35

Notificationsent

Notificationsent

2Replicationrequest

Replicationrequest

3 Replicas sentReplicas sent4 ServerB

What Is Push Replication?

A push partner notifies replication partners based on the numberof changes in its database

Push replication maintains a high level of synchronization

ServerA reaches set threshold of 50 changes in its database1

ServerA notifies ServerB that the threshold is reached2

ServerB responds to ServerA with a replication request3

ServerA sends replicas of its new database entries4

ServerA

Subnet 1Subnet 250 changes

occur indatabase

50 changes

occur indatabase

1


21/35

Replicas sent2 Requests changesevery eight hours

1ServerB

What Is Pull Replication?

A pull partner requests replication based on a time interval

Pull replication limits frequency of replication traffic acrossslow links

ServerA requests database changes every 8 hours1

ServerB sends replicas of its new database entries2

ServerA

Subnet 1Subnet 2


22/35

What Is Push/Pull Replication?

Push/pull replication ensures that the databases onmultiple WINS servers are nearly identical at anygiven time by:

Notifying replication partners whenever thedatabase reaches a set threshold of changes

Requesting replication based on a set time

Demonstration: Configuring WINS Replication


23/35

Demonstration: Configuring WINS ReplicationPartner Properties

In this demonstration, you will see how to configure

WINS Replication Partner properties


24/35

Checking WINS Database Consistency

Checking WINS database consistency helps maintaindatabase integrity among WINS servers in a large network

Checking WINS database consistency helps maintaindatabase integrity among WINS servers in a large network

WINS Server

WINS Server

WINS Server


25/35

Lesson 4: Migrating from WINS to DNS

Name Resolution for a Single-Label Name

What Is the GlobalNames Zone?

How GlobalNames Zone Name Resolution Works

Setup Requirements for Implementing the GlobalNamesZone

Demonstration: Migrating from WINS to DNS Using theGlobalNames Zone


26/35


27/35

The GlobalNames zone:

What Is the GlobalNames Zone?

Enables Single-Label name resolution for IPV6enabled networks

Uses CNAME records to point to the FQDN of the computerthat hosts the resource

Is recommended to be integrated in Active Directorywith forest-wide replication

Can be a used as a method to decommission WINS servers

Requires no additional client configuration because theclient resolves the name in standard DNS query form


28/35

How GlobalNames Zone Name Resolution Works

No changes are made to the client machine configuration

The client queries DNS in the standard format

If the DNS query fails (CNAME record does not exist), theresolution process proceeds per the client configuration







Setup Requirements for Implementing the


29/35

Setup Requirements for Implementing theGlobalNames Zone

Functions of Content Advisor include:

Requires authoritative name servers runningWindows Server 2008

Configure forest-wide, Active Directory-integratedreplication of the GlobalNames zone

Create static CNAME records that point to FQDN records

Disable dynamic updates on the GlobalNames zone

Enable single-label GlobalNames zone support on allDNS servers that host the zone

Use the following command to enable support for the GlobalNameszone on all DNS servers hosting the zone:dnscmd /config /EnableGlobalNamessupport 1

Use the following command to enable support for the GlobalNameszone on all DNS servers hosting the zone:dnscmd /config /EnableGlobalNamessupport 1

Demonstration: Migrating from WINS to DNS


30/35

Demonstration: Migrating from WINS to DNSUsing the GlobalNames Zone

In this demonstration, you will use the GlobalNames

zone to migrate from WINS to DNS


31/35

Lab: Configuring a WINS Infrastructure

Exercise 1: Installing WINS

Exercise 2: Configuring WINS Burst Handling

Exercise 3: Configuring WINS Replication

Exercise 4: Migrating from WINS to DNS

Logon information

Virtual machines NYC-DC1 and NYC-SVR1

User name AdministratorPassword Pa$$w0rd

Estimated time: 60 minutes


32/35

Lab Review

True or False: You only are required to have WINSservices available for down-level or legacy Windows

operating systems.

Can Windows clients dynamically register NetBIOS single-label names in the GlobalNames DNS zone?

When using the Push/Pull replication options for WINS

servers in your environment, what WINS topology doesthis replication type best support?


33/35

Module Review and Takeaways

Review Questions

Considerations for WINS Services

Best Practices

Tools

Notes Page Over-flow Slide Do Not Print Slide


34/35

Notes Page Over flow Slide. Do Not Print Slide.See Notes pane.

Notes Page Over-flow Slide Do Not Print Slide


35/35

Notes Page Over flow Slide. Do Not Print Slide.See Notes pane.

Documents

Module 3: Configuring and Managing WINS