Title: Windows Internet Name Service
1Chapter 5
- Windows Internet Name Service
2Learning Objectives
- Provide an overview of NETBIOS naming and NetBIOS
name resolution - Describe the features of the Windows Internet
Name Service (WINS) - Explain in detail the new features in the Windows
2000 implementation of WINS - Install WINS
continued
3Learning Objectives
- Configure replication between WINS servers
- Configure a client to use WINS
- Manage, monitor, and troubleshoot WINS
4NetBIOS Naming
- NetBIOS
- Session-level API developed to provide high-level
applications with easy access to lower-level
networking protocols - Uses a flat namespace
- Names can only be used once per machine on a
network - NetBIOS scope can overcome this limitation
- NetBT
- NetBIOS using TCP/IP as its lower-level
networking protocol stack - Common abbreviation for NetBIOS over TCP/IP
5Unique and GroupNetBIOS Names
- Unique NetBIOS names
- 16 bytes long
- Identify both the computer name and certain
services running on a computer - Example win2kdc01
- Group NetBIOS names
- Identify multiple computers
- Example Domain controllers in a domain
6Common Unique andGroup NetBIOS Name Types
7NetBIOS Naming
- Issue the nbtstat n command after the command
prompt to view a list of all the services and
their corresponding NetBIOS names
8NetBIOS Name Resolution
9How Node Types Determine Name Resolution Methods
10NetBIOS Name Resolution
- Easiest way to set the node type for a client is
to assign it as a DHCP scope option - Set the 044 option to the IP addresses of WINS
servers you want clients to use - Set the 046 or node type to 0x8, the value for
h-node
11NetBIOS Name Resolution
- Use h-node on your network to ensure that clients
first attempt to use directed communi-cation with
the WINS server and only use broadcast as a
secondary methods for name resolution
12NetBIOS Name Resolution
- By default, all Windows 2000 clients are
configured to use the Lmhosts file if it is
present and no other NetBIOS name resolution
method can provide resolution
13NetBIOS Name Resolution
14Lmhosts Extensions
15Lmhosts Files
- Main drawback administrative overhead
associated with maintaining Lmhosts files - As static databases, they require changes
whenever new computers are added to the network
or when IP addresses change - To meet the need for a better method of
alleviating some of this administration,
Microsoft created the Windows Internet Name
Service
16Windows Internet Name Service
- Allows clients to register their NetBIOS name to
IP address mappings in a dynamic database hosted
on a WINS server - Provides a dynamic method to register NetBIOS
names to IP addresses - Allows clients to use directed communica-tions to
a WINS server instead of broadcasts
17Tasks a Client Can Access WINS Servers to Perform
- NetBIOS name registration
- NetBIOS name renewal
- NetBIOS name release
- NetBIOS name query
18NetBIOS Name Registration
- Sent by WINS clients to WINS servers to ask for
registration of a particular NetBIOS name with an
IP address
19NetBIOS Name Renewal
- Sent by WINS clients to request that the WINS
server extend the NetBIOS name to IP address
mapping - Normally occurs halfway through the TTL
20NetBIOS Name Release
- Sent by WINS clients to direct the WINS server to
terminate the dynamic mapping of a NetBIOS name
to an IP address
21NetBIOS Name Query
- Used by WINS clients to query WINS servers for
information about a particular NetBIOS name - Used to find NetBIOS name to IP address mappings
22Name Query Response
- Response sent from a WINS server to the WINS
client, either informing the client of the
NetBIOS name to IP address resolution or of
failure to achieve a resolution
23Name Query and Name Query Response
24WINS in Windows 2000
- Most new features are attempts to make management
and use of the WINS server easier - Other features decrease the time used for WINS
replication (process of replicating WINS
databases between multiple WINS servers) - Major new features
- Automatic Replication Partners
- Persistent connections
- Manual tombstoning
25Automatic Replication Partners
26Installing WINS
- Pre-installation requirements
- Configure server with a static IP address, subnet
mask, and default gateway - Configure WINS settings in the Internet Protocol
Properties (TCP/IP) to point to servers own IP
address - Determine how many WINS servers the network needs
- Two minimum one as primary and another as
backup - Primary and back-up servers should be able to
support a network of 10,000 clients
27Installing WINS
- Open the Network and Dial-up Connections dialog
box
28Installing WINS
29Installing WINS
- Open the Windows Optional Networking Components
Wizard and Networking Services dialog boxes
30Installing WINS
31Installing WINS
- Click WINS and click OK to install the WINS
server and make it available under Administrative
Tools
32Installing WINS
33Installing WINSActive Registrations
34Installing WINSActive Registrations
35Configuring WINS Server
- Use default configuration clients automatically
register NetBIOS names and IP addresses with the
WINS server - To provide a WINS entry for a non-WINS client
such as a UNIX box, add a static entry to the
WINS database
36Configuring WINS Replication
- Required in a network with more than one WINS
server, otherwise clients on the network may not
be able to resolve certain NetBIOS names - All WINS servers should be configured to perform
replication with one another
37WINS Replication
38Configuring WINS Replication
- Replication partners can be set up automatically
via multicast - In most cases, you need to configure replication
manually to ensure that it meets the needs of the
network - Types of WINS replication
- Pull
- Push
39Pull and Push Replication
- Pull replication
- Occurs at a preset time interval
- Used with slow WAN links
- Push replication
- Occurs after a predetermined number of changes to
the database occur - Used with fast connections between replication
partners - Most WINS servers are configured as both push and
pull replication partners to ensure that the
databases for each server remain constant
40Configuring WINS Replication
- Open the WINS console and right-click the
Replication Partners folder
41Configuring WINS Replication
- Type the IP address of the WINS server that you
wish to configure as a replication partner and
click OK to continue - Repeat on both servers that you wish to set up as
replication partners
42Configuring WINS Replication
43Configuring Advanced Properties for WINS
Replication
- Set replication parameters
- Interval for pull replication
- Number of updates before push replication is
triggered - Set persistent connection settings
44Configuring Clients for WINS
- Easiest way
- Set the DHCP 044 and 046 scope options mentioned
earlier in NetBIOS Name Resolution - Guarantees that all DHCP-enabled clients receive
the IP address of WINS servers on your network
and the correct node type for NetBIOS name
resolution
45Configuring Clients for WINS
- On clients with static IP addresses, configure
WINS setting in the Advanced properties, WINS tab
of the Advanced (TCP/IP) settings dialog box - Configure primary and secondary WINS server
- Enable/disable use of Lmhosts file
- Enable/disable NetBIOS over TCP/IP
46Configuring Clients for WINS
- For all static clients, you must access the WINS
tab and manually type WINS server information
47Managing, Monitoring, and Troubleshooting WINS
- Most troubleshooting stems from incorrectly set
WINS entries on the client or incorrect DHCP
scope options on the DHCP servers - Use Event Viewer to discover WINS errors
- Use WINS console most important WINS
management, configuration, and troubleshooting
tool for further information about WINS server
service (eg, Back Up Database) - May need to compact the WINS database
48WINS Server Statistics Window
49Server Properties Dialog Box
50Chapter Summary
- NetBIOS naming
- Windows Internet name service
- WINS in Windows 2000
- Installing WINS
- Configuring WINS replication
- Configuring clients for WINS
- Managing, monitoring, and troubleshooting WINS