Windows NT 4.0 WINS Server Configuration Guide

Introduction

Windows Internet Name Service (WINS) provides NetBIOS name resolution for Windows networks. In NT 4.0 environments, WINS is critical for proper network functionality, especially in routed networks. This guide covers installation, configuration, and troubleshooting of WINS servers.

Understanding WINS

What is WINS?

WINS is Microsoft's implementation of a NetBIOS Name Server (NBNS): - Resolves NetBIOS names to IP addresses - Dynamic database of name registrations - Reduces broadcast traffic - Essential for browsing across subnets

NetBIOS Names

NetBIOS names characteristics: - Maximum 15 characters (16th reserved) - Case-insensitive - Different from DNS names - Required for NT 4.0 networking

When You Need WINS

WINS is required when: - Network spans multiple subnets - Using NT domains across routers - Need to reduce broadcast traffic - Supporting legacy applications - No Dynamic DNS available

Installing WINS Service

Prerequisites

• Windows NT Server 4.0
• Static IP address
• Administrative privileges
• Service Pack 3 or later recommended

Installation Steps

1. Add WINS Service Control Panel → Network → Services → Add Select "Windows Internet Name Service" Insert NT Server CD if prompted Click OK

2. Configure TCP/IP Network → Protocols → TCP/IP → Properties WINS Address tab: Primary WINS Server: [This server's IP]

3. Restart Server

4. Required for service activation
5. WINS database created automatically

Initial Configuration

1. Start WINS Manager Start → Programs → Administrative Tools → WINS Manager

2. Add Local Server Server → Add WINS Server Enter this server's IP address

WINS Database

Database Location

Default location:

%SystemRoot%\System32\WINS\
- wins.mdb (Main database)
- winstmp.mdb (Temporary file)
- J50.log, J50.chk (Transaction logs)

Record Types

Common NetBIOS suffixes: - <00> - Workstation service - <03> - Messenger service - <06> - RAS Server service - <1B> - Domain Master Browser - <1C> - Domain Controllers - <1D> - Master Browser - <1E> - Browser Elections - <20> - Server service

Database Maintenance

1. Backup Database WINS Manager → Mappings → Backup Database Specify backup path Enable automatic backup

2. Restore Database Stop WINS service Copy backup files to WINS directory Start WINS service

3. Compact Database net stop wins cd %SystemRoot%\System32\WINS jetpack wins.mdb tmp.mdb net start wins

WINS Client Configuration

Manual Configuration

1. Windows NT/2000/XP TCP/IP Properties → WINS Address Primary WINS Server: [IP Address] Secondary WINS Server: [IP Address] Enable NetBIOS over TCP/IP

2. Windows 95/98 TCP/IP Properties → WINS Configuration Enable WINS Resolution WINS Server: [IP Address]

DHCP Integration

Configure DHCP to provide WINS:

DHCP Manager → Scope → Options
044 WINS/NBNS Servers: [WINS IPs]
046 WINS/NBT Node Type: 0x8 (h-node)

Node Types

NetBIOS node types: - B-node (1): Broadcast only - P-node (2): WINS only - M-node (4): Broadcast, then WINS - H-node (8): WINS, then broadcast (recommended)

WINS Replication

Planning Replication

Consider these factors: - Network topology - WAN link speeds - Number of clients - Change frequency - Convergence requirements

Configuring Push/Pull Partners

1. Add Replication Partner WINS Manager → Server → Replication Partners Add → Enter partner IP address

2. Configure Push Partner Push Partner Properties: Update Count: 20 (changes before push)

3. Configure Pull Partner Pull Partner Properties: Start Time: 02:00 (off-peak) Replication Interval: 1800 (30 minutes)

Replication Topologies

Hub and Spoke

    WINS-Central
    /    |    \
WINS-1  WINS-2  WINS-3

Best for: Star network topology

Ring Configuration

WINS-1 ← → WINS-2
  ↑           ↓
WINS-4 ← → WINS-3

Best for: Fault tolerance

Mesh Configuration

WINS-1 ← → WINS-2
  ↕     X     ↕
WINS-3 ← → WINS-4

Best for: Maximum redundancy

Advanced Configuration

WINS Registry Settings

Key location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Parameters

Important values:

RefreshInterval: 345600 (4 days)
TombstoneInterval: 345600 (4 days)
TombstoneTimeout: 518400 (6 days)
VerifyInterval: 1728000 (20 days)
WinsThreadPriority: Normal

Static Mappings

For non-WINS clients:

1. Add Static Mapping WINS Manager → Mappings → Static Mappings Add Mappings: Name: SERVER1 Type: Unique IP Address: 192.168.1.10

2. Mapping Types

3. Unique: Single IP address
4. Group: NetBIOS group (broadcast)
5. Domain Name: Domain controllers
6. Internet Group: Multiple IPs
7. Multihomed: Multiple NICs

Import LMHOSTS

Import static mappings from LMHOSTS:

WINS Manager → Mappings → Import LMHOSTS
Select file (usually C:\WINNT\System32\Drivers\Etc\LMHOSTS)

Monitoring WINS

WINS Statistics

View in WINS Manager:

Server → Detailed Information

Statistics include:
- Total Queries Received
- Successful Queries
- Failed Queries
- Total Releases
- Registration Requests

Performance Monitor Counters

Add these counters:

WINS Server object:
- Queries/sec
- Releases/sec
- Registrations/sec
- Failed Queries/sec
- Failed Releases/sec
- Group Registrations/sec

Event Log Monitoring

Check for these events: - WINS service start/stop - Database corruption - Replication failures - Version ID problems

Troubleshooting WINS

Common Problems

Clients Cannot Resolve Names

1. Verify WINS Configuration ipconfig /all Check WINS servers listed

2. Test WINS Resolution nbtstat -R (purge cache) nbtstat -a computername

3. Check WINS Database WINS Manager → Mappings → Show Database Search for the name

Duplicate Name Errors

1. Find Conflicts Event Log shows duplicate name WINS Manager → show owner

2. Resolution

3. Delete static mapping
4. Force refresh on client
5. Check for multiple WINS servers

Database Corruption

Signs of corruption: - Service won't start - Frequent crashes - Missing registrations

Recovery steps: 1. Stop WINS service 2. Rename corrupted database 3. Restore from backup 4. Or start fresh (clients re-register)

NBTSTAT Utility

Useful commands:

nbtstat -n    Show local NetBIOS names
nbtstat -c    Display cache
nbtstat -R    Purge and reload
nbtstat -a    Query by name
nbtstat -A    Query by IP
nbtstat -s    Show sessions
nbtstat -r    Registration statistics

WINS Debug Logging

Enable detailed logging:

WINS Manager → Server → Configuration
[X] Log Detailed Events

Check log file:

%SystemRoot%\System32\WINS\JET.LOG

Best Practices

Design Guidelines

1. WINS Server Placement
2. One WINS server per 10,000 clients
3. Place near largest client populations
4. Provide secondary WINS servers

5. Consider WAN link utilization

6. High Availability

7. Configure all clients with primary and secondary
8. Implement replication between servers
9. Stagger replication schedules

10. Monitor database size

11. Performance Optimization

12. Regular database maintenance
13. Adequate hardware resources
14. Monitor replication traffic
15. Optimize registry settings

Security Considerations

1. Restrict WINS Access
2. Use IPSec if available
3. Limit who can administer

4. Monitor for rogue registrations

5. Backup Security

6. Protect backup files
7. Test restore procedures
8. Document configurations

Maintenance Schedule

Daily

• Check Event Logs
• Monitor service status
• Verify replication

Weekly

• Review statistics
• Check database size
• Analyze failed queries

Monthly

• Compact database
• Verify all partnerships
• Update documentation

Quarterly

• Test failover procedures
• Review capacity
• Plan for growth

Migration and Coexistence

DNS Integration

For future migration: 1. Enable DNS on network 2. Use WINS for NetBIOS 3. DNS for hostname resolution 4. Plan WINS retirement

WINS Proxy

For non-WINS subnets: 1. Enable on one client per subnet 2. Registry setting: EnableProxy = 1 (REG_DWORD) 3. Forwards broadcasts to WINS

Sample Configurations

Small Network (Single Site)

One WINS Server:
- All clients point to single WINS
- No replication needed
- Simple backup strategy

Medium Network (Multiple Sites)

Hub Site: Primary and Secondary WINS
Remote Sites: Local WINS servers
Replication: Hub and spoke model
Schedule: Every 30 minutes

Large Enterprise

Regional WINS Servers: 2 per region
Replication: Mesh between regions
Push Partners: Update count 20
Pull Partners: 15-minute intervals

Command Line Management

WINSCL.EXE Commands

REM Show statistics
winscl.exe stats

REM Initiate replication
winscl.exe push [partner IP]
winscl.exe pull [partner IP]

REM Backup database
winscl.exe backup [path]

REM Compact database
net stop wins
jetpack %SystemRoot%\System32\WINS\wins.mdb temp.mdb
net start wins

Conclusion

WINS is essential for Windows NT 4.0 networks spanning multiple subnets. Proper configuration ensures reliable name resolution, efficient browsing, and smooth domain operations. Regular maintenance and monitoring prevent issues and ensure optimal performance. While WINS is legacy technology, understanding its operation remains important for supporting NT 4.0 environments.