1 of 1 people found this helpful
Thank you for joining the Intel communities.
Just checking – did you try uninstalling and reinstalling the latest LAN driver?
Did the unit work before and then failed or it never worked?
Is the BIOS up to date?
- I have not tried uninstalling and reinstalling the LAN driver yet. I have only installed the latest version via the manual download (not the Intel driver app) over the top. I havnt been on site yet and thats not something i feel comfortable doing remotely using logmein.
- These NUCs had no issue until they were auto-upgraded to Windows 10. When they were Windows 8.1 (some might have been windows 7, not 100% sure) they had no network issues.
- The bios has not been updated. Also because i have not been on site.
<mini rant> We have been logging into every customer and installing a program that prevents the windows 10 upgrade thanks to Microsoft. In 1 morning we had 6 down sites because of the upgrade </mini rant>
1 of 1 people found this helpful
Yea, all hail the GWX Control Panel!
I have seen this issue resolved by uninstalling the existing LAN driver and then installing the latest. In theory, the over-install should work but, well, sh*t happens. In the case where I have done the upgrade on purpose, I installed all of the latest driver packages from scratch after the upgrade completed - and did it all locally, so cannot say whether any LAN issue had developed during the upgrade.
Updating the BIOS remotely should be possible using LogMeIn. Just run the EBU (Express BIOS Update) executable for the latest BIOS. You will lose contact with the NUC while the BIOS upgrade is being installed but, after the upgrade is completed, the NUC should reboot and you should be able to log in again. If it doesn't, someone local will have to look at it.
Hope this helps,
If this is happening after auto-upgraded to Windows 10, most likely you will need latest LAN driver for Windows 10, you can download it here:
I hope N. Scott Pearson information can be helpful for you as well.
Just updating the thread. I wasn't the person that fixed it but i talked to the person who did. He believes it was uninstalling and reinstalling the LAN drivers that fixed the issue because it got to the internet after boot up after that. He didn't test if the stations were talking to the server before updating the bios because the sites were live at the moment of applying the fix. Regardless, uninstalling and reinstalling the LAN driver (Version: 20.7.1 Date: 4/29/2016) and updated the bios (Version: 0041 Date: 7/20/2015) fixed my issue. Thanks everyone. You saved busy people from having to deal with the same call every morning until we had time to fix this along side preventing the Windows 10 upgrades until we are ready.
P.S. The Windwos 10 updates have been scheduled for 11am Friday and Saturday... Microsoft knows they have restaurants running their OS right? That's the dumbest time to auto scheduled something that brings down the PC for a long period of time. Right before a weekend lunch rust? come on.
Update: Despite my best efforts to stop Microsoft from upgrading our customers to windows 10, a couple fell through the cracks but i was able to test this issue further. I was able to confirm that the LAN drivers were the issue. The NIC wasn't getting a DHCP address and when i set it to static it still didn't detect anything on the network including an internet connection. I uninstalled the driver then installed the LAN driver version: 20.7.1 (Date: 4/29/2016) and everything was working again.