Randomly switching Network Connection Adapters

[PGrub]

I have an internet connection problem. 82579V Gigabit Network Connection Adapter provides internet connection, but sometimes, seemingly randomly, it switches to 82579LM Gigabit Network Connection Adapter, which blocks internet connection. I then have to go to Device Manager and scan for hardware changes, which then reverts back to 82579V Gigabit Network Connection Adapter, restoring internet connection. Why would this be happening and how can I stop it from happening.

[st4]

Hi grubep,

Thank you for the post. Make sure to upgrade to the latest driver for these onboard NICs. What is the system you used? I would recommend you to contact the system vendor where these two onboard NICs are embedded. They can check if there is hardware issue on the NICs.

rgds,

wb

[PGrub]

thanks wb, I have an Acer Aspire X3990 using an Intel Core i3-2120 CPU @ 3.30GHz, 64-bit OS, Windows 10 Home. I have confirmed that all drivers are up to date.

I'm not sure 82579V and 82579LM are both onboard NICs because when it reverts to 82579LM the info in Device Manager says something along the lines of 'is not currently connected' or 'not plugged in'. I'll check details more closely next time it happens.

I have noticed that the switch from 82579V to 82579LM happens after it comes back from sleep mode, and also sometimes when I turn on the computer.

I will get in touch with Acer to see if they have any suggestions and let you know if any solution is found.

cheers, Pete

[AP16]

https://downloadcenter.intel.com/download/22026/NVM-Update-Utility-for-Intel-82579V-Gigabit-Ethernet-PHY-Network-Connection https://downloadcenter.intel.com/download/22026/NVM-Update-Utility-for-Intel-82579V-Gigabit-Ethernet-PHY-Network-Connection

[PGrub]

thanks JFFulcrum, the description on that page sounds very much like what is happening on my computer, so I have downloaded and extracted the files, opened a command prompt as Administrator and typed in 82579VSKUW64e -nosilent as per instructions in the ReadMe.txt file but this results in the following...

C:\WINDOWS\system32>82579VSKUW64e -nosilent

82579VSKUW64e -nosilent is not recognised as an internal or expernal command, operable program or batch file

I'm not much of a DOS person so I could be doing something wrong, or alternatively is it actually possible to install in the normal way without having to do it through a command prompt? could you give me some pointers?

regards, Pete

Update: Reading another post I learnt that I have to reference the path in the command prompt, so I did the following...

cd\Users\Pete\Downloads (press enter)

82579VSKUW64e.exe (press enter)

This action didn't provide any feedback from the command prompt, it just went back to cd\Users\Pete\Downloads>

[AP16]

Because second time you omit the '-nosilent' key, all was done in behind. Now reboot and look, if problem is gone.