How to Check Network Card Status & Specs (2026 Guide)

You’re staring at a download speed test that’s lagging half of your plan’s promise, and you’re wondering if the bottleneck is your ISP, your router, or that obscure piece of hardware buried inside your computer. You need to update the driver, but you don’t even know what card you have. This is the frustrating gap between "I need my internet" and "I need to understand my machine."

This guide is built to be the single source of truth for that gap. I’ve spent the last decade troubleshooting network stacks for everything from home offices to data centers, and I’ve learned that how to check network card status isn't just about finding one line of code. It’s about knowing where to look. Whether you prefer the visual comfort of the Device Manager or the speed of the command line, we’ll cover how to verify drivers, check your MAC address, and diagnose hardware limits across Windows, macOS, and Linux. By the end, you won’t just see your adapter; you’ll understand what its status actually means.

View Network Card Details in Windows (GUI Method)

For most users, the graphical interface is the fastest path to a clear answer. Windows bundles most of the hardware intelligence into the Device Manager and Network Adapter Properties. If you view network card details windows-style, you get immediate visual feedback—icons that tell you if a device is enabled, disabled, or throwing an error code.

Using Device Manager to Identify Hardware

I find that people often overcomplicate finding their hardware. You don’t need to dig through Control Panel submenus. In Windows 10 and 11, the search bar is your best friend. Click the Start button (or press the Windows key), type Device Manager, and hit Enter.

Once it opens, look for the Network adapters section. It’s usually collapsed; click the arrow > next to it to expand. You’ll likely see multiple entries here—maybe a "Realtek PCIe GbE Family Controller" for wired connections and an "Intel(R) Wi-Fi 6 AX201" for wireless.

Here is where you need to pay attention to the icons. In my experience, a clean entry with no icons means the driver is installed and the hardware is active. A small down arrow ∨ means the device is manually disabled—you can re-enable it by right-clicking and selecting "Enable device." But the real red flag is the yellow exclamation point !. This indicates Windows detected the hardware but failed to install a compatible driver. If you’re seeing that, we’re past the "check" phase and into the "fix" phase.

Checking Driver Version & MAC Address via Properties

Once you’ve identified the correct adapter, right-click it and select Properties. This is the Network Adapter Properties window, and it holds the specific data you’re looking for.

To find the driver version, click the Driver tab. You’ll see a "Driver Date" and a "Driver Version." If you’re trying to match a download from the manufacturer’s site, this number is your key. For example, a date of 2026 suggests a very recent update, while a date from 2020 might be stale for a newer piece of hardware.

To find the MAC address (Physical Address), click the Details tab. In the dropdown list labeled "Property," select Network Address or Physical Address. The value will be a string like A4:BB:CC:12:34:56. This is the unique hardware identifier used by your router to recognize your specific device. While you’re in the Details tab, you can also select Hardware Ids if you need to manually search for a driver on the vendor’s website. That ID string is more reliable than the human-readable name, which can sometimes be generic.

Command Line Tools: Fast Ways to Check Network Info

Sometimes you’re troubleshooting a headless server, or you just want an answer in five seconds flat. In my 15 years of sysadmin work, the terminal has always been the tool that cuts through the noise. How to check network card via command prompt (or Terminal) gives you raw data without the UI abstraction layer.

Windows: Using ipconfig /all and PowerShell

Open the Start menu, type cmd, and run Command Prompt. The gold standard for quick checks is:

ipconfig /all

Scroll to your active adapter (usually "Ethernet" or "Wi-Fi"). You’ll see the Physical Address (MAC) and the DHCP Status (whether you’re getting an IP automatically). However, ipconfig is an older tool. It won’t tell you the driver version or the specific hardware model name as clearly.

For deeper insights, use PowerShell. Right-click the Start button and select Windows PowerShell. To get a clean list of adapters and their status:

Get-NetAdapter | Format-Table -AutoSize Name, Status, DriverVersion, LinkSpeed

This one-liner is powerful. It shows you if the adapter is "Up" or "Disconnected," the exact driver version string, and the current link speed. If you’re scripting an automated check in your environment, this command is vastly superior to parsing the text output of ipconfig.

