Wake On Lan Problem

Hello,
I have enabled PME ON WAKE from the Bios currently I am using motherboard Gigabyte GA-P35-DS3.
I have enabled Wake on Magic Packet, Disabled Wake on Pattern Match, Shutdown Wake On Lan is enabled.
I have also created a Port Forward on my Virgin SuperHub.
But I am still unable to Wake on Lan? Is there anything else I can do.
David

Hi DMatt7176,
I would provide a reference for you:
Wake-on-Lan (WOL) for Windows 7 Made Easy!
http://windows7-issues.blogspot.com/2011/03/wake-on-lan-wol-for-windows-7-made-easy.html
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Regards,
Alex Zhao
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

975x Platinum PowerUp - Wake on LAN problem...

Hi,
for TV digital cable recording with my DboxII receiver (Neutrino Linux) I need Wake-on-Lan. It work flawlessly with my old ASUS A7N266-C: PC as streaming server, woken up by the pre-programmed DBox by a "Magic Packet" containing the MAC-adress of the LAN-card. (So I don't have to program any timers on the PC, just have to be sure that it is in standby or hibernation mode.)
The new setup is the same as the old, I've only changed the PC's MAC-Adress in the DBox-setup. The DBox is connected via router.
What I've done: I activated PME in the Intel LAN properties, and activated "resume by directed packets and Magic Packet". I allowed the device to wake up WindowsXP and set the BIOS to resume by PCI and PCI-E events (seems as if PCI-E is the necessary setting for the onboard LAN).
What happens, is, that it doesn't work with Magic Packets. It almost works with this "directed packets" setting - but the problem is, that the PC only stays in hibernation mode for around 15 seconds - even if the Dbox is switched off. Maybe the router does something to wake the LAN card? DHCP is already off...
Has anyone further knowledge about WOL with this board? The next thing I'll try is, if it works better with my previous Realtek PCI card. But it would be a pity to waste a PCI slot for that....
Power-on-LAN is impossible with this board, I guess?
Martin
P.S. I'm still stuck to BIOS 7.1, because I need the Intel Raid AND the JMicron IDE - is there any beta BIOS, that I could try?

Quote from: FrobinRobin on 27-November-06, 23:25:47
I've had WOL work on various BIOSes. I know 100% it works with 7.1A.
You need to select the first boot device as LAN
I tested my WOL application firstly from the shell prompt from another PC and when it worked I set up a web page to run the WOL app - it works great but if i remember correctly I had to change some firewall settings(?) to get it working from the shell. If you cannot get it to work maybe there is a compatibilty issue with the mobo & dbox WOL packet ?
(i have dbox - they're gr8 )
I use WOL 1.1 by Greg Whittmeyer (PM me if you want a copy)
Every magic packet is the same - the mac addy 3 times, so it shouldn't matter how it's being generated. If you want to test your waking app, plug another computer into the same network cable as the 975 system and send it's magic packet.
Another thing to be sure of is to make sure your power is off, magic packets will sometimes not wake a sleeping computer - from S1, S3, or S9

Wake On Lan problem with MS-6566

Hello,
Does MS-6566 supports Wake on Lan function?? In the manual, in Mainboard specifications appears "LAN/Moden wake up function". However, it doesn't work. My systems is as follow:
- MS-6566 with BIOS revision 1.4
- P4 Intel Celeron 1,7 Ghz.
- 512 MB DDR266
- HDD 80GB
In BIOS section (AMI BIOS) "Power Managament Setup" only appears section for Modem wake-up.
I don't need WOL cable, because my NIC is PCI 2.2 compliant, is 3com 3C905-TX-M. It works fine in other mainboards like ASrock, ie.
Thank you in advance.
Best Regards,
Jose Manuel

I had the similar problem with Intel 10/100 + Managed NIC - PCI 2.2
This card has its own EPROM with configuration. I had to install the "Driver + utils" pack into W2K and I went into configuration utilities and ENABLE the WOL and MAGIC PACKET support.
HTH
Martin

Wake on lan using Artigo A1000

Hello everyone,
I have an VIA Artigo computer. I loaded Arch Linux on it and I wanted to use wake on lan. I followed the instructions on the wiki page for wake on lan, but it would not work correctly when I tried to wake the computer using wol. It would only work if I had hibernated the computer using the pm-hibernate command. If I tried to wake it after turning the computer off by either using the halt command or shutdown command it would not respond to the magic packets. I tried doing some searches for this problem but I couldn't find anyone using Arch Linux with a similar problem. I broadened the search and found that others had experienced this problem in other distributions using similar hardware. According to them, the problem was that when the computer was being shutdown it was taking network offline, which would prevent the system from recognizing the magic packet being sent. Their advice was to prevent the OS from doing that at shutdown. Unfortunately, their specific solutions didn't seem to apply to Arch Linux, I'm not sure if it has to do with their distros using sysv scripts vs Arch Linux's BSD style scripts or if it was my cluelessness. I was able to get it to work by editing the /etc/rc.d/network file and commenting out the line that reads /sbin/ifconfig ${1} down >/dev/null 2>&1 in the ifdown() function. Doing that has resolved my wake on lan problem, now the system will respond to magic packets sent using the wol command after I have shut it down using the shutdown command. My gut feeling tells me that it might not be the best way to fix this problem, I'm concerned that I might update a package some time in the future and this configuration file may get wiped out. Is that a valid concern? Is there perhaps a better way of fixing this problem?
Please let me know.
Thanks!

You may not need to leverage ConfigMgr for this.
http://blogs.technet.com/b/matthts/archive/2012/06/02/wakeup-machines-a-powershell-script-for-wake-on-lan.aspx
Daniel Ratliff | http://www.PotentEngineer.com

Wake on Lan works on my MacBook Pro, not on my iMac...

Hello everyone, with all these threads about the problem, I wanted to start a new one to make it clear, with all information you may need in order to help me out.
I've got a MacBook Pro '15 and an iMac 21.5', both are running (clean install) OS X Mountain Lion 10.8.2, both are up to date with the latest updates, both have the same apps, both have the same settings in "system preferences", and of course the same settings in "sharing" options.
My iMac is connected to my 5GHz network from my Time Capsule while my MacBook Pro use the 2.4GHz network.
Before going to bed, I leave both my Macs turned on, after 10min they go to sleep automatically. In the morning I can wake up my MacBook Pro from my iPhone or iPad with a screen sharing app.
The iMac doesn't respond at all. It stays in sleep mode. I can leave my MacBook Pro asleep for a week, it always responds. The iMac responds after a few hours but after 6 or 8 hours it seems to be completely asleep and doesn't respond to anything. If you think it's about the iPhone/iPad's app, when I try to wake the iMac from my MacBook Pro with "Back to my Mac" I have the same results.
I tried to connect my iMac to the 2.4GHz network: same problem.
OF COURSE "WAKE ON LAN" is activated in my system preferences.
I made a reset of the PRAM, the cache and the SMC on my iMac: same problem.
I type sudo periodic daily weekly monthly in the terminal and sudo dscacheutil -flushcache: same problem.
I tried everything I may have found in the forums or on this Support from people having the same issue: same problem.
I even tried to set the iMac with the same sleep mode as my MacBook Pro: same problem.
PLEASE HELP ME!

loïcfernandezcastrillon wrote:
I'm connected with the WiFi of my Time Capsule (bridge mode). I have this configuration since Snow Leopard, and no troubles...
I understand that, but if your router is not an Apple AirPort Base Station then it introduces an element of uncertainty. Apple has implemented many changes related to wireless networking recently.
You are complicating matters by changing networkoversleep:
networkoversleep - this setting affects how OS X networking presents shared network services during system sleep. This setting is not used by all platforms; changing its value is unsupported.
Solving problems like this requires that you simplify your network environment and eliminate its unknowns. Using third party routers and making unsupported changes runs counter to simplification.
The iMac stays connected to the Time Capsule about 6 hours during sleep. Then it dissapears...
The iMac wakes periodically (every few hours) to inform your router of its network presence for Wake on LAN demands. Try changing your router's DHCP lease period to something longer than a few hours. For a home environment, a few days is more appropriate. This may not solve the problem, but it is better than making unsupported changes to your system.

T500 Wake on Lan (wireless) does not work.

Hi,
I set up T500 (Windows 7 Ultimate 64bit) for wake on lan,
1) Enable Bios WOL
2) Enable WOL in power manegement tab of Intel WiFi Link 5300 AGN property in device manager.
But WOL does not work. Sending magic packet from a PC in the same WiFi segment does not wake up sleeped T500.
Are there any setting for WOL in lenovo tools ?
Does anybody use WOL(WiFI) on T500?
Thanks,

