In computer networking support, the first step in troubleshooting many user-reported problems is to verify the client’s basic TCP/IP stack status and configuration before checking servers or advanced settings. What should you confirm first on the affected workstation?

Introduction / Context:
In day-to-day desktop and helpdesk networking, many incidents stem from local misconfiguration rather than core network outages. A systematic approach starts at the endpoint's TCP/IP stack—the foundation required for any IP-based communication.

Given Data / Assumptions:

• Client is unable to access network resources.
• Environment uses standard IPv4 with common Windows/Linux tools.
• No prior confirmation exists about local TCP/IP health.

Concept / Approach:
Always begin troubleshooting from the lowest practical layer: the client's network stack and link status. Confirm that the TCP/IP stack is present, enabled, and bound to the active adapter. Without a working stack, further tests (DNS, routing, servers) will fail.

Step-by-Step Solution:

Verification / Alternative check:
Use ipconfig/ifconfig to confirm configuration and ping/arp to validate local resolution. If loopback fails, the stack is broken regardless of network conditions.

Why Other Options Are Wrong:

Common Pitfalls:
Jumping to DNS or server-side issues before validating the client, ignoring disabled adapters, and skipping loopback tests.

Final Answer:
TCP/IP is installed correctly on the client.