A database server that normally links at 1 Gbps is intermittently unreachable. The switch port connected to the server shows thousands of CRC input errors and has autonegotiated down to 100 Mbps/Full. Other switch ports are error-free. Which action should you take first to restore reliable connectivity?
Update the server's network card driver and firmware to the latest versions.
Clear the switch port counters and monitor the interface for 24 hours before acting.
Manually force both the NIC and switch port to operate at 100 Mbps full-duplex.
Replace the existing patch cable with a certified Cat 6 cable and verify the link speed.
CRC errors on a single link combined with an unexpected drop from 1 Gbps to 100 Mbps almost always point to a damaged or poorly terminated cable. Replacing the patch cord with a known-good, standards-compliant Cat 5e/6 cable is the quickest way to confirm and usually eliminate the fault. Hard-setting speed/duplex or updating drivers may mask symptoms but will not fix physical damage, while clearing counters only delays corrective action.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are CRC errors, and why are they significant in networking?
Open an interactive chat with Bash
Why does link speed autonegotiate down, and how does it relate to poor cables?
Open an interactive chat with Bash
What makes Cat 6 cables a better choice for network reliability?