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)

Similar Messages

Nokia Lumia 928 unresponsive even after several reboots

I had just watched a video online, and suddenly at the end of the video, the phone's screen started displaying weird pixels and lines throughout and the phone is now completely unresponsive, except for the power and volume buttons. I've tried the hard reboot several times, but the phone just reboots with the abnormal-looking screen. It will not allow me to get past the lock screen. It will do nothing except allow me to power it of and turn the volume up and down.
I've had this phone for less than a month... bought it after reading the glowing reviews about it. I loved the phone up until this point. I should have just kept my "dumbphone" because this crap is really ******* me off. I don't want this piece of junk anymore, but of course it's too late to return it and exchange it for another brand.

Yes it can be very annoying to buy something new and have it fail so soon. I recently bought a new Dyson cordless vacuume and it itermittantly failed shutting on-and-off. Dyson replaced it and the problem is now gone and has not returned So, with complex electronics I think you sometimes can end up with a lemon now and then.
FWIW, my wife and I ditched our feature phones and purchased two 928's and both of them have been flawless for the two months we have used them. I really like the Nokia hardware and am keeping my fingers crossed that it continues to perform well through the duration of our contract. If not, we have a warranty to fall back on.
I wish you success with your replacement and hope your gremlins never return!

Wake-On-Lan (WOL) after sleep causes high CPU usage

Hi,
I noticed a problem with constant high CPU usage on one of my cores.
As much as 60% was used.
The problem occures after I put the system to "sleep" (S3 state) and perform a WOL with a "magic packet".
I discovered that ACPI.sys+0x1af44 thread was responsible (using sysinternals ProcessExplorer) under the System process.
If i perform WOL while the machine was shut down everything works perfectly.
My NIC is "Realtek PCIe GBE Family Controller" and I'm using the latest drivers.
I discovered that if I disabled the option in Power Management for the device: "Allow this device to wake the computer", the CPU usage immediately went to normal (without restarting). But enabling it back the high CPU usage resumes. Performing
another sleep and awaking the system with power button "resets" the CPU usage issue for "good". Until i WOL from sleep again ofcourse..
I contacted the motherboard manufacturer of the problem but so far no real answer.
I'm saddened because I need the WOL feature.
I'm hoping somebody who has more insight in the behaviour of ACPI on W7 can answer my questions.
Regards
Specs:
Model Name : GA-X58A-UD7(rev. 2.0)
M/B Rev : 2.0
BIOS Ver : FC
Serial No. :
Purchase Dealer :
VGA Brand : Nvidia      Model : 7950GT
CPU Brand : Intel      Model : i7 950      Speed : 3.06GHz
Operation System : Win 7 64-bit      SP :
Memory Brand : Corsair      Type : DDR3
Memory Size : 6GB      Speed : 1600MHz
Power Supply : 450 W

Hi,
I noticed a problem with constant high CPU usage on one of my cores.
As much as 60% was used.
The problem occures after I put the system to "sleep" (S3 state) and perform a WOL with a "magic packet".
I discovered that ACPI.sys+0x1af44 thread was responsible (using sysinternals ProcessExplorer) under the System process.
If i perform WOL while the machine was shut down everything works perfectly.
My NIC is "Realtek PCIe GBE Family Controller" and I'm using the latest drivers.
I discovered that if I disabled the option in Power Management for the device: "Allow this device to wake the computer", the CPU usage immediately went to normal (without restarting). But enabling it back the high CPU usage resumes. Performing another sleep
and awaking the system with power button "resets" the CPU usage issue for "good". Until i WOL from sleep again ofcourse..
I contacted the motherboard manufacturer of the problem but so far no real answer.
I'm saddened because I need the WOL feature.
I'm hoping somebody who has more insight in the behaviour of ACPI on W7 can answer my questions.
Regards
Specs:
Model Name : GA-X58A-UD7(rev. 2.0)
M/B Rev : 2.0
BIOS Ver : FC
Serial No. :
Purchase Dealer :
VGA Brand : Nvidia      Model : 7950GT
CPU Brand : Intel      Model : i7 950      Speed : 3.06GHz
Operation System : Win 7 64-bit      SP :
Memory Brand : Corsair      Type : DDR3
Memory Size : 6GB      Speed : 1600MHz
Power Supply : 450 W
same prob here. has anyone found a solution?
...stephen

