![]() Another positive effect was that both PCs now only need 8 - 10 seconds to start Windows (after the hardware Information has disappeared). Standard NICs can be used to connect the host to a remote iSCSI target on the IP network. Software-based iSCSI implementation can be configured. Intel says the update fixes the problem - and it did! Once installed, the network adapter was recognized, the driver installed, and the network connection was there in almost no time - even withįast boot turned on. The adapters (as referenced in data sheets and product brief) support Software iSCSI and not Hardware iSCSI offload. After some research, I finally found the "Intel NVM Update Utility" here: Wake On LAN) shortly after pinging an Intel 82579LM GigaBit Ethernet Controller. I found out that the network adapter was recognized as "Intel 82579LM" (and not 82579V) which caused the problem. Intel(R) Smart Connect Technology Registry Patch (Wireless Wake On LAN). Windows fast boot turned off, the network connection was established, but starting took a loooong time. On cold boot, the network adapter Intel 82579V (not LM) was not recognized, and I did not get a working network connection with internet access. ![]() I experienced a comparable issue with 2 PCs in my company network after upgrading from Win10-1703 to 1709.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |