Random Number GodsRNG · Enemy Territory · Battlefield · D&D
Friday BF64 + Sunday D&D

Check the calendar. ET pubs running the new Frostbite rotation all week.

PC won’t recognize ethernet ?

Permalink Preview Print PC
silver_rain
Covert Ops
Members
60 posts 30 Jan 2026 joined
7 Sep 2026 at 15:01 #1

So, when plugging in an ethernet cable, the light on the back of the PC is green but Wifi is still being used. Ethernet doesn’t even get recognized. I tried to trouble shoot this a bunch of ways like reinstalling LAN drivers for my motherboard, unplugging and plugging the cable back in, etc.

When going into device manager, the ethernet controller device only shows up under HIDDEN devices. When inspecting the properties, it says “Currently, this hardware device is not connected to the computer (Code 45).” The device is very much plugged in.

So I moved onto to BIOS to see if my Intel LAN controller was disabled, but it wasn’t. But i tried disabling it, then saving and resetting, and then enabling, and saving and resetting and that somehow worked? My PC recognized ethernet after that. But the next day my PC was back to not using ethernet.

Wondering why this was happening and if there’s a more permanent fix.

silver_rain - BF64s
PTFO or mute.

willyxNilly
Engineer
Members
43 posts 13 Jan 2023 joined
7 Sep 2026 at 15:05 #2

Have you enabled the Ethernet port?

willyxNilly - BF support
Ammo box is friendship.

profae
Engineer
Members
39 posts 27 Oct 2023 joined
7 Sep 2026 at 15:05 #3

Try going to device manager and unistalling the LAN controller then restart PC

profae - Lurker
I read more than I post.

GunOut
Engineer
Members
36 posts 12 Dec 2020 joined
7 Sep 2026 at 15:08 #4

Check what model Motherboard you have, go to whichever is the appropriate website for your motherboard and find the drivers section (usually under support)

There is a chance there are ethernet drivers listed there. Download and install them. Hope this helps

GunOut - EU evenings
CET after work.

Foxyswager
Engineer
Members
41 posts 11 Feb 2022 joined
7 Sep 2026 at 15:13 #5

Find out if there's known issues with the LAN on Motherboard (LOM) for your system.

I have known system models to ship with faulty LOM requiring an expansion card to have a functional NIC. The vendor blocked the dodgy Broadcom LOM NIC ports with rubber bungs.

The LOM may be disabled by open-firnware intended to give just the minimal support needed for Linux open-boot. But you would have mentioned if the BIOS firmware didn't look like the vendors?

Ground-loops can damage NICs.

This is not an exhaustive list.

Foxyswager - ET / smokes
Utility first.

rxnxko
Field Medic
Members
32 posts 19 Jun 2022 joined
7 Sep 2026 at 16:10 #6

Driver. It shouldn’t be in the hidden drivers

rxnxko - Map votes
Frostbite supremacy.

dania200421
Engineer
Members
40 posts 16 Sep 2024 joined
7 Sep 2026 at 16:19 #7

So physically the computer does recognize ethernet it's not the PC's fault.

Something hid the ethernet, were you trying to tweak performance at some point in time? Are you using a Wi-Fi driver that likes to be dominant in all things and force the Wi-Fi active?

That you found the ethernet is hidden suggests that something did it again that software/os/something ....

If you're confident you have all the drivers downloaded for both the ethernet and the wireless, uninstall all of your network and tell it to remove the drivers and software for it.

Restart the computer, and it will come up and identify it sees these devices. Start off with your wired connection, install the drivers for those and see if it works.

Then add back the Wi-Fi.

Please note, that I'm not taking into consideration if you've done anything to do USB networked devices, Bluetooth Network devices, or any of the killer app for Wi-Fi stuff that at best outside of professional hands does nothing but add frustration and s*** to your networking.

dania200421 - Old guard
Jaymod days. Still here.

Sign in to reply.