NUC7I5BNH ethernet not working after Windows 10 resumes, claims media disconnected

[RSchm20]

Everything was working fine for the past year+ since I purchased the NUC. Now, when it wakes up, the internet does not work. I followed all of the troubleshooting steps in Windows article 10741 as well as ran the Windows network troubleshooter, but for whatever reason, it does not fix the problem.

Command line ipconfig /renew tells me media disconnected. I checked the lights on the NUC as well as the switch it is connected to, and everything is fine. Solid orange, green light blinking on the NUC. Dual green blinking on switch.

The only thing working to reset the network is to unplug the network cable and plug it back in. Rebooting the NUC does NOT fix it. This is one confusing problem to have.

[n_scott_pearson]

Well, playing Mr. Obvious, the resume is not restoring the state of the device. The question is why is it doing this all of a sudden. Let's do a full driver reset and see that happens:

1. Download latest Ethernet package from Intel site. It is here: ​https://downloadcenter.intel.com/download/28613/Intel-Gigabit-Ethernet-Network-Connection-Driver-for.... Do not attempt to install just yet.
2. Disconnect from Internet (unplug Ethernet cable from NUC).
3. From Apps and Feature, uninstall existing Ethernet p​ackage.
4. Reboot.
5. Install package downloaded earlier.​
6. Reboot.
7. Reconnect ​internet.
8. Test.

D​oes the problem reoccur?

...S

[RSchm20]

I tried several attempts the last few days to do just that. I used the Intel updater to update and I also removed the driver and tried to use the default Windows 10 driver driver. I will give it one more shot and see how it goes.

[n_scott_pearson]

No, this process I have defined is unique and your attempts do not duplicate it. The Intel updater may be part of the problem, so we need to avoid it. We also need to use a process that will curtail Windows Update during the process. Please try this process (follow it exactly) and let us see whether it makes a difference.

...S

[RSchm20]

No luck after a day of meddling with the driver (https://downloadcenter.intel.com/download/28613/Intel-Gigabit-Ethernet-Network-Connection-Driver-for...) . It seems I will have to reset the network cable to restore normal operation on the two NUCs. Not a problem with the desktop. Ping results of a NUC and desktop after waking up are below:

NUC after waking

Pinging turner-tls.map.fastly.net [151.101.149.67] with 32 bytes of data:

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=24ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=29ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Request timed out.

Reply from 151.101.149.67: bytes=32 time=2676ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=24ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Request timed out.

Request timed out.

Reply from 151.101.149.67: bytes=32 time=1962ms TTL=55

Reply from 151.101.149.67: bytes=32 time=31ms TTL=55

Reply from 151.101.149.67: bytes=32 time=34ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Request timed out.

Reply from 151.101.149.67: bytes=32 time=3049ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=30ms TTL=55

Reply from 151.101.149.67: bytes=32 time=21ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Request timed out.

Request timed out.

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=21ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=29ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Ping statistics for 151.101.149.67:

  Packets: Sent = 40, Received = 34, Lost = 6 (15% loss),

Approximate round trip times in milli-seconds:

  Minimum = 21ms, Maximum = 3049ms, Average = 247ms

NUC after unplugging and reinserting ethernet cable

After cable removed/reinserted

Pinging turner-tls.map.fastly.net [151.101.149.67] with 32 bytes of data:

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=30ms TTL=55

Reply from 151.101.149.67: bytes=32 time=21ms TTL=55

Reply from 151.101.149.67: bytes=32 time=21ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=29ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=35ms TTL=55

Reply from 151.101.149.67: bytes=32 time=27ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=21ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=34ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=27ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=27ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=24ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=21ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=23ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=21ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Reply from 151.101.149.67: bytes=32 time=22ms TTL=55

Ping statistics for 151.101.149.67:

  Packets: Sent = 60, Received = 60, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

  Minimum = 21ms, Maximum = 35ms, Average = 23ms 

Desktop after waking

Pinging cnn.com [151.101.65.67] with 32 bytes of data:

Reply from 151.101.65.67: bytes=32 time=23ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=30ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=35ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=23ms TTL=55

Reply from 151.101.65.67: bytes=32 time=21ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=23ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=25ms TTL=55

Reply from 151.101.65.67: bytes=32 time=23ms TTL=55

Reply from 151.101.65.67: bytes=32 time=23ms TTL=55

Reply from 151.101.65.67: bytes=32 time=21ms TTL=55

Reply from 151.101.65.67: bytes=32 time=23ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=21ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Reply from 151.101.65.67: bytes=32 time=22ms TTL=55

Ping statistics for 151.101.65.67:

  Packets: Sent = 28, Received = 28, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

  Minimum = 21ms, Maximum = 35ms, Average = 22ms

[n_scott_pearson]

Hhmmm, did you install a BIOS update just prior to this issue appearing? Are you running the latest available BIOS? It's probably a driver issue, but there's still the possibility of it being a BIOS issue.

...S

[Wanner_G_Intel]

Hello RSchm20, Were you able to follow the steps recommended? If you have any further questions, please let us know. Wanner G. Intel Customer Support Technician Under Contract to Intel Corporation