Linux: Using lspci, ip, and ethtool

On Linux, the hierarchy of tools is distinct: hardware identification first, then status, then deep stats.

1. Identify the Hardware: Use lspci. This reads the PCI device tree.

   lspci | grep -i network
   

   Output example: 03:00.0 Ethernet controller: Intel Corporation I210-LM [8086:153B] (rev 03). This is the most authoritative source for the model number.

2. Check Status & MAC: Use the ip command.

   ip link show
   

   Look for the state UP or state DOWN indicator and the link/ether field for the MAC address.

3. Check Speed & Duplex: This is where Linux shines for diagnostics. Use ethtool.

   ethtool eth0
   

   Note: Replace eth0 with your actual interface name, which might be enp3s0 or wlan0 on modern systems. This command outputs the Link detected: yes/no, Speed: 1000Mb/s, and Duplex: Full. If your speed is stuck at 100Mb/s when you expect 1000, ethtool will often show if auto-negotiation failed.

macOS: Using system_profiler and ifconfig

Apple’s ecosystem mixes hardware and software in a way that’s distinct from PC. For a detailed dump of all hardware, including Wi-Fi cards:

system_profiler SPNetworkDataType

This provides a nested structure showing the Ethernet or Wi-Fi interface, its MAC address (labeled as "Hardware Address"), and the speed. It’s verbose, but it tells you exactly which chips are present.

For a quick status check, ifconfig is still useful, though ifconfig on macOS can be confusing with virtual interfaces. To just see the active interfaces:

ifconfig | grep -A 2 "inet"

Diagnosing Network Card Health & Driver Status

Knowing where to look is only half the battle. The real value comes from interpreting what you see. Check network adapter driver integrity is the most common reason for intermittent connectivity. Here is how I approach a "is my card broken?" scenario.

Identifying a Bad Network Card: Signs & Symptoms

Not all failures look the same. In my experience, I categorize them into three buckets:

• Intermittent Disconnections: The network works, then drops for 5-10 seconds, then reconnects. This is often a driver bug or a power-saving feature (ASPM) on a Wi-Fi card. It’s rarely a physical break in the card itself, more likely a software handshake failure.
• High Latency/Packet Loss: You can ping, but the times are erratic. If you’re using ping -t on Windows and seeing timeouts, the card might be struggling with interrupts. Check your "Adapter Type" properties and disable "Green Ethernet" or similar power-saving features to test.
• Total Failure/No Link: The light on the Ethernet port stays off. This is usually physical. A bad cable, a dead port on the router, or a physically disconnected card inside a desktop tower. If the card is onboard (laptop/ultra-thin), a total failure often points to a dead solder joint or a failed integrated circuit, which is difficult to repair.

If you’re seeing a Blue Screen (BSOD) specifically with ndis.sys or e1g60x64.sys errors, the network stack is crashing. This is a driver-level failure. The card is working electrically, but the software bridge is broken.

Verifying Driver Integrity & Updates

Don’t just hit "Update Driver" in Device Manager blindly. Windows Update often installs a generic Microsoft driver, not the vendor-specific driver. The vendor driver (from Intel, Realtek, AMD, etc.) contains the power management and specific chipset optimizations that the generic one lacks.

Here is the logic flow I use when an adapter is missing or acting up:

1. Check "Unknown Device": If you see a generic "Network Controller" with a question mark, right-click it and select "Update driver." Windows may find it.
2. Scan for Hardware Changes: If you recently installed a new card or re-seated an old one, right-click the top of the Device Manager window and select "Scan for hardware changes."
3. The BIOS Check: If the card isn't in Device Manager at all, it might be disabled in the BIOS/UEFI. Boot into your BIOS (usually Del or F2), go to the "Integrated Peripherals" or "Onboard Devices" section, and ensure the Ethernet/Wi-Fi controller is enabled. This happens more than you’d think after a battery reset or CMOS wipe.
4. Vendor Direct: If the driver is corrupt, download the latest version from the manufacturer’s support site, not from a third-party "driver cleaner" tool. I’ve seen too many systems bricked by those utilities.

