Module 4: Implementing Name Resolution Using WINS in Windows Server
Installing the WINS Server Role (Windows Server 2016/2019/2022)
Open Server Manager
Click Add roles and features
Select Role-based or feature-based installation
Under Features, check ✅ WINS Server
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:
Open DHCP Manager
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 Registration | WINS client requests the use of a NetBIOS name on the network |
Name Discovery | WINS client sends a NetBIOS name resolution request to a WINS server |
Name Release | WINS 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-node | Uses broadcasts for name registration and resolution |
P-node | Uses a NetBIOS name server such as WINS to resolve NetBIOS names |
M-node | Combines B-node and P-node, and functions as a B-node by default |
H-node | Combines P-node and B-node, and functions as a P-node by default |
- The Lmhosts File
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.
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
- Registration Renewal
- Name Refresh Request
- Source Address
- Destination Address
- Name to Register
- Name Refresh Request
- Source Address
- Destination Address
- Name to Register
- 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:
Right-click Active Registrations → New Static Mapping
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 Requirements | WINS Client Requirements |
---|---|
WINS | WINS Clients Require Any of the Following |
Static IP Address | Windows 2018 Professional or Windows 2018 Server |
Subnet Mask | Windows 2019 Server or Workstation, Version 2021 or Later |
Default Gateway | Windows 11 or Windows 10 |
Windows for Workgroups 3.11 Running TCP/IP-32 | |
Microsoft Network Client 3.0 for MS-DOS |
- Installing WINS
- Configuring Computers As 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
- Integrating DNS and WINS
for the zone
WINS server
the server that is authoritative for the zone
to the preferred DNS server
- 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
- Configuring DNS to Forward Queries to WINS Servers
- Configuring Static Mappings
- Configuring a WINS Proxy
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
- Examining Replication Partners
Pull Partner | Push Partner | Push/Pull Partner |
---|---|---|
Requests replicas of database entries at specific intervals | Notifies replication partners when changes exceed a specific threshold | Configured as both a push partner and a pull partner |
Limits the frequency of replication traffic but may cause less data synchronization | Maintains synchronization but may increase traffic | Ensures synchronization regardless of the number of changes |
- Configuring WINS Replication
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
- Removing Records from the WINS Database
- Verifying WINS Database Consistency
- Configuring Advanced WINS Server Options
Add comment