Wake on Lan issue solved easily !

Solved !
New to Macs... migrating from Windows XP finally ! After a little fiddling and investigating found the solution:
Go to System Preferences: Sharing: Select Remote Login !
Voilá... your done.
Note it takes almost 15 seconds to wake up my brand new Imac... It took under 1 second to wake my nine year -old PC !

Remote Login let you administer your computer remotely via SSH.
Wake on LAN works differently on a Mac.
First the computer must be turned on. If it is turned off there is no way to wake it up remotely.
Settings, to enable WOL when the Mac is into Sleep state are found in System Preferences, Energy Saver, Wake for network access

Similar Messages

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

IMac "Wake on LAN" issues

When I leave my iMac I put it to sleep or it eventually puts itself to sleep. I have Mozy installed for remote back-up and I have LogMeIn installed for remote access.
Mozy is not backing up on schedule and instead is requiring that the computer be awake before it starts. LogMeIn shows the iMac offline when it is sleeping. I have checked the LogMeIn pref to "wake on LAN".
Anyone know if there are any Mac OS system prefs that will allow these to applications to function when the computer is sleeping?

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 Issue

I am unable to get Wake On Lan (WOL) to turn on 3 x Lenovo H330 computers in our office when they are turned off (S5 mode). However, I can turn on the computers from standby (S3 mode). We have 2 other Lenovo computers in the office, diffferent models, and I can turn them on from S5 using WOL with no problems.
In the BIOS I can either set Wake On Lan to Disabled or Primary. It is currently set to Primary.
I have made sure that network driver has been configure so that WOL is active. I have also updated the network driver (Intel).
What else can I do to resolve this issue?

Anyone?

Wake-on-Lan issue, low power in eth0?

Yes, I know there are 'n' posts about wol... but I think this is something special...
My wol looks 100% (working over lan), when I want to wake up my machine over the internet then it looks like this:
-let's say I've got my 'server' on, so I tunnel with ssh and then I halt server
-now server is off... when immediately use wol over internet, something like this 'wol -p 9 my.ip server.mac' it's working and my server just wake
-if I turn server off again but I do not use wol immediately and let's say I just wait a minute (or I turn off power supply)... and then I use exactly the same command for wol... it's just not working
I think it's something with my eth0 and 'not enought power' / 'no power'... my eth LED is not blinking when I turn off server so I suppose there is no power after one minute from 'halt'... This question mb seems trivial but I'm not expert about HW/network :-).
If u know how to help with this pls help, thanks

The reason why this happens is roughly described here http://serverfault.com/questions/190888 … 417#241417
See if binding an IP to your computer in the router settings helps.
Unfortunately I can't help you more than that, I can't get WOL over internet (WOI? WOW?) to work either.
If everything else fails though and you love WOL as much as I do, you can have an always-on server of some sort (ranging from gaming consoles to android phones and routers with dd-wrt) to ssh to and wol from.
Last edited by MadCatMk2 (2011-08-10 21:23:22)

T410 Wake On Lan Issues

I'm not sure if this has been discussed previously, but I am having a horrible time getting the WOL functionality to work on the 410s. It works sometimes, but it's spotty at best, and I cannot find any information with anyone having this much trouble getting it to work. We store them in a cart most of the time, and I want to be able to push out updates to them while they are in the cart. Is anyone else having this same issue? Or does anyone have any advice on how to get these to start waking up more regularly?
I think part of the problem is the nic is getting turned off when the AC is unplugged. I've tried setting the wol to both AC and battery, but I think it is still shutting off.
Any help would be appreciated!

hey aawilson319,
i suggest heading to http://support.lenovo.com and if there is a need; update your unit.
it could be that the bios of your unit is not the latest and this is causing the issue.
WW Social Media
Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
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"!
Follow @LenovoForums on Twitter!
Have you checked out the Community Knowledgebase yet?!
How to send a private message? --> Check out this article.

MOVED: Wake On LAN issue with Z68A-GD80-G3

This topic has been moved to Linux/Unix.
https://forum-en.msi.com/index.php?topic=157515.0

That's a bit worrying. Why would Intel suggest an 18Gb cache is it would wear out so quickly?
Not that I have to be concerned the %^&%^& thing wont work!

Wake On Lan for Pavilion 500-046

I have been using Wake On Lan on my other computers to wake up computers on my network that have been shut down using the shutdown command from Windows 7. This is a very useful feature for me and I would like to get it working on my HP Pavilion Desk Top computer with Qualcomm AR8161 PCI-E Gigabit Ethernet controler. The Bios on the 500-046 has this option, and I have set it to ENABLE. I am running Windows 8.1 update on the Pavilion. I have, also, looked at other possible power settings in the device manager but I'm not having any luck getting this to work. There is absolutly no response from the Pavilion when a Wake On Lan signal is sent. A similar question was posted by me a couple of days ago with no responses. Maybe and Expert could give it a whirl. Thanks for any help.
This question was solved.
View Solution.

Hello fredkoch3,
I have read your post on how you are having problems wake on LAN issues with your desktop computer, and I would be happy to guide you towards a resolution!
To begin, I recommend following this thread on "Wake on LAN" (WOL) behavior in Windows 8 and Windows 8.1. This should help explain how (WOL) is used for Windows 8.1 in comparison to Windows 7.
To find out if your system can be set to Wake on Lan I suggest running a "powercfg" command on your computer. This will check the power management features available. To do this, please follow the proceeding steps below:
Press and hold the Windows Key button and the R button simultaneously
Type in the word cmd in the box provided
In the Command Prompt window, please type in the command "powercfg -availablesleepstates"
Please compare the available sleep states using the System Power States document to see if (WOL) is available.
Reference: http://msdn.microsoft.com/en-us/library/windows/desktop/aa373229.aspx
Please re-post with the results of your troubleshooting, and I look forward to your reply!
Regards
MechPilot
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

No Wake-on-LAN possible since updating to ML

Hi everybody,
since updating from OS X 10.7 to 10.8 (clean install), Wake-on-LAN does not work anymore. Setup: Mac mini (Early 2011) connected to Time Capsule (2nd gen) via devolo dLAN. Mac mini goes to sleep after 30 minutes and eventually disappears from the network. Sending Wake-On-LAN packets or using Back To My Mac fail, it simply won't wake up.
Wake-on-LAN worked smoothly under 10.7 after some problems. Any ideas?
Thanks and regards
Steffen

