In Microsoft-centric networks, which service dynamically resolves NetBIOS names to IP addresses (as opposed to static files or DNS hostnames)?

Introduction / Context:
Legacy Windows networking used NetBIOS names for discovery and access. Mapping those names to IP addresses could be done dynamically or statically. Knowing which mechanism provides dynamic NetBIOS-to-IP resolution is important for troubleshooting name conflicts, browsing issues, and legacy application connectivity in mixed environments.

Given Data / Assumptions:

• The focus is NetBIOS name resolution, not general DNS hostname resolution.
• Dynamic rather than static mapping is required.
• Windows environments include several related services and files.

Concept / Approach:
Windows Internet Name Service (WINS) is the dynamic NetBIOS name server. Clients register their NetBIOS names and IP addresses with WINS and query it to resolve others. This differs from DNS (resolves hostnames, not NetBIOS names) and from LMHOSTS (a static text file that maps NetBIOS names to IP addresses). DHCP assigns IP configuration but does not resolve NetBIOS names.

Step-by-Step Solution:

Verification / Alternative check:
Administrative consoles show WINS databases with registered names and lifetimes; network traces capture NetBIOS Name Service queries to WINS servers, validating that WINS performs dynamic resolution in this context.

Why Other Options Are Wrong:

• DNS: primarily resolves DNS hostnames (FQDNs) via UDP/TCP 53; not specifically NetBIOS names.
• DHCP: provides IP configuration (address, mask, gateway, DNS/WINS options) but not name resolution.
• LMHOSTS: static file on clients; no dynamic registration.
• None: incorrect because WINS exists precisely for this task.

Common Pitfalls:
Assuming DNS entirely replaces NetBIOS resolution in all legacy scenarios; forgetting that LMHOSTS entries are static and must be manually maintained.

Final Answer:
WINS