If your computer takes a long time to access your network after resuming from sleep this article may solve your problem.
I have a server running Windows Home Server 2011 with 5 client computers:
· 3 Windows 7 (Home Premium & Professional desktops, gigabit LAN
· 1 Windows 8 Professional desktop test computer, gigabit LAN
· 1 Windows 7 Home Premium laptop, WAN
My laptop reconnects to a network share instantly after resuming from sleep; one desktop would reconnect in 10 or 15 seconds while the others took about 90 seconds to access a network drive after waking from sleep. Watching the progress bar in Explorer for 90 seconds is pretty sad when my desktops typically boot from off mode in 20 seconds.
Finding the problem with Google was fairly simple, the laptop’s wireless adapter was set to “always on” while the wired computers settings allowed the LAN adapter to power down.
The fix is obvious if you don’t need to wake a computer remotely, just uncheck the “Allow the computer to turn off this device to save power”.
Unfortunately if you need to wake your computer remotely you must leave this setting checked since Microsoft in its wisdom turns off WOL unless the network adapter is allowed to turn itself off creating a catch-22 situation.
After a week of researching the problem and trying obscure registry hacks with no results I thought of what should have been an obvious solution:
· Install a second network card in a computer, one set to turn off and one set to stay powered on.
It doesn’t really matter how fast the secondary network adapter is (10/100/1000), you only need it to accept a magic packet to wake the computer, although if you have to buy a network adapter you might as well buy a good cheap gigabit card for around $12 like the Rosewill RC-400 10/ 100/ 1000Mbps PCI V2.2, 32/64-bit, 33/66MHz Networking LAN Card With Heatsink & 4 LED indicators Item #: N82E16833166002, just make sure it has WOL capabilities. The TP-LINK PCI-E 100/1000 TG-3468 also works well.
If you need a good unmanaged switch for more ports the TP-LINK TL-SG1008D Unmanaged 10/100/1000Mbps Unmanaged Gigabit Desktop Switch Item #: N82E16833704043 works great, I picked mine up for $27 on sale.
Basic steps are:
1. Install a second LAN adapter in computer
2. Assign static IP addresses to both of the primary and secondary LAN adapters. I add 10 the primary IP so I can remember them easily, i.e.: computer A primary LAN adapter IP = 192.168.0.5 and computer A secondary LAN adapter IP = 192.168.0.15
3. In the primary LAN adapters properties set the TCP/IPv4 Metric to a lower number than the secondary LAN adapters TCP/IPv4 Metric. Do the same for the TCP/IPv6 Metric if you have TCP/IPv6 turned on.
Update: in the video showing how to implement this fix, I erroneously stated that filling in the IP address for the IPv4 Properties was optional. For this fix to work the IPv4 Properties must be filled in.
|
TCP/IPv6 CLICK PROPERTIES | TCP/IPv4 CLICK PROPERTIES |
CLICK ADVANCED | CLICK ADVANCED |
SET YOUR METRIC NUMBER | SET YOUR METRIC NUMBER SET YOUR METRIC NUMBER – Higher than your primary adapters Metric number |
TCP/IPv4 CLICK PROPERTIES | TCP/IPv4 CLICK PROPERTIES |
SET A STATIC IP IN YOUR ROUTER IF YOU HAVE ONE. YOU CAN ALSO SET IT HERE ALSO. CLICK ADVANCED. | SET A STATIC IP IN YOUR ROUTER IF YOU HAVE ONE. YOU CAN ALSO SET IT HERE ALSO. CLICK ADVANCED. |
SET YOUR METRIC NUMBER | SET YOUR METRIC NUMBER – Higher than your primary adapters Metric number |
Windows will probably warn you about using two network adapters on the same Gateway, ignore it, it will work anyway although if you are setting static IP’s in the adapter setting you may have to re-enter one or more settings below once or twice until Windows quits helping you. Windows has a tendency to remove the “Default gateway” settings from one of the adapters when first setting it up.
4. Now set your PRIMARY ADAPTER’S “Power Management”
CLICK CONFIGURE
CLICK POWER MANAGEMENT
5. SET YOUR SECONDARY ADAPTER’S “Power Management” TO
Now your computer will default to using your Primary LAN Adapter for network access (which always stays powered on) and will use the Secondary LAN Adapter if the Primary is unavailable.
To remotely wake a computer from sleep you send a WOL magic packet to the Secondary LAN Adapter (192.168.0.15 in this example) and connect your Remote Desktop to your Primary LAN Adapter (192.168.0.5 in this example).
read more