Module 7: Resolving NetBIOS Names by Using Windows Internet Name Service (WINS)

Overview Multimedia: The Role of WINS in the Network Infrastructure Installing and Configuring a WINS Server Managing Records in WINS Configuring WINS Replication Managing the WINS Database

Multimedia: The Role of WINS in the Network Infrastructure The objective of this presentation is to provide a high-level overview of WINS in the network infrastructure. At the end of this presentation, you will be able to: Explain the role of WINS in the network infrastructure Describe how WINS resolves NetBIOS names Describe the WINS registration process Describe how WINS replication works

Lesson: Installing and Configuring a WINS Server The Components of WINS What Is a NetBIOS Node Type? How a WINS Client Registers and Releases NetBIOS Names How Burst Handling Works How a WINS Server Resolves NetBIOS Names How to Install the WINS Service How to Configure Burst Handling

The Components of WINS WINS Server WINS Database WINS Client Subnet 1 Subnet 2 WINS Server WINS Database WINS Client WINS Proxy

What Is a NetBIOS Node Type? A NetBIOS node type is a method that a computer uses to resolve a NetBIOS name into an IP address Node type Description Registry value B-node Uses broadcasts for name registration and resolution 1 P-node Uses a NetBIOS name server such as WINS to resolve NetBIOS names 2 M-node Combines B-node and P-node, but functions as a B-node by default 4 H-node Combines P-node and B-node, but functions as a P-node by default 8

How a WINS Client Registers and Releases NetBIOS Names Name Registered Name Released WINS Client WINS Server WINS client sends request to register WINS server returns registration message with TTL value indicating when the registration expires if not renewed 1 WINS client sends request to release name WINS server sends a positive name lease response 2

How Burst Handling Works Burst handling is the response of a WINS server to a large number of WINS clients that are trying to simultaneously register their local names in WINS Request to register 1 Registered 2

How a WINS Server Resolves NetBIOS Names Subnet 2 Subnet 1 WINS Server A WINS Server B ClientA Up to 3 attempts 1 2 3 Client makes 3 attempts to contact WINS server, but does not receive a response 1 Client attempts to contact all WINS servers until contact is made 2 If name is resolved, IP address is returned to the client 3

How to Install the WINS Service Your instructor will demonstrate how to: Install the WINS service Check the status of the WINS service

How to Configure Burst Handling Your instructor will demonstrate how to configure burst handling

Practice: Installing and Configuring a WINS Server In this practice, you will install and configure a WINS server.

Lesson: Managing Records in WINS What Is a Client Record? What Is a Static Mapping? How to Add a Static Mapping Entry Methods for Filtering and Viewing Records in WINS How to Filter WINS Records

What Is a Client Record? The service that registered the entry, including the hexadecimal type identifier The registered NetBIOS name, which can be a unique name, or a group, internet group, or multihomed computer The IP address that corresponds to the registered name The WINS server from which the entry originates Displays “x” to indicate whether the entry is static and displays “null” or is blank if the entry is not static The state of the database entry, which can be active, released, or tombstoned A unique hexadecimal number that the WINS server assigns during name registration Shows when the entry will expire

What Is a Static Mapping? A static mapping is a manual entry in the WINS database that maps a NetBIOS name to an IP address Administrator enters computer name-to-IP address entry Non-WINS Clients WINS Database

How to Add a Static Mapping Entry Your instructor will demonstrate how to add a static mapping entry

Methods for Filtering and Viewing Records in WINS Search filter Description NetBIOS name and IP address Based on all or part of a NetBIOS name, an IP address, or a NetBIOS name and an IP address, including or excluding the subnet mask as a parameter Record owners Based on the name records of one or more name record owners Record types Based on one or more NetBIOS name suffix record types

How to Filter WINS Records Your instructor will demonstrate how to filter WINS records

Practice: Managing Records in the WINS Server In this practice, you will manage records in the WINS server

Lesson: Configuring WINS Replication How WINS Replication Works How Push Replication Works How Pull Replication Works What Is Push/Pull Replication? WINS Replication Partner Properties How to Configure WINS Replication How to Configure Replication Partners Properties  

How WINS Replication Works WINS replication is the process of copying updated WINS data from a WINS server to other WINS servers in a network to synchronize the data WINS Server A Subnet 2 Subnet 1 WINS Server B WINS Replication HostB HostA

How Push Replication Works A push partner notifies replication partners when the database reaches a set threshold of changes Push replication maintains a high level of synchronization/use with fast links Subnet 2 Subnet 1 WINS Server A WINS Server B Subnet 2 Subnet 1 WINS Server A WINS Server B Replicas sent 4 Replication request 3 Notification sent 2 50 changes occur in database 1 WINS Server A reaches set threshold of 50 changes in its database 1 WINS Server A notifies WINS Server B that threshold is reached 2 WINS Server B responds to WINS Server A with a replication request 3 WINS Server A sends replicas of its new database entries 4