Firefox will not complete the installation even after several attempts of rebooting the computer.

I downloaded the Firefox 9.0.1 upgrade but it will not complete the installation on my computer. Everytime I try to remove the program, it tells me to reboot the computer to finish the installation. After several reboots, the same error keeps coming up.

Try to run the Firefox program once as Administrator (right-click firefox.exe: Run as Administrator).
If that doesn't solve the problem then remove the Firefox program folder (C:\Program Files\Mozilla Firefox\) to do a clean reinstall.
Download a fresh Firefox copy and save the file to the desktop.
*Firefox 9.0.x: http://www.mozilla.org/en-US/firefox/all.html
Uninstall your current Firefox version, if possible.
*Do NOT remove personal data when you uninstall the current version or you lose your bookmarks and other data in the profile folder.
Remove the Firefox program folder before installing that newly downloaded copy of the Firefox installer.
*It is important to delete the Firefox program folder to remove all the files and make sure that there are no problems with files that were leftover after uninstalling.
*http://kb.mozillazine.org/Uninstalling_Firefox
Your bookmarks and other profile data are stored elsewhere in the Firefox Profile Folder and won't be affected by a reinstall, but make sure that you do not select to remove personal data if you uninstall Firefox.
*http://kb.mozillazine.org/Profile_folder_-_Firefox
*http://kb.mozillazine.org/Profile_backup
*http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Clean_reinstall

Wake on lan from power OFF

It appears that Mac's don't provide wake on lan from complete power off. I have no problem powering up my Mac from sleep, but it won't turn on from power off (like every PC I've tried). This is not difficult to do, as every $200 PC on the market w/ WOL does it.
I have my Mac on a large shared UPS with serveral other computers and network gear, etc.
There is a linux server which actually communicates with the UPS. During a power failure, that linux box will connect to ever other machine on the network sharing this UPS and tell them to SHUT OFF, not sleep, because hard power failure is emminent. When all remote machines are off, the linux machine shuts off, and the UPS powers off it's outlets.
On power recovery, the UPS waits until it's batteries are sufficiently recharged, and turns back on, powering up it's protected outlets. All the machines see power come back on, and are set to reboot.
Here is the problem. If the power comes back on AFTER the remote machines are shut down, but before the linux box turns off, the linux box sees power recovery, and the UPS never shuts off it's protected outlets. Now all the remote machines are off, and won't ever see their power cut off, and then recover, so they don't turn back on.
The PCs are easy... hit them with a wake-on-lan packet and they reboot from complete power off... but not the trusty Mac because Apple didn't implement that part of the wake-on-lan standard!
So... I'm faced with abandoning wake on lan for all the machines and building an interface with a big relay to KILL power to all remote machines to power them back on. Isn't this more than just a little silly? Apple... why not just make your machine comply with the standard so that it plays nicely in a mixed environment!
Providing wake on lan from sleep, and power on with power recovery, but no wake on lan from OFF is just ridiculous.
I welcome any ideas...
PowerMac G5 Dual 2.0 Mac OS X (10.4.8)

Malcolm,
If I make it sleep, then I'm forcing it to crash when the power turns off. The idea here is for a graceful shutdown before emminent power failure when the UPS battery runs out.
The only reason it's getting shut down is that the main power has failed and the UPS battery is running low.
I agree that with no power they can't interpret packets and react... but that's why proper wake-on-lan implementations keep the NIC powered up to watch for WOL packets.
Thanks,
-Russ

FF4 starts using all of available CPU after several hours, needs reboot.

This used to happen in the previous release version of FF, and it's apparently still the case in FF4.
Everything works fine after I start FF4. I have 50+ tabs open and visible through TabMixPlus and FF is fast and snappy just like I want it to be, but after several hours (most often when I come back to the PC in the morning) it starts hogging too much CPU. I don't care so much for memory, I have plenty of that to spare, but once it maxes out a core once per second, FF completely slows down about that often and becomes completely unusable. I have to reboot it every time to fix that.

Please provide us with your Event Viewer administrative logs by following these steps:
Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file to skydrive or a file sharing service and put a link to it in your next post
If you have updated to win 8.1 and you get the error message "the system cannot find the file specified" it is a known problem. The
work around is to edit the registry. If you are not comfortable doing this DONT. If you are, backup the key before you do
Press Win+"R" and input regedit
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels. Delete "Microsoft-Windows-DxpTaskRingtone/Analytic"
Wanikiya and Dyami--Team Zigzag

A78M-E35 can't wake on lan after power unplug

Hi, this is my first HTPC with Kodibuntu and trying to use the wake on lan to boot it.
I have disabled EuP 2013 and enable Resume by PCI-E device.
And I also add the MAC address and IP to TP link router ARP list.
But WOL just worked well if it boot immediately after shutdown.
So my question: is it possible to wake on lan even if i completely shutdown and unplug the power?
thanks in advance

Quote from: badboy2k on 09-February-15, 17:03:58
no that is not possible as your computer has no power!
WOL is to bring the computer out of Sleep/Hibernation not power up when its got no power to function or is fully shut down!
oic. thank you for your reply!

Wake on Lan will not shutdown

Hello everyone,
I hope I'm posting in the right forum as I think I am simply over looking something.
I have a dual boot system (win 7 and arch) and am trying to get Wake on Lan to work. I have installed ethtool and wol to find my card defaults to receive magic packets (g). I'm using an Asus Rampage IV Extreme mobo with the latest bios. Everything performs as it should with windows when shutting down or hibernating. My issue is when I suspend or shutdown arch it powers down completely and then reboots in a matter of seconds. If I force the card to wol unicast I can suspend the system (sometimes) but will still not shutdown without rebooting. I have used netctl to force the card to wol disabled and I can suspend it everytime. However, even setting wol to disabled, the computer will not shut down. I have disconnected the ethernet cord and even disabled the NIC in the bios but still the same results. If I shut down arch and pull the power when it initially shuts down it simply reboots as soon as power is connected again. The only way I have found to shut it down is to disable "wake on pcie" in the bios. This in turn also disables the windows Wake on Lan. If anybody has an idea of what a solution might be I am all ears (even if it calls for some trolling, I'm sure this deserves some :-)
Thanks in advance

Long standing problem for me and many others.. just google to see this but no solutions, 'linux wol will not shutdown'
https://bbs.archlinux.org/viewtopic.php?id=173648
http://xpenology.com/forum/viewtopic.ph … 82&p=11514
https://communities.intel.com/message/168708
http://serverfault.com/questions/349898 … nt-reboots
http://askubuntu.com/questions/281039/o … ake-on-lan
https://forums.gentoo.org/viewtopic-p-7 … ml#7493630
http://askubuntu.com/questions/132882/w … a-shutdown
http://superuser.com/questions/605324/m … ed-in-bios
Recently, I have been testing several systems (Z77 and H97-based) after I disabled all references to 'xHCI' as it pertains to USB settings. I also enabled wake on keyboard per one suggestion in one of the links above. In about 15 power cycles, I haven't observed an unintentional wake-up with 'wake on PCIe' enabled in the BIOS. More time is needed before I will claim either setting is the fix.
Last edited by graysky (2015-05-03 14:50:27)

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

How to enable wake on lan on Thinkpad Twist?

I have a Thinkpad Twist purchased because of the presence of the ethernet card.
Unfortunately I can not turn wake on lan.
I did several searches and several attempts without success.
Someone managed to enable wake on lan?
Thank you.
(sorry for the English by Google Translate)
Solved!
Go to Solution.

Hey there Cello67,
To enable Wake On Lan on a Thinkpad twist:
1) You will first need to power down your laptop completely.
2) Then turn it on, as soon as you turn it on start hitting the enter key to interrupt start up. This will take you to a start up menu.
3) From here you will need to enter your BIOS.
4) Move right over to the Config, then press enter on the Network Selection
5) The first option you should have is Wake On Lan. You can change this from disabled to either AC Only or AC and Battery.
After you have done this save your settings, and resume startup. Once the computer has finished booting go to your desktop, and pull out your charm bar by pressing Win Key + C or with a swipe from the right side of your screen in. From here you will:
1) Enter the Control Panel
2) Device Manager - > Your Ethernet Card/Adapter
3) Click the Power Management Tab
4) Select "Allow this device to wake the computer"
Hope this helps Cello67!
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution".! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.

