TELEMETRY // Normal: Valid DHCP lease | Fault: APIPA 169.254.x.x
Why It Happens: Corrupted Winsock or IP stack files prevent the OS from correctly interpreting DHCP packets from the router.
Fast Verification Test: Run 'netsh winsock reset' and 'netsh int ip reset' in an Admin Command Prompt.
Tools Needed: Windows Admin Terminal
- Open CMD as Admin
- Run reset commands
- Restart PC
⚠️ Safety Boundary: Ensure all unsaved work is closed before rebooting.
TELEMETRY // Normal: Service Status Running | Fault: Service Stopped
Why It Happens: The Windows service responsible for requesting IP addresses from the router has stopped or crashed.
Fast Verification Test: Check 'services.msc' to verify 'DHCP Client' is set to Automatic and Running.
Tools Needed: Services snap-in
- Open services.msc
- Locate DHCP Client
- Set to Automatic and Start
⚠️ Safety Boundary: Do not disable core system services.
TELEMETRY // Normal: Driver version matches OEM | Fault: Generic/Outdated driver
Why It Happens: Windows Update may have installed a generic driver that fails to negotiate properly with the NIC hardware.
Fast Verification Test: Right-click NIC in Device Manager and select 'Uninstall device', then reboot.
Tools Needed: Device Manager
- Uninstall driver
- Reboot to trigger auto-reinstall
- Update from OEM site if needed
⚠️ Safety Boundary: Ensure you have a backup driver installer if the internet remains down.
TELEMETRY // Normal: Link LED blinking | Fault: No link light
Why It Happens: A damaged Ethernet cable or faulty router port prevents physical layer communication.
Fast Verification Test: Swap the Ethernet cable with a known-good one and try a different router port.
Tools Needed: Cat6 Ethernet Cable
- Replace cable
- Test alternate port
⚠️ Safety Boundary: Do not force cables into ports; ensure the locking tab clicks.