Yes, wired. It's a wired Ethernet-over-Power Line connection, see www.devolo.com for technical details. WiFi is turned off. Anyway, wired and WiFi use the same static IP address within the LAN, it's alway 10.0.1.2, the standard host for NAT port forwarding. The network setup has always been this way and never caused problems. It has been running smoothly for almost 18 months now, using LogMeIn, Plex, jDownloader, EyeTV and other stuff for remote access via iPhone, iPad or web interfaces. Glitches started after upgrading to ML.
I just had the idea that the DHCP lease time configured in the Time Capsule might be the source of the problem. It was set to three hours, which explains why the Mac mini (10.0.1.2) eventually disappears from the list of network devices after it went to sleep: IIRC the Bonjour Sleep Proxy discards the IP reservation as soon as the lease time has elapsed, making the corresponding network device unreachable. Well, I cannot remember I changed anything in the network setting of the Time Capsule, but increased DHCP lease time to 60 days now. As soon as I get home, I will push the Mac mini's power button to re-register it's IP in the LAN and check if the new DHCP lease time solves the Wake-on-LAN issue.
I wonder why I did not run into that problem with Snow Leopard or Lion. Maybe they really changed something under the hood with regards to the Power Nap feature. For now, it's just guessing, so any further ideas are warmly welcome.

MSI H87M-G43 and Wake On LAN

I have an MSI H87M-G43 with BIOS v.1.8 running Windows 8.1 64-bit. I cannot get Wake On Lan to work with this motherboard. Can anyone confirm this is working with the MSI H87M-G43 motherboard?
Here is the PC Configuration:
CPU Intel Core i5-4440 3.1GHz
PSU Corsair CX430
DIMM1:
DIMM2: Corsair XMS3 DDR3 4GB CMX4GX3M1A1333C9
DIMM3:
DIMM4: Corsair XMS3 DDR3 4GB CMX4GX3M1A1333C9
SATA Port 1: SSD Samsung 840 EVO 120GB
SATA Port 2:
SATA Port 3: HDD Samsung 1TB SATA II
SATA Port 4: HDD Samsung 1TB SATA II
SATA Port 5: DVD Liteon IHAS124-14 24X
SATA Port 6:
SATA Port 3+4 RAID1 (Mirror)
BIOS v1.8:
01. F6 Restore Defaults: Load Optimized Defaults
02. LAN Option ROM: Enabled
03. SATA Mode: [RAID Mode]
04. SATA3 Hot Plug: Enabled
05. SATA4 Hot Plug: Enabled
06. Initiate Graphics Adapter: [IGD]
07. Serial (COM) Port 0: Disabled
08. Parallel (LPT) Port: Disabled
09. EuP 2013: Disabled
10. Windows 8/8.1 Feature: Enabled
11. Wake Up Event By: [BIOS]
12. Resume by PCI or PCIe Device: Enabled
13. Resume from S3/S4/S5 by USB Device: Enabled
14. GO2BIOS: Enabled
I have installed the following drivers:
01. Intel Chipset Driver 10.0.20
02. Intel SVGA Driver 10.18.10.3960
03. Realtek PCIE Network Drivers 8.35.716.2014
04. Intel RST RAID Driver 13.1.0.1058
05. Realtek HD Audio Drivers 6.0.1.7111
06. Intel Management Engine Components 9.5.15.1730
In the Realtek PCIe GBE Family Controller properties I have set:
01. Allow the computer to turn off this device to save power: Ticked
02. Allow this device to wake the computer: Ticked
03. Only allow a magic packet to wake the computer: Ticked
04. Energy Efficient Ethernet: Disabled
05. Green Ethernet: Disabled
06. Shutdown Wake-On-Lan: Enabled
07. Wake on Magic Packet: Enabled
08. Wake on pattern match: Enabled
I have also tested that when I send Wake On Lan magic packet data from another PC, this PC successfully receives the Wake On Lan magic packet data. However, when the PC is in Sleep/Hibernate/Shutdown state, it does not wake when it receives the Wake On Lan magic packet data.
TIA

Quote from: mville on 10-February-15, 02:16:43
No.
It is difficult to identify where the problem is then
Quote from: mville
... and to make matters worse, during extensive testing of this Wake on LAN issue, I set:
Wake Up Event By: [OS]
Resume From S3 by USB Device [Enabled]
and my USB keyboard is also unable to wake from S3/Sleep. When Wake Up Event By: [BIOS] is set, the USB keyboard is able to wake from S3/S4/S5.
Well mine does not wake up by keyboard, which is what I want, I need to see if keyboard with power key will work.
Quote from: mville
Last week, I submitted a support ticket with MSI, who responded with a basic set of wake on LAN instruction. I explained that, although I have followed the instructions, it still does not work. MSI have now gone silent on me.
I had somewhat similar experience with ASUS, but they just kept repeasting themselves, seems like language barrier or they just pretending.

K9A2 CF Wake On Lan / WOL issue

Hi everyone,
Need a bit of help here
I've been finding it impossible to get Wake on Lan working on my PC. I cannot manage to get the lights on the back of the LAN port to stay on after sleep or shutdown. I've tried all different settings in BIOS:
- enabled hpet
- enabled acpi function
- set acpi state = s3
- enabled resume by pci (pme)
- enabled resume by pci-e
- in Vista device mgr I have enabled "Shutdown Wake-On-Lan"
- and "Allow this device to wake the computer" - although I didn't think that should go along with "allow the PC to turn off this device to save power".
I have also upgraded bios (1.8) and LAN driver (Realtek 8111B v6.216).
I'm not sure if the issue could be related to the PSU?
I'm completely out of ideas - can anyone help?
Has anyone got WOL working using the onboard LAN for this board K9A2 CF?
If you need any more info then let me know
Thanks for your help,
Colly

What happens is that CMOS forgets all manual settings you have done previously. Starts a-fresh. You set date, time, out-speed for the processor and boot order. Some other adjustment too, but what I don't know.
Did you use LiveUpdate for the procedure? LiveUpdate is easily disturbed because it runs in a busy Windows environment. That may be another reason for the problem you have. You may have to re-update. Please ust the forum USB-tool next time. It does its job in a quiet environment.

M93p BIOS issue: PowerOff not correct if Enhanced Power Saving Mode Disabled and Wake on Lan Enabled