Wake over LAN

Since updating to X.6.8 my MP has problems waking remotely. I'm connected to my router by Ethernet.
I haven't tried all that much to resolve this as I'm not aware there is anything else but the wake over LAN checkbox to enable this service. I have tried unchecking the box and re-checking it, I've also tried restarting my router and setting a different length of time before the MP goes to sleep.
Oddly enough I can wake the MP if I try a little time after it goes to sleep, but if I leave it for several hours it won't wake.
It isn't just one situation/application that won't wake it either, my Apple TV won't, shared devices from the finder on other macs won't and other services like the Apple remote app and eyeTV app from the iPhone won't either.
Any thoughts.

hoping someone can help me here, as I want to accomplish WOL in my workplace. I'm in a building that has a central router that divides the internet into 4 different offices (into jacks in the wall). The central router is a linksys befsr41 that I don't have access to because it belongs to the property manager. The central router's ip address is 192.168.1.1 This router is not wireless, but I need wireless in my office, so I have my wrt54gc in my office to use with my tablet pc. I've gotten my computer to wake up no problem over LAN at home, over WAN at home (from remote location), but when I'm at my office (2 routers chained together) I don't know what I need to do to get it to work consistently. So my questions are: 1. What settings, if any, do i need to change on the central router? Do I need to port forward to the IP of MY router (or my CPU)?? 2. Same question for my router? I've looked all over the net and can't find any info on what to do for WOL in a multiple router environment such as mine. I guess I need to somehow tell that magic packet thingy to go through the central router, then through my router, and recognize my MAC address and ip. I really appreciate help in this matter.

No Wake-On-LAN for powered-down Macs?

I'm relatively new to Mac and don't have a lot of Mac experience or knowledge. Last week I completed the "Mac OS X Deployment v10.4" training in Sydney where the trainer told me that Wake-On-LAN will only work if the Mac in question is in sleep mode -i.e., you can't wake up a Mac that has been shut down. Is this really true?
As an administrator of Windows machines this seems like quite a shortcoming. From where I am sitting I can rebuild any room of computers in any town in my area of control (an area greater than 100,000 square kilometres in NSW, Australia) without having to be there physically to turn on the PCs. At the moment our two Mac rooms are located at my own site, but without Wake-On-LAN, there's no way I could see Macs being deployed anywhere else.
If Wake-On-LAN really does only work with Macs in Sleep mode, then how much power does a 20" Intel iMac draw when in Sleep mode? I really don't like the idea of setting a schedule for every Mac to turn on at a certain time then have them go into sleep mode each and every day on the off chance that I might want to rebuild just one of them. This seems like an awful waste of power to me.
Don't get me wrong, here. I'm not trying to flame because I'm very - very - impressed with Mac in almost every other respect (except the Finder and the Dock) and would switch to Mac long before I stomach Vista, but no Wake-On-LAN to me seems like an incredible stumbling block to Mac adoption.
Intel iMac 20" Mac OS X (10.4.9)

I've already complained of Mac's variation from the "standard" WOL implementation. This problem goes a step deeper as I just discovered.
If in the energy saver options you check the "Restart after a power failure event", the machine will do just that. If the power fails, and then comes back, the machine will boot.
If however, you cleanly shut down the machine, and then power fails, it does not turn back on when the power recovers. All PC's that have auto-power on with AC power restored set in their bios don't care if the machine was cleanly shutdown or crashed... when power comes back, it boots.
The problem here is that when a UPS detects a power failure and eventually decides to shut down the attached computer it should do so cleanly, not by just crashing it (that defeats the purpose of having a UPS!). After the computer turns off, the UPS will turn itself off, cutting power to the computer all together. When the AC power to the UPS returns, and the batteries charge sufficiently, it will turn BACK on, and restore power to the computers.
As it stands now, I have no mechanism by which to force my Mac to boot back up! I could depend on a linux machine on the network (that does behave properly) to send a WOL packet, but it doesn't do that correctly either... so I'm SOL
I can understand having 3 options for reboot after power restore. (1. Restore Always, 2. Restore when system on and power fails, 3. Never Restore).
Only giving us options 2 and 3 is just an oversight of how computers are used in the real world. For the desktop user that may on rare occasion find his machine powered off, and just presses the power button, this is a non issue... But in my opinion this completely eliminates a Mac like this from being used as a webserver/mailserver or other application where uptime is paramount.
I can't believe that Apple would overlook something so important and not provide a mechanism by which a UPS could turn a computer back on after a power recovery. Perhaps there is a non-published setting that doesn't have a check box on a form, that an OEM UPS driver would set that says "pretend you crashed".