Is the T500:
Associated with an access point at the time it is put into standby/sleep mode?
Connected to AC power for the whole time it is in standby/sleep mode (in otherwords the whole time it is in a low power state) when you are attempting to use WoWLAN?
If not, that may be at least part of your problem, as it is a known limitation on WoWLAN operation.
You also need to have the laptop "set up" to the master workstation, and the WLAN configured to handle braodcast wireless frame, but I am presuming you have already done that side of things.
Cheers,
Bill
I don't work for Lenovo

SG200 how to configure Wake on LAN across subnets

How can I configure to support WOL on a SG200 (8 Ports) to support Wake On Lan (Magic Packets) from a different IP Subnet or other SG200 Switch. It seems not to support Directed-Broadcasts.

I checked out the link and tested the changes. Unfortunately, the WOL still won't work. In the link you attached, it states that you cannot turn on a computer that is off. Does that mean one that is off such as unplugged or in shutdown? Also, one of the steps to configure the firewall access rules says to block all outbound connections for all services. That doesn't make any sense to me, but I might be wrong. I also noticed that the link was for another router. I don't know if that makes a difference. I also read somewhere in the forums that someone else is having a similar problem, saying that Port Forwarding still isn't working in the latest firmware. This whole problem is strange because it used to work all the time on my old router with Port Forwarding, but on this one it won't work at all.
Sent from Cisco Technical Support iPad App

