Sign in with
Sign up | Sign in
Your question
Solved

ASUS RIVE: Windows 7 slow to find Intel LAN controller...

Last response: in Motherboards
Share
February 26, 2014 1:19:48 AM

I have a discrete NIC: Bigfoot Networks Killer 2100 PCIe card, and I have been connecting to the internet through that. Now I am considering removing the NIC to make room for a different PCIe card...

So, I wanted to test the functionality of the onboard Intel LAN controller. It works fine, BUT when I start the computer with the ethernet cable attached to the motherboard (instead of the PCIe card NIC), it takes Windows a long time to discover the internet connection.

When I open the "Network and Sharing Center" in Windows, I see it searching the "Undefined Network" for internet connectivity. Then finally after searching that for about a minute and not finding any connection, Windows adds "Network 2" to the list of active networks, and finds the internet connection there. So it takes well over a minute for Windows to find the internet at startup under this configuration. Whereas when I am connected through the Killer 2100 NIC, it finds the internet within a few seconds of startup.

And I have looked at the "Network and Sharing Center" when I startup connected through the NIC. The difference is that "Network 2" is immediately present under the list of active networks right from the start. And apparently Windows does not search the "Undefined Network" at all for internet connectivity under this scenario. I believe the only reason the "Undefined Network" is present is because it hosts several virtual network adapters for VMWare Workstation.

So my question is: how to make Windows "see" the connection through the Intel LAN controller immediately on startup? I don't want to remove the NIC, add a different PCIe card, and have to wait a few minutes for internet access each time a start Windows.

Thanks for any thoughts!
a b X LAN
a c 242 å Intel
a b $ Windows 7
a c 1647 V Motherboard
a c 866 Ĉ ASUS
February 28, 2014 8:13:13 PM

Disable your discrete connection
m
0
l

Best solution

a b å Intel
a b $ Windows 7
a c 170 V Motherboard
a b Ĉ ASUS
March 1, 2014 1:06:03 AM

Oxonsi said:
I have a discrete NIC: Bigfoot Networks Killer 2100 PCIe card, and I have been connecting to the internet through that. Now I am considering removing the NIC to make room for a different PCIe card...

So, I wanted to test the functionality of the onboard Intel LAN controller. It works fine, BUT when I start the computer with the ethernet cable attached to the motherboard (instead of the PCIe card NIC), it takes Windows a long time to discover the internet connection.

When I open the "Network and Sharing Center" in Windows, I see it searching the "Undefined Network" for internet connectivity. Then finally after searching that for about a minute and not finding any connection, Windows adds "Network 2" to the list of active networks, and finds the internet connection there. So it takes well over a minute for Windows to find the internet at startup under this configuration. Whereas when I am connected through the Killer 2100 NIC, it finds the internet within a few seconds of startup.

And I have looked at the "Network and Sharing Center" when I startup connected through the NIC. The difference is that "Network 2" is immediately present under the list of active networks right from the start. And apparently Windows does not search the "Undefined Network" at all for internet connectivity under this scenario. I believe the only reason the "Undefined Network" is present is because it hosts several virtual network adapters for VMWare Workstation.

So my question is: how to make Windows "see" the connection through the Intel LAN controller immediately on startup? I don't want to remove the NIC, add a different PCIe card, and have to wait a few minutes for internet access each time a start Windows.

Thanks for any thoughts!


RIVE owner here.

There are a couple of oddities with the the Intel Ethernet controller on this board.

I would like you to perform the following:

1. Make sure that you have both of the EZ plug auxiliary power connectors plugged in (the PCIe 6 pin and 4 pin FDD connectors in the middle of the board) as well as both of the EPS power connectors (the 8 pin and 4 pin connectors at the top of the board).

The X79 chipset was rushed to market and I believe that some of the earlier RIVE board revisions routed power in a rather funny fashion. The Intel NIC on my board initially did not work at all until I plugged in the second EZ Plug

2. Update the firmware to revision 4802 if you haven't done so already. The firmware has changed extensively since the board was released. Many major new features have been added.

3. Try removing the Killer 2100 NIC and booting with just the Intel NIC. There could be some odd bus conflict.

4. Try removing cached networks from the network list. This can be done under the Network and Sharing center.

I can tell you with absolute certainty that VMWare Workstation is not causing the conflict, as I use it myself.

EDIT: The VMWare network adapters will indeed show up as Undefined Network if there's no DHCP host on that network. The adapters will be named "VMWare Network Adapter VMNetX" where X is a number.
Share
Related resources
!