Hi Levnovo support team, Recently I bought a M93p tiny(10AAA05MTW)(BIOS revision FBKT56A)and installed with Ubuntu 13.10 myself.Then tried to enable wake on lan for my tiny. The followings are my test result. 1. Enhanced Power Saving Mode Enabled, no mateter what is Wake On Lan setting PowerOff system is OK. 2. Enhanced Power Saving Mode Disable and Wake On Lan Disabled PowerOff system is OK. 3. Enhanced Power Saving Mode Disabled and Wake On Lan Primary or Automatic PowerOff system is NG. When I tried to power off system, it always can poweroff(LEDs on front all off) then POWER ON again in 2 or 3 seconds. I cannot accept this test result ,system should poweroff not reboot again. It's really hard to understand why enabling Wake on Lan will affect power off function. I tried the same procedures with my another M92p(3212A16)(BIOS revision 9SKT70AUS), and it works well.

Did you ever get a fix for this?Having the same issue on 3 of 6 machines that just arrived.

Wake on LAN Policy Issues... No WOL Packets

There's no sign of WOL packets in my captures (wireshark w/ a display
filter for UDP traffic only). I can see "packet sent" notifications on
the console tho...

Marcus Breiden wrote:
> On Mon, 17 Sep 2007 14:22:08 GMT, _jd_ wrote:
>
>> The server switch port was mirrored and all packets were captured with
>> wireshark during the policy schedule window. No sign of WOL packets in
>> the capture. All UDP traffic relates to NCP/NDS/SNMP protocols only.
>
> hmm... strange, could you post the trace?
Thanks Marcus. Here is is:
[9/14/07 15:19:18.577] WOLService:ServiceManager: Starting the
ZENworksWOLServiceManager...
[9/14/07 15:19:18.604] Service Manager (TCP): Initializing
'WOLServiceManager'...
[9/14/07 15:19:18.620] Service Manager (TCP): ServiceManagerServer
information: <IP>:16246
[9/14/07 15:19:18.621] Service Manager (TCP): ServiceManagerServerInfo:
getSerDirectory: prop_file_url =
file:/vol1:/ZENworks/RemMgmt/Server/properties/TracerFilter.properties
[9/14/07 15:19:18.621] Service Manager (TCP): Returning
"\vol1:\ZENworks\RemMgmt\Server\properties" as the directory for the
serialized file.
[9/14/07 15:19:18.621] Service Manager (TCP): Returning this as the
directory to store the file: \vol1:\ZENworks\RemMgmt\Server\properties
[9/14/07 15:19:18.642] Service Manager: Using properties file
/WOLStart.properties
[9/14/07 15:19:18.677] Service Manager: ---- begin service data for 'WOL
SERVICE'
[9/14/07 15:19:18.677] Service Manager: Service Name = WOL Service
[9/14/07 15:19:18.677] Service Manager: Class Name =
com.novell.zenworks.desktop.remotewakeup.WakeUpLAN Service
[9/14/07 15:19:18.678] Service Manager: --- begin custom properties ---
[9/14/07 15:19:18.678] Service Manager: --- end custom properties ---
[9/14/07 15:19:18.678] Service Manager: Load Type = Auto
[9/14/07 15:19:18.679] Service Manager: Service Type = User
[9/14/07 15:19:18.679] Service Manager: Restart Option = Don't Restart
[9/14/07 15:19:18.679] Service Manager: ---- end service data for 'WOL
SERVICE'
[9/14/07 15:19:18.679] Service Manager: Autoloading boot services
[9/14/07 15:19:18.679] Service Manager: No boot services defined
[9/14/07 15:19:18.679] Service Manager: Autoloading system services
[9/14/07 15:19:18.679] Service Manager: No system services defined
[9/14/07 15:19:18.679] Service Manager: Autoloading system services
[9/14/07 15:19:18.680] Service Manager: Load sequence ..
[9/14/07 15:19:18.680] Service Manager: 0) (0) WOL Service
[9/14/07 15:19:18.681] Service Manager: Autoloading, system service name
= WOL Service class =
com.novell.zenworks.desktop.remotewakeup.WakeUpLAN Service
[9/14/07 15:19:18.689] Service Manager: Attempting to load class
'com.novell.zenworks.desktop.remotewakeup.WakeUpLA NService'
[9/14/07 15:19:18.690] Service Manager: start(ServiceDataAccessor,
String[]) not found in
'com.novell.zenworks.desktop.remotewakeup.WakeUpLA NService'
[9/14/07 15:19:18.758] WOLService:ServiceManager: Starting the Wake on
Lan service...
[9/14/07 15:19:18.764] WOLService:ServiceManager: Listener file not found
[9/14/07 15:19:18.799] WOLService:ServiceManager: Starting the service
[9/14/07 15:19:18.840] WOLService:ServiceManager: Logging is as adminfalse
[9/14/07 15:19:18.856] WOLService:ServiceManager: the getScope returned0
[9/14/07 15:19:18.856] WOLService:ServiceManager: Authenticate AS code
dn CN=WOL Service_<myServer>.OU=<myOU>.O=<myO> Tree<myTree>
[9/14/07 15:19:18.856] WOLService:ServiceManager: Authenticating as
CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:18.856] WOLService:ServiceManager: NDAPAuthUtilities:
getID: Trial: 0
[9/14/07 15:19:19.414] WOLService:ServiceManager: NDAPAuthUtilities:
getID: return value= 0
[9/14/07 15:19:19.414] WOLService:ServiceManager: getID returned value0
[9/14/07 15:19:19.415] WOLService:ServiceManager: the syncString.str
name isCN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.415] WOLService:ServiceManager: authenticate as
returns istrue
[9/14/07 15:19:19.415] WOLService:ServiceManager: NDAPAuthUtilities:
createInitialContext: Getting initial context: ndsTree: <myTree>,
objectDN: CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.415] WOLService:ServiceManager: NDAPAuthUtilities:
createInitialContext: Trial: 0
[9/14/07 15:19:19.415] WOLService:ServiceManager: NDAPAuthUtilities:
createInitialContext: Creating initial context on ndsTree + objectDN
[9/14/07 15:19:19.420] WOLService:ServiceManager: NDAPAuthUtilities:
reLookUp: look up for CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>,
handle.baseDN: CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.420] WOLService:ServiceManager: getAttributesofDN:
Attributes of:
[9/14/07 15:19:19.420] WOLService:ServiceManager: NDAPAuthUtilities:
getAttributesOfDN: Trial: 0
[9/14/07 15:19:19.435] WOLService:ServiceManager:
getAttributes:Attributes={host server=Host Server: Distinguished Name
CN=<myServer>.OU=<myOU>.O=<myO>}
[9/14/07 15:19:19.435] WOLService:ServiceManager: The getAttributesofDn
returned{host server=Host Server: Distinguished Name
CN=<myServer>.OU=<myOU>.O=<myO>}
[9/14/07 15:19:19.436] WOLService:ServiceManager: The ndsSyntaxId is 1
[9/14/07 15:19:19.436] WOLService:ServiceManager: The base class is
com.novell.service.nds.naming.net.NetAttribute
[9/14/07 15:19:19.436] WOLService:ServiceManager: the attribute addeed
is
com.novell.zenworks.desktop.inventory.zencommon.Di rectoryAttribute@c24c0
for Host Server
[9/14/07 15:19:19.437] WOLService:ServiceManager: Server DN is
CN=<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.437] WOLService:ServiceManager: Logout in
NDAPAuthUtilities the syncString.str isCN=WOL
Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.437] WOLService:ServiceManager: Authenticating out as
CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.437] WOLService:ServiceManager: NDAPAuthUtilities:
clearID: Trial: 0
[9/14/07 15:19:19.437] WOLService:ServiceManager: logout tries:0
[9/14/07 15:19:19.440] WOLService:ServiceManager: After notifying
[9/14/07 15:19:19.440] WOLService:ServiceManager: Logout from NDS
returnedtrue
[9/14/07 15:19:19.440] WOLService:ServiceManager: unauthenticate
succeeded for CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.442] WUOLService:ReadRefreshTime: Logging is as adminfalse
[9/14/07 15:19:19.443] WUOLService:ReadRefreshTime: the getScope returned0
[9/14/07 15:19:19.443] WUOLService:ReadRefreshTime: Authenticate AS
code dn CN=WOL Service_<myServer>.OU=<myOU>.O=<myO> Tree<myTree>
[9/14/07 15:19:19.443] WUOLService:ReadRefreshTime: Authenticating as
CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.443] WUOLService:ReadRefreshTime: NDAPAuthUtilities:
getID: Trial: 0
[9/14/07 15:19:19.461] WUOLService:ReadRefreshTime: NDAPAuthUtilities:
getID: return value= 0
[9/14/07 15:19:19.461] WUOLService:ReadRefreshTime: getID returned value0
[9/14/07 15:19:19.461] WUOLService:ReadRefreshTime: the syncString.str
name isCN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.461] WUOLService:ReadRefreshTime: authenticate as
returns istrue
[9/14/07 15:19:19.461] WUOLService:ReadRefreshTime: NDAPAuthUtilities:
createInitialContext: Getting initial context: ndsTree: <myTree>,
objectDN: CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.461] WUOLService:ReadRefreshTime: NDAPAuthUtilities:
createInitialContext: Trial: 0
[9/14/07 15:19:19.461] WUOLService:ReadRefreshTime: NDAPAuthUtilities:
createInitialContext: Creating initial context on ndsTree + objectDN
[9/14/07 15:19:19.465] WUOLService:ReadRefreshTime: Getting
refreshschedule Attributes
[9/14/07 15:19:19.466] WUOLService:ReadRefreshTime: NDAPAuthUtilities:
reLookUp: look up for CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>,
handle.baseDN: CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.466] WUOLService:ReadRefreshTime: getAttributesofDN:
Attributes of:
[9/14/07 15:19:19.467] WUOLService:ReadRefreshTime: NDAPAuthUtilities:
getAttributesOfDN: Trial: 0
[9/14/07 15:19:19.479] WUOLService:ReadRefreshTime:
getAttributes:Attributes={zendmwolrefreshschedule= zendmWolRefreshSchedule:
[9/14/07 15:19:19.479] WUOLService:ReadRefreshTime: The
getAttributesofDn
returned{zendmwolrefreshschedule=zendmWolRefreshSc hedule:
[9/14/07 15:19:19.479] WUOLService:ReadRefreshTime: The ndsSyntaxId is 9
[9/14/07 15:19:19.479] WUOLService:ReadRefreshTime: The base class is
com.novell.service.nds.naming.net.NetAttribute
[9/14/07 15:19:19.479] WUOLService:ReadRefreshTime: the attribute
addeed is
com.novell.zenworks.desktop.inventory.zencommon.Di rectoryAttribute@1df280b
for zendmWolRefreshSchedule
[9/14/07 15:19:19.480] WUOLService:ReadRefreshTime: Got the Attributes
[9/14/07 15:19:19.481] WOLService:ServiceManager: Logout in
NDAPAuthUtilities the syncString.str isCN=WOL
Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.481] WOLService:ServiceManager: Authenticating out as
CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.481] WOLService:ServiceManager: NDAPAuthUtilities:
clearID: Trial: 0
[9/14/07 15:19:19.481] WOLService:ServiceManager: logout tries:0
[9/14/07 15:19:19.483] WOLService:ServiceManager: After notifying
[9/14/07 15:19:19.484] WOLService:ServiceManager: Logout from NDS
returnedtrue
[9/14/07 15:19:19.484] WOLService:ServiceManager: unauthenticate
succeeded for CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.484] WOLService:ServiceManager: schedule V is not empty
[9/14/07 15:19:19.516] WOLService:ServiceManager: Logging is as adminfalse
[9/14/07 15:19:19.516] WOLService:ServiceManager: the getScope returned0
[9/14/07 15:19:19.516] WOLService:ServiceManager: Authenticate AS code
dn CN=WOL Service_<myServer>.OU=<myOU>.O=<myO> Tree<myTree>
[9/14/07 15:19:19.516] WOLService:ServiceManager: Authenticating as
CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.516] WOLService:ServiceManager: NDAPAuthUtilities:
getID: Trial: 0
[9/14/07 15:19:19.534] WOLService:ServiceManager: NDAPAuthUtilities:
getID: return value= 0
[9/14/07 15:19:19.534] WOLService:ServiceManager: getID returned value0
[9/14/07 15:19:19.535] WOLService:ServiceManager: the syncString.str
name isCN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.535] WOLService:ServiceManager: authenticate as
returns istrue
[9/14/07 15:19:19.537] WOLService:ServiceManager: NDAPAuthUtilities:
createInitialContext: Getting initial context: ndsTree: <myTree>,
objectDN: CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.537] WOLService:ServiceManager: NDAPAuthUtilities:
createInitialContext: Trial: 0
[9/14/07 15:19:19.537] WOLService:ServiceManager: NDAPAuthUtilities:
createInitialContext: Creating initial context on ndsTree + objectDN
[9/14/07 15:19:19.543] WOLService:ServiceManager: NDAPAuthUtilities:
reLookUp: look up for CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>,
handle.baseDN: CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.543] WOLService:ServiceManager: NDAPAuthUtilities:
modifyAttributes: Trial: 0
[9/14/07 15:19:19.543] WOLService:ServiceManager: modify
DirContext:CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.560] WOLService:ServiceManager: Modify attributestrue
[9/14/07 15:19:19.560] WOLService:ServiceManager: Logout in
NDAPAuthUtilities the syncString.str isCN=WOL
Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.562] WOLService:ServiceManager: Authenticating out as
CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.562] WOLService:ServiceManager: NDAPAuthUtilities:
clearID: Trial: 0
[9/14/07 15:19:19.562] WOLService:ServiceManager: logout tries:0
[9/14/07 15:19:19.567] WOLService:ServiceManager: After notifying
[9/14/07 15:19:19.567] WOLService:ServiceManager: Logout from NDS
returnedtrue
[9/14/07 15:19:19.567] WOLService:ServiceManager: unauthenticate
succeeded for CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 15:19:19.568] WOLService:ServiceManager: Wake on Lan service
started successfully
[9/14/07 15:19:19.568] Service Manager: Service 'WOL Service', started
successfully
[9/14/07 15:19:19.568] Service Manager: Successfully autoloaded service,
WOL Service
[9/14/07 15:19:19.568] Service Manager (TCP): 'WOLServiceManager' is ready
[9/14/07 15:22:30.089] WOLService:ServiceManager: Refreshtimecallback ::
Schedule fired :: Reading Policy
[9/14/07 15:22:30.093] WUOLService:ReadPolicy: Reading Policy...
[9/14/07 15:22:30.094] WUOLService:ReadPolicy: Get policy called with dn
= CN=<myServer>.OU=<myOU>.O=<myO> orFlags =1073741824 dominateFlag =
1073741824 policy type =zenpolServerType policy Value = zendmWakeUpPolicy
[9/14/07 15:22:30.352] WUOLService:ReadPolicy: The number of
effectivePolicies: 1
[9/14/07 15:22:30.352] WUOLService:ReadPolicy: the policy dn is
CN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:30.352] WUOLService:ReadPolicy: Found policy :: getting
attributes ...
[9/14/07 15:22:30.353] WUOLService:ReadPolicy: Logging is as adminfalse
[9/14/07 15:22:30.353] WUOLService:ReadPolicy: the getScope returned0
[9/14/07 15:22:30.353] WUOLService:ReadPolicy: Authenticate AS code dn
CN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO> Tree<myTree>
[9/14/07 15:22:30.353] WUOLService:ReadPolicy: Authenticating as
CN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:30.353] WUOLService:ReadPolicy: NDAPAuthUtilities: getID:
Trial: 0
[9/14/07 15:22:30.371] WUOLService:ReadPolicy: NDAPAuthUtilities: getID:
return value= 0
[9/14/07 15:22:30.371] WUOLService:ReadPolicy: getID returned value0
[9/14/07 15:22:30.371] WUOLService:ReadPolicy: the syncString.str name
isCN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:30.371] WUOLService:ReadPolicy: authenticate as returns
istrue
[9/14/07 15:22:30.371] WUOLService:ReadPolicy: NDAPAuthUtilities:
createInitialContext: Getting initial context: ndsTree: <myTree>,
objectDN: CN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:30.371] WUOLService:ReadPolicy: NDAPAuthUtilities:
createInitialContext: Trial: 0
[9/14/07 15:22:30.371] WUOLService:ReadPolicy: NDAPAuthUtilities:
createInitialContext: Creating initial context on ndsTree + objectDN
[9/14/07 15:22:30.375] WUOLService:ReadPolicy: NDAPAuthUtilities:
reLookUp: look up for CN=Server
Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>, handle.baseDN:
CN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:30.375] WUOLService:ReadPolicy: getAttributesofDN:
Attributes of:
[9/14/07 15:22:30.375] WUOLService:ReadPolicy: NDAPAuthUtilities:
getAttributesOfDN: Trial: 0
[9/14/07 15:22:30.389] WUOLService:ReadPolicy:
getAttributes:Attributes={zenpolscheduledpolicy=ze npolScheduledPolicy:
zendmwoltargetlist=zendmWolTargetList: Distinguished Name
CN=WKS001279ADF0E6|00:12:79:AD:F0:E6.OU=Workstatio ns_ZFD7.OU=Utility.O=<myO>}
[9/14/07 15:22:30.389] WUOLService:ReadPolicy: The getAttributesofDn
returned{zenpolscheduledpolicy=zenpolScheduledPoli cy:
zendmwoltargetlist=zendmWolTargetList: Distinguished Name
CN=WKS001279ADF0E6|00:12:79:AD:F0:E6.OU=Workstatio ns_ZFD7.OU=Utility.O=<myO>}
[9/14/07 15:22:30.389] WUOLService:ReadPolicy: The ndsSyntaxId is 1
[9/14/07 15:22:30.389] WUOLService:ReadPolicy: The base class is
com.novell.service.nds.naming.net.NetAttribute
[9/14/07 15:22:30.389] WUOLService:ReadPolicy: the attribute addeed is
com.novell.zenworks.desktop.inventory.zencommon.Di rectoryAttribute@176e552
for zendmWolTargetList
[9/14/07 15:22:30.389] WUOLService:ReadPolicy: The ndsSyntaxId is 9
[9/14/07 15:22:30.389] WUOLService:ReadPolicy: The base class is
com.novell.service.nds.naming.net.NetAttribute
[9/14/07 15:22:30.389] WUOLService:ReadPolicy: the attribute addeed is
com.novell.zenworks.desktop.inventory.zencommon.Di rectoryAttribute@c980c9
for zenpolScheduledPolicy
[9/14/07 15:22:30.389] WUOLService:ReadPolicy: Logout in
NDAPAuthUtilities the syncString.str isCN=Server
Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:30.389] WUOLService:ReadPolicy: Authenticating out as
CN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:30.390] WUOLService:ReadPolicy: NDAPAuthUtilities:
clearID: Trial: 0
[9/14/07 15:22:30.390] WUOLService:ReadPolicy: logout tries:0
[9/14/07 15:22:30.392] WUOLService:ReadPolicy: After notifying
[9/14/07 15:22:30.392] WUOLService:ReadPolicy: Logout from NDS returnedtrue
[9/14/07 15:22:30.392] WUOLService:ReadPolicy: unauthenticate succeeded
for CN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:30.393] WOLService:ServiceManager: This SCHEDULE is added
to the current list
[9/14/07 15:22:30.394] WOLService:ServiceManager: Schedule Fired ::
ExploreDS :: Going to read target list attributes
[9/14/07 15:22:30.398] DefaultThreadPool: Creating Thread- {Thread Count
: 0, TimerInterval : 1991}
[9/14/07 15:22:30.399] DefaultThreadPool: Starting thread : WUOL Service
Thread-T0
[9/14/07 15:22:30.405] WUOLService:ExploreDS: RUN CALLED in Explore DS
target_list.size():1
[9/14/07 15:22:30.405] WUOLService:ExploreDS: Logging is as adminfalse
[9/14/07 15:22:30.405] WUOLService:ExploreDS: the getScope returned0
[9/14/07 15:22:30.405] WUOLService:ExploreDS: Authenticate AS code dn
CN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO> Tree<myTree>
[9/14/07 15:22:30.405] WUOLService:ExploreDS: Authenticating as
CN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:30.405] WUOLService:ExploreDS: NDAPAuthUtilities: getID:
Trial: 0
[9/14/07 15:22:30.428] WUOLService:ExploreDS: NDAPAuthUtilities: getID:
return value= 0
[9/14/07 15:22:30.428] WUOLService:ExploreDS: getID returned value0
[9/14/07 15:22:30.428] WUOLService:ExploreDS: the syncString.str name
isCN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:30.428] WUOLService:ExploreDS: authenticate as returns istrue
[9/14/07 15:22:30.428] WUOLService:ExploreDS: NDAPAuthUtilities:
createInitialContext: Getting initial context: ndsTree: <myTree>,
objectDN:
CN=WKS001279ADF0E6|00:12:79:AD:F0:E6.OU=Workstatio ns_ZFD7.OU=Utility.O=<myO>
[9/14/07 15:22:30.428] WUOLService:ExploreDS: NDAPAuthUtilities:
createInitialContext: Trial: 0
[9/14/07 15:22:30.428] WUOLService:ExploreDS: NDAPAuthUtilities:
createInitialContext: Creating initial context on ndsTree + objectDN
[9/14/07 15:22:30.433] WUOLService:ExploreDS: ExploreDS:: auth done
[9/14/07 15:22:30.433] WUOLService:ExploreDS: Explore called for DS::
[9/14/07 15:22:30.434] WUOLService:ExploreDS: Search called inside
explore for DS::
[9/14/07 15:22:30.434] WUOLService:ExploreDS: Search:: inside
[9/14/07 15:22:30.434] WUOLService:ExploreDS: NDAPAuthUtilities: search:
Trial: 0
[9/14/07 15:22:30.434] WUOLService:ExploreDS: NDAPAuthUtilities: search:
DirContext:CN=WKS001279ADF0E6|00:12:79:AD:F0:E6.OU =Workstations_ZFD7.OU=Utility.O=<myO>
[9/14/07 15:22:30.434] WUOLService:ExploreDS: NDAPAuthUtilities: search:
Base DN = , filter = (|(Object Class=Workstation)(Object
Class=zenWorkstationGroup))
[9/14/07 15:22:34.753] WUOLService:ExploreDS: The ndsSyntaxId is 3
[9/14/07 15:22:34.753] WUOLService:ExploreDS: The base class is
com.novell.service.nds.naming.net.NetAttribute
[9/14/07 15:22:34.753] WUOLService:ExploreDS: The ndsSyntaxId is 20
[9/14/07 15:22:34.753] WUOLService:ExploreDS: The base class is
com.novell.service.nds.naming.net.NetAttribute
[9/14/07 15:22:34.753] WUOLService:ExploreDS: The ndsSyntaxId is 3
[9/14/07 15:22:34.753] WUOLService:ExploreDS: The base class is
com.novell.service.nds.naming.net.NetAttribute
[9/14/07 15:22:34.753] WUOLService:ExploreDS: The ndsSyntaxId is 3
[9/14/07 15:22:34.754] WUOLService:ExploreDS: The base class is
com.novell.service.nds.naming.net.NetAttribute
[9/14/07 15:22:34.755] WUOLService:ExploreDS: The ndsSyntaxId is 3
[9/14/07 15:22:34.755] WUOLService:ExploreDS: The base class is
com.novell.service.nds.naming.net.NetAttribute
[9/14/07 15:22:34.755] WUOLService:ExploreDS: NDAPAuthUtilities: search:
returning...
[9/14/07 15:22:34.755] WUOLService:ExploreDS: Search:: inside Done
[9/14/07 15:22:34.755] WUOLService:ExploreDS: Search:: inside
ret_vect.size() is 1
[9/14/07 15:22:34.756] WUOLService:ExploreDS: search:: inside getAtt called
[9/14/07 15:22:34.758] WUOLService:ExploreDS: Search:: getAtt:: inside
called:: ret.directoryAttributes.size() is 5
[9/14/07 15:22:34.759] WUOLService:ExploreDS: Search:: getAtt::
1:wmachine.wsDN is
CN=WKS001279ADF0E6|00:12:79:AD:F0:E6.OU=Workstatio ns_ZFD7.OU=Utility.O=<myO>
[9/14/07 15:22:34.759] WUOLService:ExploreDS: getatt:: Attribute id is
WM:Network Address
[9/14/07 15:22:34.759] WUOLService:ExploreDS: Inside getatt ::
num_values is 1
[9/14/07 15:22:34.759] WUOLService:ExploreDS: getatt:: values.element at
j is <myWorkstationIP>
[9/14/07 15:22:34.760] WUOLService:ExploreDS: getatt:: 1st elseif
[9/14/07 15:22:34.760] WUOLService:ExploreDS: Search:: getAtt::
1:wmachine.wsDN is
CN=WKS001279ADF0E6|00:12:79:AD:F0:E6.OU=Workstatio ns_ZFD7.OU=Utility.O=<myO>
[9/14/07 15:22:34.760] WUOLService:ExploreDS: getatt:: Attribute id is
Object Class
[9/14/07 15:22:34.760] WUOLService:ExploreDS: Inside getatt ::
num_values is 4
[9/14/07 15:22:34.760] WUOLService:ExploreDS: getatt:: values.element at
j is Class Name Workstation
[9/14/07 15:22:34.760] WUOLService:ExploreDS: getatt:: values.element at
j is Class Name Computer
[9/14/07 15:22:34.760] WUOLService:ExploreDS: getatt:: values.element at
j is Class Name Device
[9/14/07 15:22:34.760] WUOLService:ExploreDS: getatt:: values.element at
j is Class Name Top
[9/14/07 15:22:34.760] WUOLService:ExploreDS: Search:: getAtt::
1:wmachine.wsDN is
CN=WKS001279ADF0E6|00:12:79:AD:F0:E6.OU=Workstatio ns_ZFD7.OU=Utility.O=<myO>
[9/14/07 15:22:34.760] WUOLService:ExploreDS: getatt:: Attribute id is
zenwmSubnetMask
[9/14/07 15:22:34.760] WUOLService:ExploreDS: Inside getatt ::
num_values is 1
[9/14/07 15:22:34.760] WUOLService:ExploreDS: getatt:: values.element at
j is 255.255.255.0
[9/14/07 15:22:34.760] WUOLService:ExploreDS: getatt:: 3rd elseif
[9/14/07 15:22:34.763] WUOLService:ExploreDS: Search:: getAtt::
1:wmachine.wsDN is
CN=WKS001279ADF0E6|00:12:79:AD:F0:E6.OU=Workstatio ns_ZFD7.OU=Utility.O=<myO>
[9/14/07 15:22:34.763] WUOLService:ExploreDS: getatt:: Attribute id is
ZEN:INV SubNet Address
[9/14/07 15:22:34.763] WUOLService:ExploreDS: Inside getatt ::
num_values is 1
[9/14/07 15:22:34.764] WUOLService:ExploreDS: getatt:: values.element at
j is [255.255.255.240]
[9/14/07 15:22:34.764] WUOLService:ExploreDS: Search:: getAtt::
1:wmachine.wsDN is
CN=WKS001279ADF0E6|00:12:79:AD:F0:E6.OU=Workstatio ns_ZFD7.OU=Utility.O=<myO>
[9/14/07 15:22:34.764] WUOLService:ExploreDS: getatt:: Attribute id is
zenwmMACAddress
[9/14/07 15:22:34.764] WUOLService:ExploreDS: Inside getatt ::
num_values is 1
[9/14/07 15:22:34.764] WUOLService:ExploreDS: getatt:: values.element at
j is 00:12:79:AD:F0:E6
[9/14/07 15:22:34.764] WUOLService:ExploreDS: getatt:: 2nd elseif
[9/14/07 15:22:34.764] WUOLService:ExploreDS: search:: inside getAtt
call done
[9/14/07 15:22:34.764] WUOLService:ExploreDS: Search:: outside
[9/14/07 15:22:34.764] WUOLService:ExploreDS: Search call finished
inside explore for DS::
[9/14/07 15:22:34.764] WUOLService:ExploreDS: Explore call ends for DS::
[9/14/07 15:22:34.764] WUOLService:ExploreDS: ExploreDS:: explore done
[9/14/07 15:22:34.764] WUOLService:ExploreDS: ExploreDS:: unauth start
[9/14/07 15:22:34.764] WUOLService:ExploreDS: Logout in
NDAPAuthUtilities the syncString.str isCN=Server
Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:34.764] WUOLService:ExploreDS: Authenticating out as
CN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:34.764] WUOLService:ExploreDS: NDAPAuthUtilities:
clearID: Trial: 0
[9/14/07 15:22:34.764] WUOLService:ExploreDS: logout tries:0
[9/14/07 15:22:34.768] WUOLService:ExploreDS: After notifying
[9/14/07 15:22:34.768] WUOLService:ExploreDS: Logout from NDS returnedtrue
[9/14/07 15:22:34.768] WUOLService:ExploreDS: unauthenticate succeeded
for CN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:34.768] WUOLService:ExploreDS: ExploreDS:: unauth done
[9/14/07 15:22:34.768] WOLService:ServiceManager: WUOLService element read
[9/14/07 15:22:34.772] DefaultThreadPool: Creating Thread- {Thread Count
: 1, TimerInterval : 2036}
[9/14/07 15:22:34.773] WUOLService:ExploreDS: ExploreDS:: in final block
unauth doing
[9/14/07 15:22:34.773] WUOLService:ExploreDS: Logout in
NDAPAuthUtilities the syncString.str isnull
[9/14/07 15:22:34.773] WUOLService:ExploreDS: Logout from NDS returnedtrue
[9/14/07 15:22:34.773] WUOLService:ExploreDS: unauthenticate succeeded
for CN=Server Package_<myServer>:WOLTesting.OU=<myOU>.O=<myO>
[9/14/07 15:22:34.773] WUOLService:ExploreDS: ExploreDS:: in final block
unauth done
[9/14/07 15:22:34.773] DefaultThreadPool: Starting thread : WUOL Service
Thread-T1
[9/14/07 15:22:34.786] WOLService:ServiceManager: <myWorkstationIP>
001279ADF0E6 Packet sent to remote machine.
[9/14/07 15:25:00.001] WOLService:ServiceManager: One of the schedules
expired
[9/14/07 15:25:00.001] WOLService:ServiceManager: Policy Refresh
Schedule has expired.
[9/14/07 15:26:35.699] WOLService:ServiceManager: <myWorkstationIP>
001279ADF0E6 Remote Machine not responding.
[9/14/07 16:47:24.587] Service Manager (TCP):
ServiceManagerServer.stopAllServices called
[9/14/07 16:47:24.588] Service Manager (TCP): ServiceManagerServer.close
called
[9/14/07 16:47:24.588] Service Manager (TCP):
ServiceManagerServerInfo.deleteInfo called
[9/14/07 16:47:24.589] Service Manager (TCP): ServiceManagerServerInfo:
getSerDirectory: prop_file_url =
file:/vol1:/ZENworks/RemMgmt/Server/properties/TracerFilter.properties
[9/14/07 16:47:24.589] Service Manager (TCP): Returning
"\vol1:\ZENworks\RemMgmt\Server\properties" as the directory for the
serialized file.
[9/14/07 16:47:24.589] Service Manager (TCP): Returning this as the
directory to store the file: \vol1:\ZENworks\RemMgmt\Server\properties
[9/14/07 16:47:24.590] Service Manager: Terminating service manager
[9/14/07 16:47:24.590] Service Manager: Terminating service manager
[9/14/07 16:47:24.590] Service Manager: Stopping 'WOL Service'
[9/14/07 16:47:24.595] Service Manager: Stopping Service WOL Service
[9/14/07 16:47:24.595] WOLService:ServiceManager: Stopping the Wake on
Lan service ...
[9/14/07 16:47:24.596] WOLService:ServiceManager: Schedule being removed
[9/14/07 16:47:24.596] WOLService:ServiceManager: Logging is as adminfalse
[9/14/07 16:47:24.596] WOLService:ServiceManager: the getScope returned0
[9/14/07 16:47:24.596] WOLService:ServiceManager: Authenticate AS code
dn CN=WOL Service_<myServer>.OU=<myOU>.O=<myO> Tree<myTree>
[9/14/07 16:47:24.596] WOLService:ServiceManager: Authenticating as
CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 16:47:24.596] WOLService:ServiceManager: NDAPAuthUtilities:
getID: Trial: 0
[9/14/07 16:47:24.617] WOLService:ServiceManager: NDAPAuthUtilities:
getID: return value= 0
[9/14/07 16:47:24.617] WOLService:ServiceManager: getID returned value0
[9/14/07 16:47:24.617] WOLService:ServiceManager: the syncString.str
name isCN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 16:47:24.617] WOLService:ServiceManager: authenticate as
returns istrue
[9/14/07 16:47:24.617] WOLService:ServiceManager: NDAPAuthUtilities:
createInitialContext: Getting initial context: ndsTree: <myTree>,
objectDN: CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 16:47:24.617] WOLService:ServiceManager: NDAPAuthUtilities:
createInitialContext: Trial: 0
[9/14/07 16:47:24.617] WOLService:ServiceManager: NDAPAuthUtilities:
createInitialContext: Creating initial context on ndsTree + objectDN
[9/14/07 16:47:24.621] WOLService:ServiceManager: NDAPAuthUtilities:
reLookUp: look up for CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>,
handle.baseDN: CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 16:47:24.621] WOLService:ServiceManager: NDAPAuthUtilities:
modifyAttributes: Trial: 0
[9/14/07 16:47:24.621] WOLService:ServiceManager: modify
DirContext:CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 16:47:24.633] WOLService:ServiceManager: Modify attributestrue
[9/14/07 16:47:24.633] WOLService:ServiceManager: Logout in
NDAPAuthUtilities the syncString.str isCN=WOL
Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 16:47:24.633] WOLService:ServiceManager: Authenticating out as
CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 16:47:24.633] WOLService:ServiceManager: NDAPAuthUtilities:
clearID: Trial: 0
[9/14/07 16:47:24.633] WOLService:ServiceManager: logout tries:0
[9/14/07 16:47:24.635] WOLService:ServiceManager: After notifying
[9/14/07 16:47:24.635] WOLService:ServiceManager: Logout from NDS
returnedtrue
[9/14/07 16:47:24.635] WOLService:ServiceManager: unauthenticate
succeeded for CN=WOL Service_<myServer>.OU=<myOU>.O=<myO>
[9/14/07 16:47:24.636] WOLService:ServiceManager: Wake on Lan service
stopped successfully
[9/14/07 16:47:24.636] Service Manager: Service WOL Service stopped
successfully
[9/14/07 16:47:24.636] Service Manager: 'WOL Service', stopped successfully
[9/14/07 16:47:24.636] Service Manager (TCP): ServiceManagerServer has
exited successfully
[9/14/07 16:47:24.641] Service Manager (TCP): finalize of
ServiceManagerServer called
[9/14/07 16:47:24.641] Service Manager (TCP): ServiceManagerServer.close
called

