Ethernet Link Speed and Network Checks on Used PCs

Ethernet testing should separate the PC's network adapter from the cable, router, internet service, and remote server. A fast internet speed test cannot isolate those parts. Use a known cable and a known local network port, confirm negotiated link speed, then move data across the local network while watching for drops and errors.

Inspect the jack and identify the adapter

Check the RJ45 jack for bent contacts, debris, looseness, corrosion, or a broken retaining edge. In Windows Device Manager, record the adapter's exact model and driver status. Compare it with the motherboard or laptop specification. An inexpensive add-in network card may be a valid repair, but it also means the original onboard port may not work.

Confirm negotiated link speed

Open the Ethernet connection properties and read the current link speed. It should match the highest common capability of the adapter, cable, and network port, subject to configuration. A gigabit-capable adapter repeatedly linking at 100 Mbps often points to a cable pair, connector, port, or forced setting problem. Link speed is not the same as actual file-transfer throughput.

Eliminate cable and switch variables

Bring a known-good cable rated for the target connection and use a network port already proven at that speed. If negotiation is low, try one alternate cable and switch port before blaming the computer. Leave speed and duplex on automatic unless the network specifically requires manual configuration. A forced mismatch can create poor performance and errors while still showing connected.

Run a local sustained transfer

Transfer a large disposable file to or from another wired computer or local storage device that is fast enough for the test. A local throughput tool can isolate network performance more precisely. Watch Windows for disconnects and check adapter statistics for errors. Avoid using one internet download as the verdict because the service, Wi-Fi segment, server, and routing may be limiting.

1. Use a known cable and verified network port.
2. Record adapter identity and negotiated speed.
3. Run a sustained local transfer in both directions.
4. Repeat after sleep and inspect for disconnects or errors.

Test sleep, wake, and driver behaviour

Let the PC sleep, wake it, and confirm the adapter reconnects at the expected speed. Check for warning icons, repeated device resets, or connection loss under load. Manufacturer drivers can matter, especially for multi-gigabit adapters, but do not install random driver packages during a sale. Record the current version and use the board or system maker's support page later.

Place Ethernet in the full connectivity check

A failed onboard port may be repairable with a PCIe or USB adapter, but laptops and small systems have fewer convenient options. Test Wi-Fi and Bluetooth separately with our wireless connectivity guide, and test USB adapters through the port routine. Price the machine according to the connection you actually need.

Frequently asked questions

Why does a gigabit Ethernet port connect at only 100 Mbps?

A damaged cable pair, worn connector, limited switch port, forced speed setting, or adapter fault can cause lower negotiation. Substitute known-good network parts one at a time.

Does an internet speed test verify the Ethernet port?

Not by itself. Internet service and remote servers can limit the result. A sustained transfer between known local wired devices isolates the LAN more effectively.

Should speed and duplex be set manually?

Usually no. Automatic negotiation is the normal setting. Manual values on one side can create mismatches unless the network is intentionally configured that way.

Can I replace a failed onboard Ethernet port?

Often a desktop can use a PCIe adapter, while a laptop can use USB or a dock. Confirm available slots, ports, drivers, and required speed first.

Key takeaways

• Negotiated speed and sustained local throughput answer different questions.
• Use a known cable and network port before blaming the used PC.
• Test reconnect behaviour after sleep and watch for errors during load.