Clams
Well-Known Member
Thread Starter
- Joined
- Jan 29, 2007
- Messages
- 7,286
- Likes
- 358
This is annoying when trying to stream from the "Cloud PC" to either of the HTPC's. (or any combo thereof)
Bottom line is that they won't Wake On LAN. When these PC's either idle to sleep (default S3) or are "put" to sleep by the user, they refuse to awaken when another network PC tries to access them. I have to go to the other room and tap the space bar to wake these things up - LOL.
When machines are asleep - the RJ45 jack is still lit up - as it should be. (so I know it's able to receive)
I tried going into BIOS and turning Power On By PCI-E to ON - no difference.
2 Hero's, 1 Formula - These boards all use the Intel i218-V Ethernet Controller.
Device manager PM settings: (which I think are the defaults)
Allow computer to turn off this device to save power - ON
Allow this device to wake the computer - ON
Only allow a magic packet to wake the computer - ON
I can't be sure - but I want to say this only started when 1607 came down. (not positive though).
-W
Bottom line is that they won't Wake On LAN. When these PC's either idle to sleep (default S3) or are "put" to sleep by the user, they refuse to awaken when another network PC tries to access them. I have to go to the other room and tap the space bar to wake these things up - LOL.
When machines are asleep - the RJ45 jack is still lit up - as it should be. (so I know it's able to receive)
I tried going into BIOS and turning Power On By PCI-E to ON - no difference.
2 Hero's, 1 Formula - These boards all use the Intel i218-V Ethernet Controller.
Device manager PM settings: (which I think are the defaults)
Allow computer to turn off this device to save power - ON
Allow this device to wake the computer - ON
Only allow a magic packet to wake the computer - ON
I can't be sure - but I want to say this only started when 1607 came down. (not positive though).
-W
Last edited: