Difficulty: Easy
Correct Answer: NBTSTAT
Explanation:
Introduction / Context: NetBIOS name resolution (for legacy Windows networking) differs from DNS. When browsing or connecting to shares fails due to name issues, a tool that exposes the NetBIOS name cache, remote name tables, and sessions is needed to diagnose the problem accurately.
Given Data / Assumptions:
Concept / Approach: NBTSTAT is the dedicated utility for NetBIOS over TCP/IP. It can display local and remote NetBIOS name tables, purge and reload the cache, and show NetBIOS sessions. In contrast, Netstat shows active sockets and routing; Ping tests IP reachability; Hostname prints the local machine’s name only and does not troubleshoot NetBIOS names.
Step-by-Step Solution:
Identify the troubleshooting scope: NetBIOS names, not generic TCP/UDP ports.Map each tool to its function and eliminate those unrelated to NetBIOS names.Select NBTSTAT as the correct utility.Verification / Alternative check: Commands like “nbtstat -n”, “nbtstat -c”, and “nbtstat -A
Why Other Options Are Wrong:
Netstat: lists connections and listening ports; not NetBIOS name tables.PING: tests ICMP reachability; does not diagnose NetBIOS naming.Hostname: shows local name only; no remote or cache insight.None of the above: incorrect because NBTSTAT is correct.Common Pitfalls: Assuming DNS and NetBIOS use the same tools; they have different caches and diagnostics.
Final Answer: NBTSTAT.
Discussion & Comments