How Pull Replication Works A pull partner requests replication based on a set time Pull replication limits frequency of replication traffic across slow links Subnet 2 Subnet 1 WINS Server A WINS Server B Requests changes every 8 hours 1 Replicas sent 2 Subnet 2 Subnet 1 WINS Server A WINS Server B WINS Server A requests database changes every 8 hours 1 WINS Server B sends replicas of its new database entries 2

What Is Push/Pull Replication? Push/pull replication effectively ensures that the databases on multiple WINS servers are nearly identical at any given time by: Notifying replication partners whenever the database reaches a set threshold of changes AND Requesting replication based on a set time

WINS Replication Partner Properties Property Description Enable automatic partner configuration As WINS servers are discovered joining the network, they are added as replication partners Enable persistent connections Increases the speed of replication so that a server can immediately send records to its partners Enable overwrite unique static mappings at this server (migrate on) If presented with both a static and dynamic-type entry for the same name, the static mapping is overwritten

How to Configure WINS Replication Your instructor will demonstrate how to: Configure WINS replication Modify a replication partner type Modify the Push Replication settings for replication partners Modify the Pull Replication settings for replication partners Replicate with all WINS partners Start push replication for a WINS replication partner Start pull replication for a WINS replication partner

How to Configure Replication Partners Properties Your instructor will demonstrate how to: Configure the Pull properties for the replication partner Configure the Push properties for the replication partner

Practice: Configuring WINS Replication In this practice, you will configure WINS replication

Lesson: Managing the WINS Database Why Back Up a WINS Database? How to Back Up and Restore a WINS Database What Are Simple Deletion and Tombstoned Deletion of Records? How to Delete a WINS Record What Are Dynamic and Offline Compacting? How to Compact a WINS Database How Scavenging Works How to Scavenge a WINS Database How a WINS Database Is Checked for Consistency How to Check for Consistency on a WINS Database Guidelines for Decommissioning a WINS Server How to Decommission a WINS Server

Why Back Up a WINS Database? To repair a corrupt WINS database, you can back up and then restore a WINS database To back up a WINS database : To restore a WINS database: Specify a backup directory Back up manually or configure automatic backups Manually delete and restore database files

How to Back Up and Restore a WINS Database Your instructor will demonstrate how to: Specify a back up directory for the WINS database Manually back up a WINS database Restore a WINS database from a recent backup

What Are Simple Deletion and Tombstoned Deletion of Records? To recover unused space that obsolete records occupy, you can update the WINS database by: Simple deletion. Records selected by using the WINS console are removed from the current local WINS server Tombstoned deletion. Records are marked for deletion, replicated to other WINS servers, and then removed during the next scavenging operation

How to Delete a WINS Record Your instructor will demonstrate how to delete a WINS record

What Are Dynamic and Offline Compacting? Compacting is the process of recovering unused space in a WINS database that is occupied by obsolete records Maintain WINS database integrity by using: Dynamic compacting. Automatically occurs while the database is in use Offline compacting. Administrator stops the WINS server and uses the jetpak command

How to Compact a WINS Database Your instructor will demonstrate how to compact a WINS database offline

4 6 7 3 5 1 2 How Scavenging Works Scavenging process: 7-days Jan 1 Jan 15 Jan 8 Scavenge No-Refresh Interval Refresh Time stamped Aging Scavenging process: Scavenging process: 4 6 7 3 5 1 2 The active names that the WINS server owns and for which the Renew Interval has expired are marked as released The scavenging timer starts when the server starts up and is equal to half the Renewal interval Released names that the WINS server owns and for which the Extinction interval has expired are marked for deletion Names marked for deletion for which the Extinction timeout has expired are deleted and removed from the database Active names that are replicated from other servers and for which the Verification interval has expired are revalidated Names marked for deletion that are replicated from other servers and for which the Extinction timeout has expired are deleted and removed from the database Names marked for deletion that are replicated from other servers are removed from the database

How to Scavenge the WINS Database Your instructor will demonstrate how to: Configure scavenging settings on the WINS database Scavenge the WINS database

How a WINS Database Is Checked for Consistency Checking WINS database consistency helps maintain database integrity among WINS servers in a large network WINS Server

How to Check for Consistency on a WINS Database Your instructor will demonstrate how to: Configure WINS database verification Verify database consistency Verify version ID consistency

Guidelines for Decommissioning a WINS Server Decommissioning an installed WINS server is the act of removing it from a network Guidelines for decommissioning a WINS server: If you reduce the number of WINS servers in your network, you can reconfigure WINS clients to point to other WINS servers in the network Reconfiguration is necessary only if clients are still using WINS If you eliminate WINS in your network, you can implement DNS as your primary naming service

How to Decommission a WINS Server Your instructor will demonstrate how to decommission a WINS server

Practice: Managing a WINS Database In this practice, you will manage a WINS database

Lab A: Resolving NetBIOS Names by Using Windows Internet Name Service (WINS) In this lab, you will identify and resolve common issues when resolving NetBIOS names by using WINS