You are an ethical hacker tasked with conducting an enumeration of a company's network. Given a Windows system with NetBIOS enabled, port 139 open, and file and printer sharing active, you are about…

Question

Options

• AUse nbtstat -c to get the contents of the NetBIOS name cache
• Buse nbtstat -a followed by the IPv6 address of the target machine
• CUtilize Nmap Scripting Engine (NSE) for NetBIOS enumeration
• DSwitch to an enumeration tool that supports IPv6

• A
  7% (2)
• B
  14% (4)
• C
  4% (1)
• D
  75% (21)

Explanation

Explanation

Switching to an IPv6-compatible enumeration tool is necessary because nbtstat is designed exclusively for IPv4 networks and cannot resolve or communicate with IPv6 addresses, making it functionally useless in this scenario. Option A is incorrect because nbtstat -c only displays the local NetBIOS name cache and doesn't actively enumerate a remote target at all. Option B is incorrect because nbtstat -a accepts a hostname or IPv4 address as its argument - it does not support IPv6 address syntax, so the command would simply fail. Option C, while Nmap NSE is a powerful tool, is not the most direct next step compared to selecting a purpose-built IPv6-compatible enumeration tool, and the question emphasizes addressing the IPv6 compatibility gap as the primary obstacle.

Memory Tip: Think of it this way - "Old tools, old rules." nbtstat was built in the IPv4 era and never got an IPv6 upgrade. Whenever you see IPv6 + NetBIOS enumeration, your first thought should be: "nbtstat won't work here - I need a modern, IPv6-aware tool." The protocol mismatch is always the blocker.

No community discussion yet for this question.