Advanced: Verifying Speed, Duplex & Hardware Limits

One of the most common complaints is "my internet is slow." Often, it’s not the internet. It’s the link between the PC and the router.

Understanding Link Speed and Auto-Negotiation

How to check network card speed and duplex settings is critical because a mismatch here can cut your effective bandwidth by 90%.

Most modern cards support Auto-Negotiation. This is a handshake where the card and your router/switch agree on the fastest common speed. If auto-negotiation fails, the link might drop to 100 Mbps (half-duplex or full-duplex) even if both devices support 1000 Mbps (Gigabit).

To check this in Windows:

1. Open Network Connections (ncpa.cpl).
2. Right-click your adapter > Status > Properties.
3. The "Link Speed" or "Speed" field will show you the current negotiated speed, not the maximum capability. If it says 100.0 Mbps, your connection is bottlenecked.

In Linux, ethtool (as mentioned earlier) is superior because it shows the "Duplex" setting explicitly.

Why does this matter? Half-duplex mode is almost obsolete. If your card is forced into half-duplex, it can only send or receive, not both at once. This causes massive latency. If you see "Duplex: Half," check your physical cabling. Often, a damaged Ethernet cable forces the link to fall back to Half-duplex to maintain stability. Replace the cable before you blame the card.

Also, be aware of hardware limits. A 2.5G or 10G card is useless if your router only has Gigabit ports. The link will negotiate to 1000 Mbps. Checking the speed tells you what you’re getting, but knowing your router’s specs tells you what you could get.

Frequently Asked Questions

How do I check my network card model? The quickest method is to open Device Manager, right-click your network adapter, select Properties, then the Details tab. Select Hardware Ids from the dropdown. Copy the first string (e.g., PCI\VEN_8086&DEV_153B) and paste it into Google. The second part (VEN_8086 is Intel) identifies the manufacturer. Alternatively, run lspci | grep -i network on Linux for a direct model name. What is the command to check network card in Linux? The standard command to identify the hardware model is:

lspci | grep -i network

This outputs the PCI device ID and the human-readable name, such as "Intel Corporation I210-LM." For status, use ip link show.

Why is my network card not showing up in Device Manager? Three common causes:

1. Driver Deletion: The driver was uninstalled but the hardware is still present. Use "Scan for hardware changes" in Device Manager.
2. BIOS Disablement: The onboard Ethernet/Wi-Fi was disabled in the UEFI settings.
3. Physical Disconnection: For desktops, the cable or antenna is loose, or the card itself has come out of the PCIe slot (rare, but happens after moving the PC).

How do I check if my network card is 1000 Mbps capable? Check the Link Speed in the adapter's Status window in Windows, or use ethtool in Linux. If it shows 1000Mb/s, it is capable and currently connected at that speed. However, the card's maximum capability is defined by the chip. Most modern "Gigabit" cards top out at 1000 Mbps. If you have a "2.5G" or "10G" card, the status will reflect the negotiated speed, which might be lower if your router doesn't support the higher speed.

Conclusion

Navigating the layers of hardware and software is rarely intuitive. The key takeaway from this guide is that how to check network card status isn't a single action, but a layered process: identify the hardware (Device Manager/lspci), verify the driver (Properties/ethtool), and validate the physical link (Speed/Duplex settings).

Remember that knowing your exact model number—found via Hardware IDs or lspci—is the single most important step in finding the right driver. A generic driver will keep you connected, but a vendor-specific driver will keep you fast and stable. For advanced users, the command-line tools aren't just for show; they allow you to script health checks and monitor duplex mismatches before they affect your workday.

Bookmark this page for the next time your connection gets flaky. If you’re currently stuck with a "missing" adapter, head back to the Diagnosing section—the BIOS check is a step 80% of users skip. And if you’re using a specific OS or vendor stack that feels different from these examples, drop a comment with your setup. I read all of them, and I’m happy to point you in the right direction for your specific hardware.