Other Devices Ethernet Controller

[Channing Arther]

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.

So, I had to install a new Power Supply for my PC a couple days ago because my PC wouldn't start. After I had life again and thought all was good, I immediately noticed I was unable to connect to my wired internet.

I went to device manager and noticed my ethernet device wasn't even listed under network adapters but now under other devices as "ethernet controller". When I clicked on it, I was met with the following device status: -The drivers for this device are not installed. (Code 28) -There are no compatible drivers for this device. -To find a driver for this device, click Update Driver.

I tried troubleshooting multiple times through windows but when I followed their steps and restarted my PC, still nothing changed. Then, I went to Intel forums, videos, and websites supporting my issue and went through various guided steps to try and solve this.

After installing the latest version of Intel Ethernet Adapter Complete Driver Pack and many hoops and bounds later, I went back into device manager and noticed my ethernet device was now showing under network adapters as "Intel(R) Ethernet Controller (2) I225-V".

In device manager, I attempted to automatically install the driver through windows and it would not work being unable to find a compatible driver. I also tried manually installing it and choosing a driver and was still unsuccessful.

After enabling/disabling my ethernet device, trying the steps over and over again, trying to install an older version of the driver, updating my BIOS, made sure my ethernet cables were stable and good, and going down tons of rabbit holes, I end up where I started with the same device statuses.

2. I don't know what caused my last power supply unit to fail. I was able to power on and operate my PC the night before like any typical night, but the next day it wouldn't power on at all after trying a different power cord, outlet, etc.

When I go into device manager and attempt updating the driver with the file I extracted from the Intel Ethernet Adapter Complete Driver Pack zip file I downloaded, I am met with this screen (image applies to both searching automatically for drivers, and browsing my PC files for driver.

I also made the discovery that when I click on "Let me pick from a list of available drivers on my computer", and choose any of the listed Intel driver devices to try and install, I am met with the same (Code 10) this device cannot start. Additionally, now my device name of "ethernet controller" moves from the other devices tab to under the network adapter tab and matches the name of the driver device tried installing prior as you can see in this image:

So I went to your link and downloaded and extracted the zip file of "Intel Network Drivers" version 26.2.0.1 under the subcategory "LAN Drivers". I auto ran the app and attempted to install it was met with this screen:

Since you are using MSI product, with embedded NIC, contact MSI support for further assistance. They may be able to provide additional troubleshooting steps or even replace the motherboard if it is found to be defective.

Please be informed that we will now close this request since we haven't received any response from our previous follow up. Just feel free to post a new question if you may have any other inquiry in the future as this thread will no longer be monitored.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

Hi, can anyone help me. When I run a Linuxmint HVM on qubesos I can connect another device to this VM via ethernet and it is going through the qubesos networking. When I am trying the same thing with a fedora or debian based qube using network-manager I cannot get it to work. Does anyone know how to set this up?

I would like to connect a device (e.g. a tablet) via ethernet to a template based (H)VM (debian or fedora under R4.2) and then I want to pass this connection upstream to the internet. It would look like this:

I have set up a Raspberry Pi 3 running Raspbian Bullseye and connected it to WiFi. This is being done on a college campus, so I cannot give my Pi a static IP. However, I can register it with my college's network which gives me a hostname that points to my Pi.

I am trying to use the Pi to control another device over ethernet using Telnet in a python script. The other device is a controller for a blackbody. The controller itself has a configurable static IP address for ethernet. It does not provide any other network information (gateway, dns, subnet).

I want to set up the Pi so that it is connected to the WiFi, but also connected to this controller through ethernet, that way I can SSH into the Pi and run a program that controls the blackbody controller.

Edit: added that I am trying to connect using Telnet over ethernet.Edit: I have also figured out that the black body controller can be configured to operate in DHCP mode. Is there a way to configure the Pi to give the controller an IP over ethernet?

If you can't edit the IP of the device and it's fixed, then in the raspberry put something in the same subnet as the device. In other words, copy the first 3 parts of the IP the device has and for the last part put something other than the device's last number. Hope it makes sense.

When plugging an ethernet cord into the raspberry pi, the pi automatically assigns the port an IP on a specific subnet. From there, I just had to configure the controller device to have a static IP on the same subnet as the Pi's ethernet port. From there, it connected without issue.

3a8082e126