Unsolved
This post is more than 5 years old
7 Posts
0
145408
February 3rd, 2008 14:00
Wake on LAN (WOL)
Does the XPS 720 support wake on LAN? Has anyone used this functionality?
If I put my 720 in standby, I can not get it to wake on lan activity. I have tried a couple of utilities to send magic packets, and could not get the PC to resume from standby. I can ping my 720's ip address, and the first packet times out, but the subsequent packets return replies from the ping, so it appears that the ping has brought the computer out of standby. Remote desktop connects, and allows me to enter my user name and password, but the window just closes when I click OK. I am using the same login at the console and with remote desktop, but I have no problems with the remote desktop connection if my XPS is in a fully powered state.
The worst part...
After attempting to "wake on LAN", I cannot get the PC to resume from standby, even at the console. My only option is to power down the PC by holding the power button.
System:
XPS720 black A03 BIOS
Q6600 @2.4GHz
Broadcom NetXtreme 57xx Gigabit Controller
Linksys WRT54G router
I have tried both S3 and S1 standby modes.
The NIC wakeup capabilities is set to both. Power Management is set to "allow the computer to turn off this device to save power" and "allow this device to bring the computer out of standby."
I have a home network set up with a cable internet connection and a linksys WRT54G router. My XPS is connected to the router with cat5, and I have a couple of laptops on wireless connections. I do not use DHCP for my PCs (I do have DHCP enabled on the router for my TiVo).
If I put my 720 in standby, I can not get it to wake on lan activity. I have tried a couple of utilities to send magic packets, and could not get the PC to resume from standby. I can ping my 720's ip address, and the first packet times out, but the subsequent packets return replies from the ping, so it appears that the ping has brought the computer out of standby. Remote desktop connects, and allows me to enter my user name and password, but the window just closes when I click OK. I am using the same login at the console and with remote desktop, but I have no problems with the remote desktop connection if my XPS is in a fully powered state.
The worst part...
After attempting to "wake on LAN", I cannot get the PC to resume from standby, even at the console. My only option is to power down the PC by holding the power button.
System:
XPS720 black A03 BIOS
Q6600 @2.4GHz
Broadcom NetXtreme 57xx Gigabit Controller
Linksys WRT54G router
I have tried both S3 and S1 standby modes.
The NIC wakeup capabilities is set to both. Power Management is set to "allow the computer to turn off this device to save power" and "allow this device to bring the computer out of standby."
I have a home network set up with a cable internet connection and a linksys WRT54G router. My XPS is connected to the router with cat5, and I have a couple of laptops on wireless connections. I do not use DHCP for my PCs (I do have DHCP enabled on the router for my TiVo).
Message Edited by wickpika on 02-03-2008 10:43 AM
No Events found!
Davet50
4 Operator
•
14.4K Posts
0
February 3rd, 2008 16:00
have you tried disabling the allow the computer to turn off this device to save power? seems like you are telling the nic too things go to sleep and then try to wake up..i would think that the nic should be ready at any time to wake on lan..
here is some info i copied out Wikipedia
Wake on LAN (WoL) support is implemented in the motherboard of the computer. Most modern motherboards with an embedded Ethernet controller support WoL without the need for an external cable. Older motherboards must have a WAKEUP-LINK header onboard and connected to the network card via a special 3-pin cable; however, systems supporting the PCI 2.2 standard coupled with a PCI 2.2 compliant network adapter typically do not require a WoL cable as the required standby power is relayed through the PCI bus.
Wake on LAN must be enabled in the Power Management section of the motherboard's BIOS. It may also be necessary to configure the computer to reserve power for the network card when the system is shut down.
In addition, in order to get WoL to work it is sometimes required to enable this feature on the card. This can be done in Windows from the properties of the network card in the device manager, on the "Power Management" tab. Check "Allow this device to bring the computer out of standby" and then "Only allow management stations to bring the computer out of standby" to make sure it does not wake up on every single network activity that occurs.
just curious as I have the same router you mentioned you dont use DHCP so how are you connting the systems to the router..i dont see a reserve function in the router...
NemesisDB
2 Intern
•
7.9K Posts
0
February 3rd, 2008 17:00
Dave, hope you don't mind if I jump in.
To the OP, make sure to get the latest drivers from www.broadcom.com -- they will be newer than dells. For my setup (on XP with an intel card), I have the following options:
under the power management tab: Allow the computer to turn off this device to save power (Checked), Allow this device to bring the computer out of standby (checked), Only allow management stations to bring the computer out of standby (Checked).
under the advancaed driver tab: Wake on Magic & Directed. Wake on OS might also work, I'm not sure.
Broadcom's options may be different, but that should get you started. My computer (dimension 9150) does not have explicit WoL bios support -- so I can only resume from standby or hibernate but not when the computer is fully turned off. Regardless, you should check the bios options for anything related to WoL functionality on your machine.
Last suggestion is to try from a machine nearby on the lan so you can watch what is happening in realtime. For instance, when I send magicpackets from my router (which has a utility built in) everything works fine. When I use a magicpacket utility I downloaded on my vista laptop, absolutely nothing happens. I feel like some of these utilities just don't work! Of course, you also need to ensure that the proper broadcast address and MAC address has been entered before you send the wakeup call.
wickpika
7 Posts
0
February 3rd, 2008 17:00
I read the wikipedia article. That is where I found the links to the magic packet utilities. I also tried telling the computer to never turn off the nic, but no change, so I switched it back. When I put my 720 into standby or completely power it down, the light on the nic remains lit, so it would appear that it is capable of WOL. However, I see no wake on LAN option in the bios. Maybe the motherboard does not support WOL, or perhaps the cable is not connected...? I find it odd that the ping does appear to wake up the PC. Remote desktop connections time out before pinging the PC. The 1st packet times out, and packets 2 - 4 return replies. Then, I can connect with remote desktop, it just won't let me log in...
I just specify my ip address, subnet mask, and default gateway in my network connection's TCP/IP properties. I use the router's MAC address filter to only allow specific devices to connect to the network via wireless.
I have tried monitoring what happens when I send a magic packet and a ping from a laptop connected via wireless. I am using the correct MAC address, but nothing appears to happen when using the magic packet utility. I ran tcpview from sysinternals, and I saw no activity when I attempted to send the magic packets.
I think I am going to create a second user for connecting with remote desktop, and see where that gets me. I will also try updating the broadcom drivers.
Thanks!
Davet50
4 Operator
•
14.4K Posts
0
February 3rd, 2008 20:00
NemesisDB
feel free to jump in any time
I do not see anything in the Bios like the op says
as to the power options on our ethernet contoller here are the options
WakeUpMode
= "None"
= "Magic Packet"
= "Wake Up Frame"
= "Both"
default is both what ever that is..i am assuming it magic packet and frame...
USP45
8 Posts
0
February 26th, 2009 10:00
I also have an XPS 720 with your same issue. I believe the network card that shipped with these is the culprit. See below:
Why does the Wake On LAN feature not work properly on my system containing a 5700, 5701, or 5702 adapter when running in Vista or Windows 2008?
goodvibrations
23 Posts
0
February 23rd, 2010 22:00
Hi, First post....i know this thread is old but you probably googled to get here like me. My system is a dell xps 720 (A06 Bios) running XP and i had a problem very similar to what wickpica wrote. More specifically i was trying unsuccessfuly to get Logmein on a client computer to wake up my remote host computer the dell xps 720. The client computer just could not wake up the host computer. I believe i have solved the problem and wish to share it.
On the power management tab of the 57xx gigabit controller (nic card?) settings, i had to unclick the box beside "only allow management stations to bring the computer out of standby". (the other 2 boxes above that stayed clicked on).
This solved the problem. I am now able to remotely access the dell xps 720 via "wake on lan" WOL. However, a new problem arose and luckily i figured that out also.
The new problem was that under this new setting, the computer kept coming out of standby on it own without me touching the mouse or keyboard. I made a guess that logmein was causing the computer to come out of standy (based on the packets i could see thru viewing the network activity of comodo firewall). Also I read a very good post at http://en.community.dell.com/forums/p/19301828/19601275.aspx and figured out that under the Advanced tab of the 57xx gigabit controller settings >wake on lan capabilities, i should choose >magic packet.....not >both .....where both would include "wake up frame" and "magic packet". By choosing .>magic packet on the drop down menu, the annoying wakeup from standby problem caused by logmein was solved. (on the other dell forum above, it was suggested to disable wake on directed packets, this must be a similar function as "wake on frame" ...it seems that disabling them prevents random wakeups form standby )
The last comment is about the following quote from wickpika above:
"The worst part...
After attempting to "wake on LAN", I cannot get the PC to resume from standby, even at the console. My only option is to power down the PC by holding the power button"
i experienced this same real hassle although in my case it was a slightly different change in the behaviour of standby mode (related to the time it took to come out of standby and how deeply it went into standby). It was almost a bit of a nightmare because it was permanently doing this. I realize that the only change i had made was switching from S3 default setting to the S1 setting (in the bios) under power management (i think). I know (or i'm pretty sure) that this bios change caused the annoying change in standby - probably a registry change corruption (?). It shouldn't have caused it but that is the nature of random events. Going back to an earlier restore point (3 hours earlier) solved this problem for me.
Thankyou so much to everyone for the comments that have helped me trouble shoot things.
Peace