Unsolved
This post is more than 5 years old
1 Message
0
159670
Can't get Wake on Wireless LAN (WoWLAN) to work on Latitude D830/D630 with Intel 3945ABG adapter
32bfhd1
We have several Dell D630 and D830 Latitudes in our office, all of which have the Intel 3945ABG wireless adapter with the newest drivers / Intel ProSet software (v12.1.1.0) loaded. My issue is -- despite claims by Intel and Dell -- I cannot get the 'Wake on WLAN' feature to work...the laptops simply never wake up from Standby. A network monitor/sniffer shows the 'magic packets' being broadcast (one laptop at a time), but the laptops stay in Standby. The wireless access point is a D-Link DIR-655. I called Dell today and got nowhere -- I couldn't get someone versed in this niche issue. I also called Intel, and they conveniently said call Dell. I'm hoping someone here can help.
We have a Sonicwall SSL VPN 200 device which allow users who don't take their laptops home to remote desktop in from home/wherever. Likewise, we have Acronis TrueImage Workstation Echo installed on all machines for nightly backups. Currently, all laptops are left on all the time in their docks. A waste of energy. Ideally, I'd like for them to go into Standby until either the Sonicwall device or Acronis wakes them up for use (via standard magic packets)...or the user sits at their desk.
There are three options in the Intel 3945ABG's Power Management settings (under ProSet->Advanced->Adapter Settings), I have tried all possibilities of the first two options:
(i) Allow the computer to turn off this device to save power
(ii) Allow this device to bring the computer out of standby
...but none caused the laptop to wake from Standby. I read that checking the 1st option negates the 2nd option as it might turn off the Intel device (in Standby and otherwise), which means it wouldn't receive the magic packets. But, when I uncheck the 1st option...it greys out the other options. Ugh. I've found that if I check the 1st option...then check the 2nd and 3rd (see below)...and then uncheck the 1st again...then the 2nd and 3rd options are still checked but they're greyed out...does this mean they're still actively checked...who knows...
I have tried toggling the third option ('only allow management stations to bring the computer out of standby') with no differing effect. I've read that this 'management station' option only allows magic packets to affect the WoWLAN...which is what I want...but that magic packets will still work with the third option unchecked.
As for the laptops' BIOS (Dell's most recent revs), the Wake on LAN/WLAN option under the Power Management section is selected as 'LAN or WLAN'...but this shouldn't matter as this only affect the laptops when they're off (LAN) or in hibernation (WLAN).
I sure would appreciate any help on this. Below is a link on Intel's configuration instructions, all of which I've done. The only caveat is that under Step 6 I checked both Persistent and Pre-Login/Common. I need the Pre-Login feature so that the wireless connection is established even before a user logs in.
http://www.intel.com/support/wireless/wlan/sb/CS-029827.htm
Craig
partymarty84
3 Posts
1
March 31st, 2010 08:00
Craig, follow the list below and it should work for you.
1. WoWLAN only works when the system has been sent to standby or hibernation
2. The laptop must be connected to a power adapter, it doesn't work off a battery (as far as i know) * note that connecting a power adapter after the laptop has hibernated won't help, it has to be connected before standby/hibernation
3. Enable the wake option via the power management section of the wireless adapter
4. In the BIOS, enable Wake on WLAN.
5. Note down the MAC address of the wireless adapter
6. I don't use the Intel software as the Windows wireless already has the 'persistent connection' but this also needs to be setup if you stay with Intel's software.
7. Use a third party tool such as this one - http://www.depicus.com/wake-on-lan/wake-on-lan-gui.aspx
8. Run the tool from the local subnet. Type in the MAC address, leave the internet address blank and set the mask to 255.255.255.0 and the port to 7. You can't run the tool from outside the subnet (including via VPN) without additonal configuration. Create a web app that sits on an internal server to get around this