Cisco RV180 and Wake-On-Lan (WOL)

Hello,
I got a RV180 (firmware version: 1.0.1.9) and I am bit surprised by the lack of the configuration flexibility...
I am trying to use Wake-On-Lan (from internet) to wake up a machine in my home (trying to be green and not keep the machine on all the time, just when i need it).
The configuration is quite simple:
Work machine ----> (internet) ----> (WAN) RV180 (LAN) ----> Home Machine (off, linux, wol enabled for UNICAST and Magic Packet - flags "ug")
What i tried so far:
1. All the following RV180 settings together:
   a. Used Port Forwarding from the WAN IP to the Home Machine IP (UDP port 7 and 9)
       - i had no choice but to put the Home Machine's IP address, since i cannot put the BROADCAST address (xxx.xxx.xxx.255) <- forbidden in the configuration page (i wonder if a new version of firmware allows this)
   b. Used Static DHCP to pair the Home Machine's IP to it's MAC address
   c. Used IP/MAC binding for the Home Machine
2. All the following RV180 settings together:
   a. Created a PPTP VPN connection
   b. Connected from the Work machine (obtained a LAN IP, can ping the Home Machine if it is on)
   c. Tried to send a broadcast message to LAN (no success !)
3. I also tried to activate the MULTICAST and BROADCAST WOL flags on the Home Machine but it seems that it receives some messages and the machine wakes up in a very short amount of time after i shut it down (it seems that RV180 sends some messages over LAN by itself).
In all the 3 possibilites above i was not successful in using WOL....
Is there any possibility to use WOL from internet in this configuration ?
Are there new options that will allow WOL from internet in the latest firmware ?
Any advice is appreciated
Thank you
Mircea

Dear Mircea,
Thank you for reaching the Small Business Support Community.
I was researching about your concern and found several people with the same inquiry where they were told WoL is not a supported feature on these Small Business Routers and that I think is a correct assumption, however I found the below threat where someone with a similar case scenario as yours were able to make it work, it's on a different RV router but I thought I may be interesting for you to check;
https://supportforums.cisco.com/thread/2188810
Please let me know if there is any further assistance I may help you with.
Kind regards,
Jeffrey Rodriguez S. .:|:.:|:.
Cisco Customer Support Engineer
*Please rate the Post so other will know when an answer has been found.

Wake on Lan works with Ethernet, not over Wi-Fi.

Hello, after several months of tests I came to this conclusion.
Wake on Lan only works with Ethernet for my iMac. Wake on Lan over Wi-Fi works for a few hours, but if the iMac is asleep for 6 hours or so, it becomes unavailable... On the other hand, with Ethernet it's always available even if it sleeps for an entire week.
My iMac isn't that old (mi-2011), so I guess it should handle Wake on Lan over Wi-Fi. Is it a software issue?
- I've got a MacBook Pro since Snow Leopard 10.6 and now with Mountain Lion it handles Wake on Lan over Wi-Fi without problem.
- I've got my iMac since Lion. Does the iMac only handle Wake on Lan with Ethernet and works differently compared to the MacBook Pro?
I prefer to use Wake on Lan over Wi-Fi because for the tests I've placed my iMac in the living room in order to plug it to the Time Capsule, but the right place for my iMac is in my bedroom.
I tried to change the MTU size as it is described here: http://osxdaily.com/2012/08/02/fix-os-x-mountain-lion-wireless-connection-proble ms/
Note that "Wake on Lan" is checked in my System Preferences, I don't think it's my router's fault, because my Apple TV, AirPort Express, iPhone 5, iPad 2 and my Printer don't disconnect even when they're asleep (I'm talking about my printer and Apple TV in that case).

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.

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.

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

Similar Messages

Maybe you are looking for