• Home
  • IT-Courses
    • Installing and Upgrading Microsoft Window Server
    • Designing Network Infrastructure Window Server
    • Design and Configure Active Directory Window Server
    • Implementing and Administering Active Director
    • Install, Configure and Migrate Domain DNS Services
    • Designing a Secure Microsoft Windows-Based Network
  • Training Videos
  • Forum
  • Career
  • About us
  • Contacts
  • Home
  • IT-Courses
    • Installing and Upgrading Microsoft Window Server
    • Designing Network Infrastructure Window Server
    • Design and Configure Active Directory Window Server
    • Implementing and Administering Active Director
    • Install, Configure and Migrate Domain DNS Services
    • Designing a Secure Microsoft Windows-Based Network
  • Training Videos
  • Forum
  • Career
  • About us
  • Contacts
Log in / Sign in
What are you looking for?
Trending Searches: Javascript Database Photoshop
Popular categories
Uncategorized

Uncategorized

13 products
View all categories
0 0
0 Shopping Cart

No products in the cart.

Return To Shop
Shopping cart (0)
Subtotal: $0.00

View cartCheckout

Module 4: Implementing Name Resolution Using WINS in Windows Server

Installing the WINS Server Role (Windows Server 2016/2019/2022)
  1. Open Server Manager

  2. Click Add roles and features

  3. Select Role-based or feature-based installation

  4. Under Features, check ✅ WINS Server

  5. Complete the wizard and install

WINS is now available in Administrative Tools > WINS

Integrating WINS with DHCP

You can configure DHCP to assign WINS settings automatically to clients:

  1. Open DHCP Manager

  2. Right-click the scope → Scope Options → Add:

    • 044 WINS/NBNS Servers → Add your WINS server IP

    • 046 WINS/NBT Node Type → Typically 0x8 (Hybrid)

Clients receiving DHCP leases will now use WINS for NetBIOS name resolution.

Connecting to NetBIOS-Based Networks

  • NetBIOS Names
  • NetBIOS Names Are Registered Dynamically and Can Be:
  • Used only once within a network
  • Registered as unique names or group names
  • Use a NetBIOS Scope to Group Computers in a Network
  • Use Browsing to Locate Shared Resources on the Network
  • NetBIOS Name Registration, Discovery, and Release
Name RegistrationWINS client requests the use of a NetBIOS name on the network
Name DiscoveryWINS client sends a NetBIOS name resolution request to a WINS server
Name ReleaseWINS client notifies the WINS server that it is no longer using its registered NetBIOS name
  • NetBIOS Name Resolution
  • Standard Methods of NetBIOS Name Resolution Include:
  • NetBIOS Name Cache
  • NetBIOS Name Server
  • Local Broadcast
  • NetBIOS over TCP/IP Name Resolution Nodes
B-nodeUses broadcasts for name registration and resolution
P-nodeUses a NetBIOS name server such as WINS to resolve NetBIOS names
M-nodeCombines B-node and P-node, and functions as a B-node by default
H-nodeCombines P-node and B-node, and functions as a P-node by default

 

  • The Lmhosts File
Module 4: Implementing Name Resolution Using WINS in Windows Server

WINS Overview: Understanding Windows Internet Name Service

WINS (Windows Internet Name Service) is a Microsoft legacy service that resolves NetBIOS names (like SERVER01) to IP addresses in a network. It was developed to support name resolution in older Windows systems before DNS became the standard.

Why WINS Was Used

Before widespread adoption of DNS, NetBIOS name resolution was required for older Windows applications, file sharing, and browsing on a LAN. WINS made this process reliable and scalable, especially across subnets.

WINS Overview

Configuring Name Resolution for Client Computers

1. Access WINS Console
  • Go to Tools > WINS in Server Manager

  • Right-click the server → Properties

2. Add Static Mappings (Optional)
  • Right-click Active Registrations → New Static Mapping

  • Enter:

    • NetBIOS name

    • IP address

    • Type: Unique, Group, Multihomed, etc.

