Network bring-up checklist: A newly installed workstation on an Ethernet LAN cannot communicate with the network. What should you check first before reinstalling software or reconfiguring protocols?

Introduction / Context:
When a workstation cannot reach the network, best practice is to start at the physical layer and work upward (the OSI model approach). A quick check of link status often isolates cabling or switch-port issues without diving into software changes.

Given Data / Assumptions:

• Fresh installation or newly connected device on Ethernet.
• No connectivity observed (no ping, no DHCP, no browsing).
• We seek the first, fastest indicative check.

Concept / Approach:

Layer 1 verification precedes configuration. LEDs on the NIC and switch indicate whether a link is established. If link is down, no amount of driver reinstallations or IP tweaks will help. If link is up, proceed to IP configuration (e.g., DHCP address, subnet, gateway) and higher-layer tests.

Step-by-Step Solution:

Verification / Alternative check:

Loopback/cable testers and swapping cables/ports quickly confirm physical issues. If link remains solid but no network access, then move to driver and protocol layers.

Why Other Options Are Wrong:

• Reinstall drivers/protocols: premature if there is no physical link.
• Verify IP configuration: useful only after link is confirmed.
• None of the above: incorrect because checking link LEDs is the right first step.

Common Pitfalls:

Skipping physical checks, overlooking disabled switch ports, or using the wrong VLAN/untagged port, which can mimic link but block traffic.

Final Answer:

Verify the link status on the computer's network card