Which command line utility is used to diagnose NetBIOS name resolution issues?

• A. Nbtstat
• B. Nslookup
• C. Ipconfig
• D. Ping

Answer: (A)

NetBIOS name resolution issues are diagnosed by inspecting NetBIOS names, their cache, and active sessions on a Windows machine. The tool that exposes all of this is used specifically to troubleshoot NetBIOS over TCP/IP, showing what names are registered locally, what names have been cached, and how the system is resolving remote NetBIOS names. You can view the local registrations with a command that lists the names the machine has registered and whether they’re unique or group names. You can look at the NetBIOS name cache to see what resolutions have recently occurred, and you can inspect or verify the remote machine’s NetBIOS name table to confirm the remote name is being advertised correctly. You can also flush and reload the cache to force fresh resolution attempts, which helps determine if stale cache entries are causing the problem. This focus on NetBIOS name tables, cache contents, and sessions makes it the right choice for NetBIOS-specific name resolution problems.

By contrast, nslookup targets DNS name resolution, ipconfig shows network configuration and NetBIOS over TCP/IP settings but not the resolution process itself, and ping tests reachability using whatever name resolution policy is in place without diagnosing NetBIOS name issues.