background image
Name Resolution 273
NetBIOS over TCP/IP (NBT)
TCP/IP communication relies on IP address as endpoint identifiers. Microsoft Windows
communication relies on simple names as endpoint identifiers. TCP/IP workstations running
Microsoft Windows use NBT, and Microsoft and Cisco recommend NBT for medium and large
networks.
Name Resolution
In commands that require client and service access, Microsoft Windows uses NetBIOS names
to communicate. NetBIOS names are created when services are started, when clients log in to
the network, or when a NetBIOS application starts.
A client's or server's NetBIOS name is the computer name assigned during installation. This
name can be viewed in Network Neighborhood when resources are accessed.
Before two NetBIOS hosts can communicate, the name must be resolved to an IP address.
NetBIOS name resolution is the process of mapping a computer's name to an IP address.
Microsoft uses several methods of resolving NetBIOS names:
·
Broadcasts
·
LMHOSTS
·
WINS
·
DNS
Broadcasts
By sending broadcasts on a subnet, Windows clients cause a browser election. The computer
that is elected as browse master maintains a list of all the resources available. Because this
method does not scale well, it is not recommended.
LMHOSTS
The LMHOSTS file is used to resolve NetBIOS names and IP addresses of remote computers
outside the local subnet. The most common use of the LMHOSTS file is for locating remote
servers for file, print, and RFC services. All clients are configured with an LMHOSTS file,
which contains the name and IP address of their primary domain controller. Manual
configuration tasks create an administrative burden and make the LMHOSTS option
undesirable in medium to large networks.
87200333.book Page 273 Wednesday, August 22, 2001 2:37 PM