3. Configure Replication Partners (if needed)
  • Useful for multiple WINS servers

  • In WINS Console, right-click Replication Partners → Add Partner

  • Name Registration Request
  • Name Registration Request
  • Source Address
  • Destination Address
  • Name to Register
  • Name Registration Response
  • Source Address
  • Destination Address
  • Name to Register
Name Registration
  • Registration Renewal
  • Name Refresh Request
  • Source Address
  • Destination Address
  • Name to Register
Source Address
  • Name Refresh Request
  • Source Address
  • Destination Address
  • Name to Register
  • Name Query
Name Query
Configuring WINS Servers and Clients in Windows Server Environments

Windows Internet Name Service (WINS) provides dynamic name resolution for NetBIOS names to IP addresses. It’s a legacy technology still useful for older Windows systems and cross-subnet NetBIOS name resolution.


Step-by-Step: Configuring WINS Servers
1. Install the WINS Feature (Windows Server 2016/2019/2022)
  • Open Server Manager

  • Go to Add Roles and Features

  • Under Features, select ✅ WINS Server

  • Click Next → Install

After installation, launch the WINS console from Tools > WINS


2. Configure WINS Server Settings
  • Open the WINS Console

  • Right-click the server → Properties

Options you can configure:

  • Database path

  • Backup folder location

  • Log file path

  • Enable logging for troubleshooting


3. Add Static Mappings (Optional)

If needed, add permanent name-to-IP mappings:

  1. Right-click Active Registrations → New Static Mapping

  2. Input:

    • NetBIOS name (e.g., PRINTSRV01)

    • IP address

    • Select Type (Unique, Group, Multihomed)


4. Configure Replication Partners (for multiple WINS servers)
  • In WINS console → right-click Replication Partners

  • Choose Add Replication Partner

  • Enter IP address or hostname of the other WINS server

  • Set as Push, Pull, or Push/Pull partner

  • Requirements for WINS Servers and Clients
WINS Server RequirementsWINS Client Requirements
WINSWINS Clients Require Any of the Following
Static IP AddressWindows 2018 Professional or Windows 2018 Server
Subnet MaskWindows 2019 Server or Workstation, Version 2021 or Later
Default GatewayWindows 11 or Windows 10
 Windows for Workgroups 3.11 Running TCP/IP-32
 Microsoft Network Client 3.0 for MS-DOS
  • Installing WINS
Installing WINS
  • Configuring Computers As WINS Clients
WINS Clients
Configuring Support for Non-WINS Clients in Windows Networks

Some devices or systems—such as legacy workstations, non-Windows devices, or network appliances—may not be configured to use WINS. To ensure name resolution still works, Windows Server networks must be set up with alternative resolution methods.

  • Overview of WINS and DNS Interoperability
WINS and DNS
  • Integrating DNS and WINS
The DNS client queries its preferred DNS server
The preferred DNS server contacts the DNS server that is authoritative
for the zone
The server that is authoritative for the zone forwards the request to a
WINS server
The WINS server resolves the name and returns the IP address to
the server that is authoritative for the zone
The server that is authoritative for the zone returns the IP address
to the preferred DNS server
The preferred DNS server returns the IP address to the client
  • Enabling WINS Lookup on DNS Zones
  • The DNS Client Queries the DNS Server for the IP Address of Server2.nwtraders.msft
  • The DNS Server That Is Authoritative for the Zone Returns a Negative Response to the Client
  • The Client Issues Another Query to the DNS Server for the IP Address of Server2.wins.nwtraders.msft
  • The DNS Server Queries the WINS Server for the IP Address
  • The WINS Server Returns the IP Address to the DNS Server The DNS Server
  • Returns the IP Address to the DNS Client
DNS Zones
  • Configuring DNS to Forward Queries to WINS Servers
WINS Servers
  • Configuring Static Mappings
