On Windows NT and related Windows clients, which command-line utility should you use to view whether IP configuration (address, mask, gateway, DNS) has been assigned to the system?

Introduction / Context:
Verifying a machine's IP address, subnet mask, default gateway, and DNS servers is a common troubleshooting step. Windows platforms provide several network utilities, but only a few display full IP configuration in a concise, reliable way from the command line. This question tests which tool is appropriate on Windows NT and later Windows systems.

Given Data / Assumptions:

• Platform: Windows NT class systems.
• Need: display assigned IP configuration.
• Prefer a command-line utility for scripting and remote use.

Concept / Approach:
IPCONFIG outputs the current TCP/IP configuration, including DHCP details and DNS suffixes. Adding the /all switch provides complete information, including MAC addresses and lease data. NETSTAT lists active connections, ports, and routing tables; NBTSTAT shows NetBIOS over TCP/IP name tables; WINIPCFG existed on Windows 9x (GUI), not on NT-class systems; PING tests reachability but does not show local configuration.

Step-by-Step Solution:

Verification / Alternative check:
Windows documentation and help text (ipconfig /?) confirm this usage. Modern equivalents persist across Windows versions, making IPCONFIG the canonical choice.

Why Other Options Are Wrong:

• NBTSTAT: NetBIOS name tables, not IP config.
• NETSTAT: sockets and routes, not assigned addresses.
• WINIPCFG: Windows 9x GUI utility, not NT.
• PING: reachability test, not configuration display.

Common Pitfalls:
Confusing netstat -r (route table) with IP address assignment; expecting ping to reveal local addresses; using winipcfg on NT where it is unavailable.

Final Answer:
IPCONFIG.