Report on wake-on-lan enable/disable

Hi,
I'm needing to find a way to report on whether or not workstations have Wake-on-Lan enabled.
Any ideas?
Kind regards,
Laura

Laura,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

3.2 Server Stuck Offline & Wake on LAN issues

Got through installation and getting started guide running 1 VM Server and a separate VM Manager I was able to shutdown the Server from the Manager GUI; however, when trying to restart the Server from the Manager I received an error: OVMAPI_4005E No worker server found to perform operation on: ovmserv1. I was able to restart the Server by pressing the power button and the Manager was able to recognize the Server as on after it booted. The Manager reports the Server as having Wake-on-LAN 'Yes'. I'm using onboard NIC on Supermicro server, BIOS has a wake on modem feature, nothing for wake on LAN or PCI device. I checked the Server with ethtool and it reported Wake-on-Lan was enabled on both eth0 and eth1. There is an optional IPMI card available for the server but my understanding is that IPMI is only needed if trying to wake from a different network, while everything here is on the same LAN and ping-able. Any help will be greatly appreciated.
Last night I added an Openfiler iSCSI SAN with 3 SCSI targets, one for the pool file , one for the repository and an extra one. Setup server pool, pool file and repository in the Manager. Everything seemed great and I was looking forward to importing some appliances the next day and I shutdown for the night. Today I was trying to setup an FTP server and was messing with LDAP on the Openfiler server, unable to get that going I tried to setup an FTP server on my laptop which is also on the LAN. Later when firing everything up, somehow the NIC on the Manager had been disabled and the Manager was booted without network connectivity. After shutting down the Manager, re-enabling it's NIC and booting up again, the network connectivity was good. The problem is the Manager reports the Server as either Offline when the Server is on, or Stopped(Error) when the Server is off. Using the Manager trying to start the Server fails with 'already on' and trying to stop Server fails with 'not running'. I shutdown and rebooted all 3 servers a couple of times in different orders and the problem persists with the Server still stuck in Offline status. Any help will be greatly appreciated.

Hi,
I uninstalled Mozy a long time ago just because it did prevent my iMac i7 to go to sleep.
I don't know if they have fixed the problem since with an update, or if they'll do it but yes for me back then Mozy = no sleep.
Wake on lan should stay unchecked if you don't need it, this is also known to be a frequent cause of sleep issues.
EDIT : sorry... I didn't read properly your message... My problem was the opposite... Sorry again for my mistake...
Message was edited by: LeDav007

Wake On Lan only works within a few minutes