[solved] Cannot activate wake on lan with systemd

I have activated successfully wake on lan with systemd, following these guidelines :
https://wiki.archlinux.org/index.php/Wol#With_systemd
My [email protected] is:
[Unit]
Description=Wake-on-LAN for %i
Requires=network.target
After=network.target
[Service]
ExecStart=/usr/bin/ethtool -s %i wol g
Type=oneshot
[Install]
WantedBy=multi-user.target
It worked nicely until I recently had to reinstall my server (following a disk replacement). Since then systemd fails to activate wake on lan.
Output from systemctl status wol@enp0s4 :
● [email protected] - Wake-on-LAN for enp0s4
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: inactive (dead) since ven. 2014-07-25 11:21:28 CEST; 23min ago
Process: 181 ExecStart=/usr/bin/ethtool -s %i wol g (code=exited, status=0/SUCCESS)
Main PID: 181 (code=exited, status=0/SUCCESS)
Output from ethtool enp0s4|grep "Wake" :
Supports Wake-on: pg
Wake-on: d
If I explicitly start the service with systemctl start wol@enp0s4, then ethtool enp0s4|grep "Wake" shows:
Supports Wake-on: pg
Wake-on: g
My guess is that the service does not start at the correct timing at boot.
I have also tried wol-systemd package from the AUR without success.
Last edited by elb (2014-07-25 15:02:21)

After a fiew tries and reading docs, I found that replacing network.target with multi-user.target in [email protected] seems to work for me.

WRT160Nv3 Wake On Lan Forwarding Issue

Hello,
I want to set up WOL on my desktop. Currently I have port 3389 forwarding on my router already to my desktops static IP so I can use remote desktop. This is seen on canyouseeme.org.
Now I am trying to forwarding the port 7 (UDP) to the same static IP so I can also use Wake On Lan. canyouseeme.org times out when trying to hit this port. In actuality I have tried about 10 different port numbers, all with the same result.
I am looking for some trouble shooting steps here, since one port is forwarding fine yet when I want to forward another it doesn't work.
Relevant Information:
OS: Windows 7 64-bit
Static IP? Yes
Router Firmware: v3.0.03
Thanks for any help,
-Nick

I'm not 100% sure if WOL is fully supported by the router but you should make sure that you have used DHCP Reservation to set a "static IP" and that your computer's firewall also allows udp port 7.
I don't work for Cisco. I'm just here to help.

Wake on Lan issue solved easily !

Similar Messages

Maybe you are looking for