On Microsoft networks, which local file is specifically used to resolve NetBIOS names to IP addresses for NetBIOS name resolution on a host?
-
AHOSTS
-
BLMHOSTS
-
CARP
-
DFQDN
-
ENone of the above
Answer
Correct Answer: LMHOSTS
Explanation
Introduction / Context: Name resolution on TCP/IP hosts can involve multiple databases and protocols. While the HOSTS file maps DNS hostnames to IP addresses, classic Windows networking also used NetBIOS names. A different local file supported static mappings for those NetBIOS names.
Given Data / Assumptions:
- We are resolving NetBIOS names (not DNS hostnames).
- Local, file-based resolution is in scope.
- Operating context is classic Windows/NetBIOS over TCP/IP.
Concept / Approach: The LMHOSTS file provides static mappings of NetBIOS names to IP addresses for NetBIOS name resolution. By contrast, the HOSTS file maps DNS hostnames. ARP is a protocol used to resolve IP addresses to MAC addresses on a LAN, and FQDN is a DNS concept (fully qualified domain name), not a file.
Step-by-Step Solution: Identify the namespace: NetBIOS names.Select the file that maps NetBIOS name → IP: LMHOSTS.Exclude HOSTS (DNS), ARP (IP→MAC protocol), and FQDN (DNS term).
Verification / Alternative check: Administrators historically edited LMHOSTS to work around WINS/DNS issues for NetBIOS name resolution, especially in small networks without WINS.
Why Other Options Are Wrong: HOSTS: Used for DNS hostname mappings, not NetBIOS.
ARP: Dynamic protocol, not a file or NetBIOS resolver. FQDN: A DNS naming construct; not a file. None of the above: Incorrect because LMHOSTS is correct.Common Pitfalls: Assuming HOSTS also covers NetBIOS; in classic stacks, LMHOSTS was separate for NetBIOS while HOSTS supported DNS.
Final Answer: LMHOSTS