Which command is commonly used to troubleshoot NetBIOS name resolution problems on Windows?

Which command is commonly used to troubleshoot NetBIOS name resolution problems on Windows?

• A. nbtstat -a <IP address>
• B. nslookup
• C. ipconfig /all
• D. nbtstat

Answer: (B)

NetBIOS name resolution problems are diagnosed using NetBIOS-specific tooling rather than DNS tools. The typical command to troubleshoot NetBIOS name resolution is nbtstat, because it lets you view the NetBIOS name table and cache, see which names are registered on the local machine, and query a remote host’s NetBIOS name table by IP or name. This helps verify whether NetBIOS names are being resolved correctly and whether there are conflicts or registration issues. nslookup, by contrast, queries DNS servers for DNS records and does not expose NetBIOS name tables or NetBIOS/WINS-related problems, so it isn’t the right tool for NetBIOS name resolution troubleshooting. When using nbtstat, you can inspect local names (nbtstat -n), query a remote host’s NetBIOS name table by IP (nbtstat -A <IP>), or by name (nbtstat -a <name>), and refresh caches as needed (nbtstat -R, nbstat -RR). Also check that NetBIOS over TCP/IP is enabled (via ipconfig /all) and that any WINS or broadcast paths are functioning.

NetBIOS name resolution problems are diagnosed using NetBIOS-specific tooling rather than DNS tools. The typical command to troubleshoot NetBIOS name resolution is nbtstat, because it lets you view the NetBIOS name table and cache, see which names are registered on the local machine, and query a remote host’s NetBIOS name table by IP or name. This helps verify whether NetBIOS names are being resolved correctly and whether there are conflicts or registration issues.

nslookup, by contrast, queries DNS servers for DNS records and does not expose NetBIOS name tables or NetBIOS/WINS-related problems, so it isn’t the right tool for NetBIOS name resolution troubleshooting. When using nbtstat, you can inspect local names (nbtstat -n), query a remote host’s NetBIOS name table by IP (nbtstat -A ), or by name (nbtstat -a ), and refresh caches as needed (nbtstat -R, nbstat -RR). Also check that NetBIOS over TCP/IP is enabled (via ipconfig /all) and that any WINS or broadcast paths are functioning.