Unidentified Network on new Windows 10 install, Gigabyte z170x onboard ethernet Killer e2200

parappa

Commendable
Jul 10, 2016
2
0
1,510
I'm building a new PC with Windows 10 and so far I haven't been able to get a network connection on it. All I'm trying to do is use the wired ethernet. It always gets stuck in the status "Unidentified Network" and I cannot even ping 192.168.0.1 (which is definitely my router's IP address, I can access it from my laptop.)

The Gigabyte GA-Z170X has two on-board ethernet adapters, one Killer e2200 and the other an Intel one. I am trying to connect to a Motorola Surfboard SBG6782 combo modem and router (which I do not recommend; it was supplied by my internet provider and I've been meaning to replace it.)

I've tried updating my network drivers and also tried uninstalling just the Killer drivers to just get the Intel adapter working. I also tried setting up a static route but the best result I've had so far is that my adapter decides more quickly that it cannot get an IP address from my router. Both of the ethernet lights on the back of my rig do light up, although one blinks green for a while and the other comes on as solid orange.

[This user had the same trouble](https://www.reddit.com/r/techsupport/comments/41bvbr/gigabyte_z170xgaming_7_ethernet_ports_not_working/) but the solution was merely to install drivers off of the supplied mobo CD disc, which I have already done. I also tried downloading more recent drivers.

Some commands I've used to try and reset my ip config to a reasonable state are,

netsh winsock reset catalog
netsh int ip reset

I've also seen suggestions to run

ipconfig /release /renew

But my adapter is not in a state to do this.

When I run the Win 10 diagnostic tool, it says that one of the protocol drivers is not installed and tries to fix that, but it fails. The missing protocol seems to be Microsoft Network Adapter Multiplexor Protocol.
Based on other posts I've seen, the issue could be some kind of software that I have installed, but I have no idea what that could be. The Killer Networking stuff should be clean and I don't have any anti-virus running yet.

I found [a duplicate thread](https://www.reddit.com/r/pcmasterrace/comments/3f0ler/windows_10_killer_network_drives_pls_help_no/) and it seemed oh so close, but it didn't work for me.

In order to get access to the Killer Bandwidth Control protocol, I had to re-install the whole Killer / Bigfoot suite. Sure enough it showed up, but disabling this protocol hasn't made any difference so far. Which actually isn't all that surprising given that I've tried replacing my driver with others that didn't include that protocol, and that hasn't worked either.

For what it's worth I have been able to get wired internet out of my router before. I've connected a Raspberry Pi to it and a printer, both were able to get on the network, and the Pi had web access.

I'm also trying to follow [this thread](https://forum-en.msi.com/index.php?topic=174229.0) in case it is in fact remnants of the Killer Suite that is interfering with my ethernet controller. I haven't been able to find a working link to the Killer Cleaner tool but I did find links to their [vanilla drivers](http://www.killernetworking.com/product-support/driver-downloads/standard-drivers).

Found an [interesting thread](https://www.techpowerup.com/forums/threads/guide-turn-your-killer-e2200-nic-into-qualcomm-atheros-ar8161.198899/) with instructions for installing Qualcomm Atheros AR8161 drivers for the Killer e2200 device. I gave it a try but it didn't seem to fix anything. :/

I've also gone into the BIOS and turned off the Intel adapter to see if that helps getting the Killer e2200 to work, but no dice there either.
 
Did you install all other drivers? Particularly the INF (chipset) driver? Beyond that just download the Intel driver from the motherboard manufacturer website to a thumb drive, using another computer, then install them on the new one. That should get it working. If not, give the motherboard manufacturer a call
 
False alarm, turns out the router's ethernet ports are dead. I should have tested that more throughly, but it is weird that those died while the wifi still works.