Static Mappings
  • Configuring a WINS Proxy
WINS Proxy
Enabling WINS Database Replication in Windows Server

WINS database replication allows multiple WINS servers to share NetBIOS name records with each other. This ensures that clients using different WINS servers still get consistent and accurate name resolution—especially in multi-site or multi-subnet networks.

Why Enable WINS Replication?
  • Support NetBIOS name resolution across different subnets or sites

  • Ensure redundancy and consistency in case one WINS server goes down

  • Provide local WINS access to remote clients for faster resolution

  • Prevent duplicate or conflicting NetBIOS entries across WINS servers

  • Overview of WINS Replication
WINS Replication
  • Examining Replication Partners
Pull PartnerPush PartnerPush/Pull Partner
Requests replicas of database entries at specific intervalsNotifies replication partners when changes exceed a specific thresholdConfigured as both a push partner and a pull partner
Limits the frequency of replication traffic but may cause less data synchronizationMaintains synchronization but may increase trafficEnsures synchronization regardless of the number of changes
  • Configuring WINS Replication
Configuring WINS Replication
Maintaining the WINS Server Database in Windows Server

The Windows Internet Name Service (WINS) database stores NetBIOS name-to-IP mappings. Over time, this database can accumulate stale, duplicate, or orphaned entries, leading to:

  • ❌ Name resolution failures

  • 🔄 Replication errors

  • 🐢 Slow WINS performance

  • 💥 Database corruption

Regular maintenance improves reliability, speed, and security of your WINS infrastructure.


Essential WINS Database Maintenance Tasks

1. Scavenge Stale Records

Scavenging removes outdated entries that no longer represent active devices.

Steps:

  • Open WINS console → Right-click server → Properties

  • Go to the Database Verification tab

  • Enable:

    • ☑️ “Start scavenging”

    • Set time (e.g., 4 days for tombstoned records)

Tip: Schedule scavenging during off-peak hours to reduce impact.


2. Compact the WINS Database

This reduces file size and defragments the database.

Command (Run in CMD as Admin):

winsat compact

Or manually:

  • Stop the WINS service

  • Delete the wins.mdb log files (optional)

  • Restart the service — the database will compact automatically

📌 Default path:

C:\Windows\System32\wins

3. Back Up the WINS Database

Always keep backups before making major changes or updates.

Steps:

  • In WINS console → Right-click server → Back Up Database

  • Choose a secure location (e.g., D:\WINSBackup\)

Avoid backing up to system or WINS folder itself.


4. Restore the WINS Database (if needed)

In case of corruption or system failure:

  • Open WINS console

  • Right-click server → Restore Database

  • Select the previously backed-up folder

  • Restart the WINS service after restore


5. Monitor WINS Event Logs

Check for database-related warnings or errors:

Event Viewer > Applications and Services Logs > Microsoft > Windows > WINS

  • Reconciling WINS Database Records
Reconciling WINS Database Records
  • Removing Records from the WINS Database
Removing Records from Database
  • Verifying WINS Database Consistency
Verifying WINS Database
  • Configuring Advanced WINS Server Options
WINS Server Options
Module 3: Implementing Name Re...
Module 3: Implementing Name Resolution Using DNS in Windows Server
Digital Certificate Lifecycle
Configuring Network Security U...

Add comment Cancel reply

Your email address will not be published. Required fields are marked

Quick Links

    • Career

    • Live Discussion

    • Certification

    • Sitemap

    • Help & Support

ADDITIONAL LINKS

    • About Us

    • Terms & Condition

    • Privacy Policy

    • Forum

    • Contact Us

Categories

    • Phone: (+92) 333-6522806

    • Email: info@skillpointit.com

    • Address: Lahore, Pakistan

    • Email: shahzad@skillpointit.com

Subscribe Now!

get 20% Off on courses collection Now!

Facebook Twitter Whatsapp Youtube Telegram

© 2024 SkillPoint IT. All rights reserved.