Hi!
I have a problem...I left my MacPro sleeping for a few hours and now it will not respond to wake on lan...It does work to wake within a few minutes but not after a few hours.
Anyone have a solution for this? (I'n not using a router)

Found the problem!! A nice person on logmein forums helped me. Thought i should post the solution in case somebody runs into this issue. I was forwarding the local IP of my computer (192.168.2.2) to a port (say port 9). It seems a router remembers the local IP's for a few minutes after the mac goes to sleep and after that its ARP table (which links MAC address to IP address) gets deleted. This is why it works for the first few minutes and not after that.
So the local IP being forwarded should be the 'broadcast address' and not the local computer's LAN address. It seems for subnet mask 255.255.255.0 the broadcast for IP range 192.168.2.x takes place for x=255. So i changed the router settings to forward local IP 192.168.2.255 to port 9. And it started to work. Hopefully this should help anyone with the same issue.

Wake-on-LAN Breaks After Several Reboots, 3.18 Kernel

Greetings all,
I'm leaving town for a month and I dont' want keep my machine turned on so I set up Wake-on-LAN on my desktop machine running 3.18 kernel. Got the wol command working but the problem is that something breaks and won't work beyond a few reboots. If I phisycally power up and shutdown the machine and then try it again, it magically works again.
I set up port forwarding on my router then followed the wiki and tried every single method mentioned there, udev, cron, systemd and wol-systemd as a last resort. Strangely enough they all give me the same result, for whatever configuration, it doesn't last beyond a few reboots.
As it stands, this is my current configuration after installing the wol-systemd package from AUR:
[Unit]
Description=Wake-on-LAN for %i
Requires=network.target
After=network.target
[Service]
ExecStart=/usr/sbin/enable-wol %i
Type=oneshot
[Install]
WantedBy=multi-user.target
My alternative is to leave my machine running, I can ssh into it just fine. but I'm hoping someone can shed some light. Feel free to ask any questions. Thanks!
***EDIT***
No takers yet? Super quiet around the forums lately,
I'm no networking guru, but I read up on some additional material regarding this subject. Apparently my problem is related to my router's ARP cache releasing the IP address after an initial period. Since the cache expires the magic packets never reach the destination IP, which coincides with the problem I'm having.
An option is to use the broadcast address in place of the IP, however, that's beyond my router's capabilities, at least I think. My router is a Linksys EA6500. I've tried just about everything. I also tried messing around with AMT but that's even a bigger headache on linux. If anyone has a workaround it would surely be a great help. Thanks!
Last edited by w201 (2015-02-24 22:32:39)

Greetings all,
I'm leaving town for a month and I dont' want keep my machine turned on so I set up Wake-on-LAN on my desktop machine running 3.18 kernel. Got the wol command working but the problem is that something breaks and won't work beyond a few reboots. If I phisycally power up and shutdown the machine and then try it again, it magically works again.
I set up port forwarding on my router then followed the wiki and tried every single method mentioned there, udev, cron, systemd and wol-systemd as a last resort. Strangely enough they all give me the same result, for whatever configuration, it doesn't last beyond a few reboots.
As it stands, this is my current configuration after installing the wol-systemd package from AUR:
[Unit]
Description=Wake-on-LAN for %i
Requires=network.target
After=network.target
[Service]
ExecStart=/usr/sbin/enable-wol %i
Type=oneshot
[Install]
WantedBy=multi-user.target
My alternative is to leave my machine running, I can ssh into it just fine. but I'm hoping someone can shed some light. Feel free to ask any questions. Thanks!
***EDIT***
No takers yet? Super quiet around the forums lately,
I'm no networking guru, but I read up on some additional material regarding this subject. Apparently my problem is related to my router's ARP cache releasing the IP address after an initial period. Since the cache expires the magic packets never reach the destination IP, which coincides with the problem I'm having.
An option is to use the broadcast address in place of the IP, however, that's beyond my router's capabilities, at least I think. My router is a Linksys EA6500. I've tried just about everything. I also tried messing around with AMT but that's even a bigger headache on linux. If anyone has a workaround it would surely be a great help. Thanks!
Last edited by w201 (2015-02-24 22:32:39)

SCCM 2012R2 multihomed client, Wake on LAN unreliable

We are seeing a strange problem related to Wake on LAN on client computers with both wired and wireless network interfaces.
All clients are initially imported with the wired MAC address, booted via PXE and image installed. The client then boots up and contacts SCCM. End users then typically use them via wireless and one would expect SCCM to "learn" both the IP/MAC configuration
of the wired and the wireless interfaces. (These networks use separate vlans and IP subnets)
SCCM and our routers are configured for directed broadcasts.
Network sniffing has confirmed that for these clients, SCCM attempts to send the broadcast to the wifi subnets instead of the wired subnets. All directed broadcasts sent to wired subnets have been confirmed to arrive as expected and those clients wake up
as expected.
However, over time the wired network interface appears to be dropped by SCCM, causing Wake on LAN to fail because it obviously won't work using the IP/MAC information for the wireless adapter. When checking the client properties in Configuration Manager,
some clients are incorrectly listed without a wired network interface.
How should we proceed to troubleshoot this issue? Any pointers/ideas/suggestions are welcome.

"one would expect SCCM to "learn" both the IP/MAC configuration of the wired and the wireless interfaces."
Why would one "expect" this?
ConfigMgr uses heartbeat discovery to discover IP address information. What is your heartbeat discovery interval set to?
Jason | http://blog.configmgrftw.com | @jasonsandys

Dot1x + wake on lan

hi,
i found some datasheet about dot1x and WOL, but no ones gave me satisfaction this day.
I try to have the WOL with dot1x, but is it possible ?
i have switch 2960X (SW version :15.0(2)EX4) )
the initial port's configuration below (for dot1x of course) :
authentication port-control auto
authentication violation protect
dot1x pae authenticator
with the value "authentication port-control auto" the magic packet cannot access to the computer. When i remove the value, the compoter boot correctly but, i dont have any authentication, the port keeps the old authentication and i dont see my computer on the ACS when he reboots. (i see the computer for each reboots on ACS).
but, i can log on the network domain, i have an IP, but i dont know if the computer is legit or not
i want to see the computer's registration with "sh authenti session int xxxx"
without the value "port control auto" i just see :
MAC Address: Unknown
IP Address: Unknown
Status: Authz Success
and with the value :
MAC Address: b4b5.2fae.xxxx
IP Address: 10.45.66.54
User-Name: ps01826
so, how do I do ? is it possible or not ?
thank for the reply

