MrBrillo
2012-07-21, 00:06
Hi there
This question may have been answered somewhere else, but the 337 postings make it a tad hard to find!
I'm running a 2010 iMac with the latest OS and patches which acts as my SB server. Occasionally, the Boom alarms (I have 3 booms in the house) resort to their default wake-up sound because it can't establish a connection with the Mac server. This also happens sporadically when the Mac hasn't been used for a while and I want to listen to the Boom radio. The solution is for me to manually wake the Mac by pressing the mouse button, or the keyboard. Well this obviously is not the solution if I want to wake up to Capital Radio, or Radio NZ!
So the problem isn't a Boom problem, but a Mac issue. I'm hoping someone else has experienced this and has a solution.
What I've done is to run a constant Ping command that never terminates to one of my Booms. Often this fails also, with a timeout error. I've set the config so the Mac now never sleeps, but this is a workaround that I'm not particularly fond of because it uses energy and sort of defeats the purpose of allowing a wake-up on LAN.
Does anyone have any clues that might help?
Cheers
Bob
This question may have been answered somewhere else, but the 337 postings make it a tad hard to find!
I'm running a 2010 iMac with the latest OS and patches which acts as my SB server. Occasionally, the Boom alarms (I have 3 booms in the house) resort to their default wake-up sound because it can't establish a connection with the Mac server. This also happens sporadically when the Mac hasn't been used for a while and I want to listen to the Boom radio. The solution is for me to manually wake the Mac by pressing the mouse button, or the keyboard. Well this obviously is not the solution if I want to wake up to Capital Radio, or Radio NZ!
So the problem isn't a Boom problem, but a Mac issue. I'm hoping someone else has experienced this and has a solution.
What I've done is to run a constant Ping command that never terminates to one of my Booms. Often this fails also, with a timeout error. I've set the config so the Mac now never sleeps, but this is a workaround that I'm not particularly fond of because it uses energy and sort of defeats the purpose of allowing a wake-up on LAN.
Does anyone have any clues that might help?
Cheers
Bob