Ethernet Device Manager

[Young Vadlapatla]

WhenI originally wrote this troubleshooting guide, not all PCs had an Ethernet adapter. Nowadays, it's pretty much a given. Even so, it's quite possible - especially when building a new computer from scratch or reinstalling Windows - that the drivers are not installed and the adapter isn't working. There are some easy tests that can be done. If you can't get similar successful results to those you will see in this section, then your Ethernet card/port/adapter is not properly installed or the drivers it relies upon are not properly installed. You'll likely just be wasting your time to even try to go on. These tests are simple, but it's also essential that your Ethernet ports pass them.

Software driver upgrades have also been known to cause issues and break working systems. Sometimes issues arise because the system is trying to be "smart." I have a laptop that attempts to conserve battery life by turning off the power to the wired Ethernet port when it's running on the battery. If there isn't a wired Ethernet connection up when I unplug the AC power, it shuts the port off. The bad thing is it doesn't turn the port back on when inserting a cable thereafter so long as it remains on battery. (There's a Control Panel in my particular case that will let me re-enable the wired Ethernet port.) Other laptops have a physical switch that turns off the wireless Ethernet adapter. These can get switched off by accident. Suffice it to say there are cases where an Ethernet adapter may not be recognized even when you know it is (or was) there.

The first test is to just verify that the Ethernet port is recognized by the operating system. We will be using a Windows 10 operating system for the screenshots. (The original graphics in this section were taken from a mix of Windows 2000, XP and Vista, Windows 7, and Windows 10 machines - just to give you an idea of how long these issues have been around.) In most of the tests, the various flavors of Windows machines have the same tools with a slightly different look. Occasionally, manufacturers forget to install the drivers for some of their devices, and sometimes a driver installed for some completely different device can interfere with the LAN driver. For me, this occurs most often when performing a major upgrade (such as upgrading from Windows 10 to Windows 11).

Alternatively, click on the Start button (typically in the lower-left corner), and type device manager into the search box. Choose the Device Manager Control Panel from the list (as highlighted in the picture below).

If your Ethernet adapter is recognized as a device by the operating system, it will appear under the Network adapters portion of the Device Manager list. (By default, the devices are listed alphabetically by type.) If you see Network adapters listed, click on the "caret" to the left of it to expand that entry. You could see your specific Ethernet card (NIC) listed there as shown below. If you don't see such an entry, see Problem 1: There isn't any entry named "Network adapters" in the Device Manager or there is no entry in the Network adapters that corresponds to my Ethernet adapter.

The computer shown above has two Ethernet adapters (Intel I211 Gigabit Network Connection and Realtek PCIe 2.5GbE Family Controller) and a wireless Internet adapter (Intel Wi-Fi 6 AX200 160MHz). Right-click on the entry for the network adapter that we are troubleshooting (e.g., Intel I211 Gigabit Network Connection) and choose Properties from the pop-up menu. (You can also just double-click on the entry.)

The usual culprit is a bad or missing driver when you know you have the Ethernet adapter installed, but it doesn't appear under the Network adapters list. Look in the Device Manager for the Other devices entry. (Generally, there will not be an Other devices entry if all devices are installed properly on your PC or there will not be any devices listed under the entry.) If there is one, expand it by clicking on the plus sign. If you see a device with a name similar to "Ethernet Controller," it's almost guaranteed you have a (lack of a) driver problem. Possible solutions:

What you want this field to say is, "This device is working properly." If you have any other message, you likely have a wrong, corrupted or missing driver. Microsoft has a nice list of the device manager error codes here, along with some suggested solutions. Generally, uninstalling and reinstalling the correct driver fixes this issue.

Running Windows 7 64 bit on desktop computer. Installed driver for Win 7 but computer does not recognize the deveice. It does not appear in Device Manager. I did plug the devide in too early, before installing the sofware from CD. Cancelled the autoplay install, installed the Win 7 driver but no connection. When I plug the ethernet cable into the devicethe light does come on steady.

We use Amazon exclusively, partly because returns are handled by them and are no-hassle. You might get a follow-up email from us. If Amazon is slow in any way in getting the refund, please just email sup...@plugable.com.

