Macintoshes on heterogeneous networks - wake on lan
Hi All,
I've been setting up a couple of Macintosh labs this summer, using Intel based iMacs running Mac OS 10.5 (Leopard). I've purchased Apple Remote Desktop to allow me to manage all the Macs from my office. The one problem I've run into that I can't fix is waking up the Macs across our network after they've gone to sleep. Our (Windows-based) DHCP server sees the Macs go to sleep and then disconnects them from the network; so my directed broadcast WOL (Wake on LAN) packets fall in the bit bucket. Our computer center folks say there's a fix for this, but they won't do it because they claim it opens up our entire network to a distributed denial of service attack. My workaround is to never let the Macs go to sleep - which I hate because when idle they draw 48W of power each, and when asleep only 2.4W.
Anyone out there have a heterogeneous network that allows Macs to safely sleep?
thanks,
john
hehe, yeah I've been through this and feel your frustrations. Grrrrrrrrrrrrrrr
Here is your answer!!!
Control Panel>System>Hardware>Device Manager>Network Adapter>>> Select the netowrk adapter, right click and select Properties. Select the Advanced tab and then go down the list and look for "Wake on Settings">on the right select disable.
It should not "Turn On' randomly now.
Cheers,
Michael
Similar Messages
-
TimeMachine to G4 via Network - Wake on LAN , Standby, Sleep
Hello,
I want to backup to a G4 running 10.4.11, wich is capable of Wake on LAN.
How may I make Time Machine automatically wake up the G4? Right now I am using
http://www.readpixel.com/wakeonlan/index.html
manually.
Bye
JasonAll,
I have a g4 MDD that I have set up to Wake on LAN. I
have another computer (ibook) setup to send the Wake
on LAN magic packet. This works fine and the MDD
awakens from sleep after sending the packet.
However, in about 10 or 15 seconds the MDD goes back
to sleep again. Why??
Thanks,
-BL
More background info:
Rather than sending the WOL packet over the network, I walked up to the sleeping MDD and hit the spacebar. It awoke, then went back to sleep about 15-30 seconds later. I hit the spacebar a second time and then started to use the computer (Logged in, checked a few sites in Safari, etc) and the computer remained awake.
So I guess my more directed question is: why does the MDD go back to sleep when there is no input/usage?
Thanks again,
-BL -
Hy ,
My mac pro (SL 10.6.8) wakes up every minutes when I use wake on lan and I share one of my Hard Drive.
When I unplug the ethernet cable it doesn't wake any more so I suppose that some thing wakes it up on my network ( 1 printer canon MP620, 2 mac books, 2 iPads, 2 IPhones and 2 time capsules !) ...even when all these devices are "sleeping"
Any idea?
THKS
Phil
PS .: I'm french so my english is probably quite strange ! ... Sorry for thatSorry - posted this in the wrong forum. Reposted in Mac Pro.
-
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. -
HP Color LaserJet CM1312nfi MFP Mystery Wake on LAN
The printer wakes unexpectedly, and unpredictably on the network. I cannot determine what, if anything, is waking it. The printer wakes and goes into calibration without any users on the network and without any print jobs. Mystery wake on LAN.
The HP drivers won't load on my 10.10.x (10.10.1 thru 10.10.4) OSX macbook pro. The install says the version of OSX isn't supported even thought I've tried 1.5.0 dmg file which is for 10.7 and greater. I did the math and I believe 10.10.x is greater than any version of 10.7. I also tried HP Easy Scan and it doesn't even see my scanner. Printing works fine, but I scan a lot of paper. Also, I've found that the Mac OSX version of the HP software (when it still worked) creates obscenely large PDF files. I can get around this by opening Adobe Acrobat Pro and re-saving the file as a reduced file size with the same name. I can take a 25 MB file HP creates and get it down to about 300KB or so. I found a way around all this but you won't like it. I've loaded Parallels (installed windows 7 ultimate 64 bit) and installed the windows client in my parallels image. The windows client works fine. Not a solution I prefer, but this is an HP issue not an apple issue .... HP hasn't put out a driver for this printer in the better part of 3.5 years. Lastly, I'm not hooking up a USB cable to my printer/fax/scanner .... what's the point of having a dhcp network capable printer if I have to hard wire to a PC? I've used HP printers since the mid-'90s, but I guess it's time to find a company that supports OSX.
-
Is there a way to get Zenwork's wake-on-lan feature to work across subnets?
I am not a LAN administrator so pardon any ignorance you see in my
question.
Zenwork's wake-on-lan function won't work on our LAN because our switches
are set to not allow forwarding of subnet-oriented broadcasts, which is a
generic requirment for zenworks wake-on-lan function to work. Our security
folks say enabling this on the switches is not an option because it
introduce a security vulnerbility. I find it strange that there wouldn't
be a solution for this by Novell/Zenworks considering that multiple
subnets, switches, and security considerations are usually a component of
all networks which zenworks is specifically targeted for in the first
place.
ThanksOriginally Posted by Marcus Breiden
On Thu, 07 Sep 2006 22:52:59 GMT, [email protected] wrote:
[color=blue]
it is the only way though.. that's how any WOL software works.. they can
limit the packets comming from either your c1 wks or the zenworks server
though.. otherwise you would require one server per subnet
Marcus Breiden
If you are asked to email me information please change -- to - in my e-mail
address.
The content of this mail is my private and personal opinion.
Edu-Magic.net, deceased
Exactly, and this is the best choice. Make "Replication Servers" in each subnet, is very simple. U can use a Windows machine or SuSE, both without installing zenworks. Only registering them as servers satellites. You must install the agent (logically, hehe). -
I just purchased the MSI K7N2G-L/NFORCE2 board. I noticed it said it had WOR(wake on ring), but I didn't see a WOL (wake on lan). Is it possible to hook this up?
i have not tried it but the option is listed in win xp's device manager. double click the nvidia network controller listing. goto -advanced- click on -wake on lan from power off- check to see if its enabled or not. i think its enabled by default. hope this helps.
-
Would like to request the following changes (could make it more easy to support WOL):
/etc/config.d/wol:
# Comment out the following line to support Wake On LAN
WOL_ARGS="-i"
/etc/rc.shutdown (or wherever there's a reference to 'halt -i' or similar):
. /etc/conf.d/wol
/sbin/poweroff -d -f -h $WOL_ARGS
/sbin/reboot -d -f $WOL_ARGS
[Edit]
/etc/rc.d/network:
. /etc/conf.d/wol
if [ -n $WOL_ARGS ]; then
/sbin/ifconfig ${1} down >/dev/null 2>&1
fi
Thoughts?
Thanks
Last edited by soloport (2008-07-30 06:31:03)You should submit a feature request for this on the bugtracker. Here in the forum, there is no guarantee that the right devs, or any devs, will see it.
-
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 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) -
Can I use Wake-On-LAN with P1606dn Printer?
I have a P1606dn laser printer which is remotely located and the power is remotely switched.
When it is first powered up, the button on the front has to be pressed to cajole the printer into life . It lights up green and we are good to go. After this, even if it has dropped into power saving mode, sending a print commnad wakes it up and network printing works fine.
However, I want to do away with the walk to press the button when it is first powered up. I've tried using a Wake-On-LAN command to the IP and MAC addess of the printer, but nothing happens.
I realise I could leave it permananetly powered but don't want to do this because there are other devices on the same supply that need to be turned off at night.
How can I get it to wake up remotely?
many thanks.
This question was solved.
View Solution.Whenever power is first applied to the P1606dn, that has been in a no-power state, the unit is turned Off. The unit's power light may be on, but the unit itself is off. Whenever you press the button, then the unit goes through the power up and obtains the IP address to function.
Hope this helps.
-------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------
I am not an HP employee. -
How to enable Wake On Lan on MSi P45 Neo2?
Hi,
I just bought a P45 Neo2, and I think I have WOL on this machine, as the Realtek chipset 8111C does support the feature. However, I'm not sure how to
- enable
- use
the function. Can you help me?
Under Device Manager, I go to the Realtek network adapter --> Properties --> Power Management --> Allow this device to bring the computer out of standby.
Now, it is enabled. How should I use it? I would be very thankful :-).Please have a look here first for basic introduction to Wake on LAN and "Magic Packets":
http://en.wikipedia.org/wiki/Wake-on-LAN#How_it_works -
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. -
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 -
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
Maybe you are looking for
-
Sharing an iTunes Library w/Multiple iPods/Computers
I'm sure there is a tutorial somewhere that tells you how to do this...but I cant seem to find one. I'm trying to find out how to share one iTunes library that is on my mac with another computer on my network (a laptop PC). I have 2 ipods as well, an
-
Mini display to s-video adapter wont work in windows xp
I have a Macbook 1.1 and can not get my mini display adapter to work in windows xp, it flashes a black screen really fast like it is trying but no picture.... i am running xp with service pack 3 and all updates are current, any suggestions would be g
-
I recently formatted my hard drive so that I could give my computer to my brother but when I was trying to reinstall OS X Lion (10.7) the only option that showed up was to reinstall OS X mountain lion which I do not have, so now I can't get past the
-
IPod Battery Problems.. Send in for a replacement?
My iPod is just over a month and a half old. I use it very often. The battery lately takes about 12 to 14 hours to fully charge. Once I get a full charge into the battery, the battery lasts about 10mins, even though I don't play games or scroll alot.
-
Filter failed message from printer
I get the filter failed message from printer - an Epsom 387. It has worked wirelessly for over a year - today it will not.