In Microsoft networking, which configuration file is specifically used for NetBIOS name resolution on TCP/IP networks?

Introduction / Context:
NetBIOS name resolution predates widespread DNS use in Windows environments and is still relevant in legacy or isolated networks. Two similar-sounding files can cause confusion: HOSTS and LMHOSTS. This item distinguishes their roles.

Given Data / Assumptions:

• Environment uses NetBIOS names over TCP/IP.
• Goal is static name-to-address mapping for NetBIOS.
• We compare common files/utilities.

Concept / Approach:
LMHOSTS provides static mappings of NetBIOS names to IP addresses. HOSTS maps DNS hostnames to IP addresses. ARP is a runtime cache/protocol, not a config file. FQDN is a naming format, not a file.

Step-by-Step Solution:
Identify that the naming system is NetBIOS, not DNS.Recall the specific static mapping file: LMHOSTS.Confirm other options do not satisfy NetBIOS static mapping.

Verification / Alternative check:
Windows documentation shows lmhosts.sam as the sample, with entries like “IPaddr NETBIOSNAME”. HOSTS is used for DNS queries only.

Why Other Options Are Wrong:
HOSTS: For DNS hostnames, not NetBIOS.

ARP: Protocol/table for IP-to-MAC, not a name file.

FQDN: A fully qualified domain name, not a file.

None of the above: Incorrect because LMHOSTS exists for this purpose.

Common Pitfalls:
Assuming HOSTS also covers NetBIOS; it does not. NetBIOS name resolution uses LMHOSTS, WINS, or broadcast.

Final Answer:
LMHOSTS