Fellow NUC Fans,
I've found a workaround.
While enduring this symptom, my NUC's clock was set about eight hours in the future (fast). I thought that was irrelevant.
Yet after adjusting the clock to my local time (US/Pacific) and re-entering Visual BIOS, the NIC came online, and the iSCSI configuration screens became functional.
I believe this is a firmware bug; it seems like the NIC should come online while entering Visual BIOS regardless of the clock's setting. Would y'all agree?
Thanks so very much,
Sounds like an odd and funny bug...
What if you manually set the clock +8 hours into the future and reboot?
Can you spot at which difference the NIC stops working, will +4 hours work but not +5?
Only thing I can come up with that is time dependent is if some kind of ssl certificate (or similar for encryption) is being used for your iscsi initialisation. In those cases mismatching clock can make the ssl (or such) handshake to fail. Timestamps might also be used in IP-packets but that would a really odd bug if that would be related to the issues you are seeing.