In Device Manager, delete the driver for the old adapter and choose the option to also delete the driver files. Do the same for this new adapter. Make sure the old adapter is NOT plugged into your PC. Reboot.

Install the new adapter according to the instructions. The new adapter may have to be plugged into your PC when you install the driver. OR NOT ! Read and follow the installation directions to know whether or not to have the adapter plugged in while installing its driver.

Double check in network manager (click on the indicator) that you have Enabled Networking ticked and you should also force deletion of old "wired connections" and selecting the new wired connection shown in the network manager indicator.

I had the same problem with a fresh install on my Asus Eee PC 1005HA. The live environment worked with no problems, but once installed I couldn't get the connection to respond or to not read "device not managed". When I changed the text in this configuration file and restarted Network Manager everything worked!

Explanation, Please Read So you don't screw up:Network-manager presumably looks at both 10-globally-managed-devices.conf files in the two aforementioned directories. If neither of them have [keyfile] seperated by a new line, network-manager crashes (confirmed). If both of them have [keyfile] separated by a new line, presumably as before network-manager will crash (unconfirmed). Presumably [keyfile] means "use this file as config" hence the aforementioned network-manager behavior. So one of those files should be empty and the other should have [keyfile] followed by new line and the rest of the command. So in Ubuntu the /usr/ file will always be zeroed unless possibly way back like 14.04 or earlier. But for other distros it might be reverse where /etc/ file is zeroed and /usr/ file edited and formatted properly.

Situation like this may appear, when one runs pppoeconf or something similar and the command overwrites the setting saved by NetworkManager. Even though the device seems to be working properly, Network Manager shows device status to be unmanaged.

or totally remove the network manager thru the package manager or terminal and use the /etc/network/interfaces and /etc/resolve.conf file to control your connections. If not you will see the error you are getting. Even with static IP I've found that the network manager makes things easy and you can configure your IPV4 connections thru the menu.

This is because the alternate images were for a period of time, configuring the wireless networks in /etc/network/interfaces; which causes NetworkManager to, on purpose, ignore the interface and consider them online.

A good solution if you want to simply use your wireless connection (or wired) with DHCP is to comment out these settings in /etc/network/interfaces for all interfaces except lo, and reboot your system or restart NetworkManager like so:

Just to add a non-default answer, this can also happen if your computer has a hardware ON/OFF switch for the Wi-Fi interface. If you have such a "killswitch", ensure that you haven't accidentally turned the interface off

In 11.10 you can go to System Settings and you should see a Network Icon. Run that utility and you should see tabs for your network devices, wired and wireless. Each tab has a slider that allows you to switch the device off. Or in your case switch eth0 or wired connection 1, as it is now called, on. May be. At least check that it not switched to off.

So I had recently built a new pc and once I got it all setup with installing all the drivers and such, I go plug in the ethernet cord and there is no connection. I go to the device manager and it says that Intel(r) Ethernet controller (3) I225-V is working properly but in events it says *attached file*. I really have no clue how to fix this issue. Please feel free to ask any further questions and I can try to answer them tot he best of my ability.

So I had plugged in my working ethernet cord and on the motherboard back panel, there is no light indicating connection but on my router, next to the ethernet spot where I had plugged in the other end of the cable, there is a blinking red light. I tried disabling and re enabling the adapter and that didn't change anything.

The driver certificate is expired, and Windows is puking it out. Intel needs to update their driver pack, and hopefully start using signing certs that last a little longer than 1 year. There's very little additional security benefit to having short validity periods like this. Generate the strongest cert possible, and give it at least 5 years to breathe. The Sectigo CA root and intermediate certs in this certificate chain are valid for 10 years. Why make things harder than they need to be?

I too have run into this issue with my own MSI MAG Z790 Tomahawk. I've done the weirdest things with the drivers and it still won't budge. I hope a fix is released soon because running over Wifi only gets you this far.

Tomorrow I will open a ticket on my own to solve this problem.

Sincerely,

3a8082e126