i found the answer this morning :
"IEEE 802.1X Authentication with Wake on LAN
The IEEE 802.1X authentication with wake on LAN (WoL) feature allows dormant PCs to be powered when the switch receives a specific Ethernet frame, known as the “magic packet.” You can use this feature in environments where administrators need to connect to systems that have been powered off.
When a host that uses WoL is attached through an 802.1X port and the host powers off, the 802.1X port becomes unauthorized. The port can only receive and send EAPOL packets, and WoL magic packets cannot reach the host. When the PC is powered off, it is not authorized, and the switch port is not opened.
When the switch uses 802.1X authentication with WoL, the switch forwards traffic to unauthorized 802.1x ports, including magic packets. While the port is unauthorized, the switch continues to block ingress traffic other than EAPOL packets. The host can receive packets but cannot send packets to other devices in the network."
describes exactly the problem i have, and i cant fix it because if i remove the "authentication port-control auto" the computer does not authenticate anymore :/

K9NGM3-FIH and Wake-On-Lan?

Just updated my K9NGM3-FIH with the 2.7 BIOS and now I can't seem to find any way to get Wake-On-Lan on there, can anyone help me with this?

BIOS revisions seldom give new features, they are bugfixes and give new CPU support.
They do not improve speed or such....unless the speed is caused by a bug somewhere, but then a lot of people reported that.
BIOS is NOT a driver...leave it alone if you have no problems.
Anyway, in order to use WOL, you normally have to set the BIOS setting PME-wakeup and/or PCI-wakeup....as well in the driver that it needs to wakeup on magic-packet.
However, not all boards wakeup from poweroff, try sleep and see what it does.
What are you trying to do anyway? I ask this as wakeup-packets do not pass routers!! You have to be on the same LAN to send it.

Wake on lan for macbook pro residing behind a linksys router in clamshell

Hi:
I have a macbook pro residing behind a router at home
with its lid closed connected to an external display
and USB keyboard and mouse. When I use it at home, I
use the keyboard and mouse to wake it up (I believe
this is called clamshell mode) and use the external display.
I would like to access the machine from my office.
I have set up the "wake from lan" option in enery saver
and have forwarded port 9 (UDP) to the macbook pro.
But the machine does not wake up and I cannot ssh
into it from the outside (I have forwarded port 22 to it as well).
Is this a problem with operating it with the lid closed
that "wake on lan" is not working ?
How do I set this up ?
Thanks!

It has been fixed by latest SMC firmware update. Works fine on Mountain Lion.

Wake On Lan Problem

Similar Messages

Maybe you are looking for