Wake on LAN across subnets
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.
Thanks
Originally 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).
Similar Messages
-
SG200 how to configure Wake on LAN across subnets
How can I configure to support WOL on a SG200 (8 Ports) to support Wake On Lan (Magic Packets) from a different IP Subnet or other SG200 Switch. It seems not to support Directed-Broadcasts.
I checked out the link and tested the changes. Unfortunately, the WOL still won't work. In the link you attached, it states that you cannot turn on a computer that is off. Does that mean one that is off such as unplugged or in shutdown? Also, one of the steps to configure the firewall access rules says to block all outbound connections for all services. That doesn't make any sense to me, but I might be wrong. I also noticed that the link was for another router. I don't know if that makes a difference. I also read somewhere in the forums that someone else is having a similar problem, saying that Port Forwarding still isn't working in the latest firmware. This whole problem is strange because it used to work all the time on my old router with Port Forwarding, but on this one it won't work at all.
Sent from Cisco Technical Support iPad App -
When setting up WOL across a Layer 3 boundary you have to enter an ' ip helper ' address on the WOL server L3 vlan for each subnet you want to ' wake '.
What if you have 200+ subnets , I'm fairly sure the practical limit for ' ip helper ' addresses is 16 ?I wonder where the original poster got the idea that the practical limit for ip helper-address was 16? I agree that there is some additional overhead on the router for each helper-address that you add to the configuration. But a router should be able to process a lot more than 16 helper-addresses.
200+ would be a lot of helper-addresses and depending on what kind of router (how much CPU does it have) and what other features are configured doing 200+ might be a stretch. But most routers should be able to do lots more than 16.
HTH
Rick -
Unable to wake emacs across subnets
We have several emac labs w/ ard active on them, however, we are unable to wake them up from our central office location. If the client is available we can observe, control and just about anything else we need to do to them. Our biggest issue is that we can't wake them up across subnets. We also have a mini running server 10.4.7 as a task server out there...any ideas
First, make sure that "wake on network administrator access" is active in the Energy Saver -> Options on your clients.
If it is, try WakeOnLan or WakeOnMac and see if either of those work. If those don't work either, then the routers on your network are probably not correctly passing the necessary packet.
Hope this helps. -
Wake on Lan not working properly?
So as far as i'm aware Windows 8 supports wake on lan whilst the device is either in sleep or hibernate (not completely off) and so far it works fine when in sleep mode (no randomly turning on like lots of people have been saying) but nothing happens when in hibernate. Is there any particular reason why this may be?
Lenovo G780
Windows 8.1
Using unified remote (full) to control power options (tried in both administrative and not)
Qualcomm Atheros AR8162/8166/8168 PCI-E Fast Ethernet Controller (NDIS 6.30). Set to recieve packets
and i think i've made all of the nessasary changes to BIOs and my router (Belkin) to allow WoL (seeing as it works when sleeping)Hallo Forumreaders,
WOL (Wake On Lan) works only through a router when it is capable to forward to broadcast LAN-IP-adres.
In my consideration only the good old BEFSR41 is capable to forward to the broadcast adres for example 192.168.1.255 (SM: 255.255.255.0)
Because there is no IP-adres in powerless PC's the "Magic Packet" (which WOL realy is) MUST be send onto your LAN by means of the broadcast-adres.
Other routers are NOT able to sumit a adres like 192.168.1.255 in a subnet of 255.255.255.0 because they are NOT allowed to use any broadcast-adres.(they can get trouble by means of a broadcaststorm!!!)
So do not get rid of that old router you have!!
More info;
The "Magic Packet" contains the MAC-adres of your recipient host and wil trigger the powersupply of that PC.
For Internet WOL, try http://www.dslreports.com/wakeup, submit your IP-adres of your home, your MAC-adres of your PC and klick on "Wake up".
Looking for an application for on a USB-stick, download the small tool; http://www.depicus.com/wake-on-lan/wake-on-lan-gui.aspx
Hope I helped,
Greetings
Message Edited by R.J. on 02-11-2010 02:04 PM -
Multiple routers and subnets - can't access across subnets
Hey all, I'm having an issue with multiple routers and subnets on my FIOS connection. Here's how everything is setup:
Primary router:
ActionTec MI424WR Rev D (from Verizon)
WAN IP: From ISP
WAN NETMASK: From ISP
LAN IP: 192.168.1.1LAN NETMASK: 255.255.255.0
Secondary router (WAN connected to ActionTec LAN):
Belkin N750 gigabit w/ 802.11n
WAN IP: 192.168.1.2
WAN NETMASK: 255.255.255.0
LAN IP: 192.168.2.1
LAN NETMASK: 255.255.255.0
With this setup, I have the secondary router's WAN port connected to a LAN port on the primary router. Each are broadcasting an SSID and each are running DHCP to assign address to their respective subnets. Everything was well and good, except that I could reach 192.168.1.* systems from 192.168.2.*, but not vice versa -- anything connected to the Primary router was blind to systems connected to Secondary. Also, I could not ping anything on .2 from .1.
So, I added the following static route to the primary router:
DESTINATION: 192.168.2.0
NETMASK: 255.255.255.0
GATEWAY: 192.168.1.2
Once this was added to the router, I could ping everything, so that was good. However, even though .1 can now ping .2, I can't access certain things such as the web interface of my NAS (192.168.2.2). I can ping it, but accessing it in the browser from .1 doesn't work; however, accessing from .2 does work.
I think the ActionTec router might be blocking it, but that's just a guess. The firewall on this thing has me thoroughly confused. Currently, I have 192.168.1.2 in the DMZ on the ActionTec, but that didn't make a difference. I've also completely disabled the firewall on the secondary Belkin router, but still nothing.
Any help from the pros here? Much appreciated!
Solved!
Go to Solution.Ok, I figured it out and everything is now working. The issue appears to be that the ActionTec router doesn't recognize traffic from Subnet 1 to Subnet 2 as internal traffic -- it treats it as external traffic and closes it off. To fix this, it required some Advanced Firewall Filters that were far from unituitive and took a lot of testing to get it just right. If anyone runs into a similar situation in the future, here's a rundown of what I did to make it all work:
Primary Router:
ActionTec, MI424WR Rev D
WAN IP/NETMASK:Assigned by ISP
LAN IP/NETMASK:192.168.1.1 / 255.255.255.0
Secondary Router:
Belkin N750 Gigabit w/ 802.11n
WAN IP/NETMASK:192.168.1.2 / 255.255.255.0
LAN IP/NETMASK:192.168.2.1 / 255.255.255.0
Plug Secondary router's WAN port into a LAN port on the Primary router.
Setup Secondary router to have static LAN address (192.168.1.2)
At this point, you should have 2 separate subnets: Subnet 1 (192.168.1.*) and Subnet 2 (192.168.2.*).
Systems on both subnets should be able to reach the internet. Also, Subnet 2 should be able to ping and reach systems on Subnet 1; however, systems on Subnet 1 should not be able to ping or reach systems on Subnet 2. For this, we need to create a static route so Subnet 1 can reach Subnet 2.
Create and apply the following static route in the Primary router: (Advanced > Routing)
RULE NAME:Network (Home/Office)
DESTINATION:192.168.2.0(your secondary subnet)
GATEWAY:192.168.1.2(secondary router's WAN IP)
NETMASK:255.255.255.0
METRIC:1
The router now has a route between Subnet 1 (192.168.1.*) and Subnet 2 (192.168.2.*). You should be able to ping systems on Subnet 1 from 2, and ping systems on Subnet 2 from 1. You should not be able to access any systems, though -- the firewall is still blocking all but ping traffic from Subnet 1 to Subnet 2. We need to create some firewall rules to allow this communication.
Make sure Primary firewall is set to at least typical/medium (Firewall Settings > General).
We need to create some network objects to make it easier to manage the rules we'll create. Go to Advanced > Network Objects and do the following:
1.Click Add. You are now on Edit Network Object screen.
2.Set Description to 'Subnet 1'.
3.In Items section below, click Add.
4.Set Network Object Type to 'IP Subnet'.
5.Set Subnet IP Address to 192.168.1.0.
6.Set Subnet Mask to 255.255.255.0.
7.Click Apply. You are now back on Edit Network Object screen.
8.Click Apply. You are now back on Network Objects Screen.
9.Repeat the above steps again, but this time creating a second network object called 'Subnet 2':
Nameubnet 2
IP Subnet:192.168.2.0
Subnet Mask:255.255.255.0
Now we create the firewall rules. Go to Firewall Settings > Advanced Filtering.
In the Inbound/Input rules section, click the Add link next to Network (Home/Office) Rules.
Create the following Advanced Filter:
SOURCE ADDRESSelect 'Subnet 1'
DEST. ADDRESSelect 'Subnet 2'
PROTOCOL:'Any'
OPERATION:'Accept Packet'
OCCUR:'Always'
Click Apply. You will now be back on the Advanced Filtering page.
In the Outbound rules section, click the Add link next to Network (Home/Office) Rules.
Create the following Advanced Filter:
SOURCE ADDRESSelect 'Subnet 1'
DEST. ADDRESSelect 'Subnet 2'
PROTOCOL:'Any'
OPERATION:'Accept Packet'
OCCUR:'Always'
Click Apply. You will now be back on the Advanced Filtering page.
Click Apply.
You're all done. You should now have internet access on both subnets, be able to ping across subnets and also be able to access services across subnets (local webservers, SSH, telnet, mail, etc). You will not be able to see network file shares across subnets in Windows, however, as this requires a WINS server (which is well outside the scope of this post). For instance, I have a Western Digital NAS on the 192.168.2.0 subnet that I can access as \\Mybooklive\ from within Subnet 2; on Subnet 1, however, I have to access it by its IP \\192.168.2.10\. -
Manage machines across subnets?
What steps do I need to take to be able to manage clients across subnets? I need to be able to wake clients that are not on my local subnet (my office is in one subnet and the clients are distributed all over a university campus with subnets that correspond to buildings). Is there anything that I can do to make that happen? My admin machine is using ARD 2.2 on Tiger.2 and the clients are ARD 2.2 Client on Tiger.2. I used to be able to wake the machines to gain access in the 2.0 version of ARD, but not anymore... Help! Please!!!
Thanx in advance!Waking a system requires that the router(s) pass Directed Broadcast, something most network administrators don't want to allow. If Directed Broadcast is blocked, there's no way any software can get the packet through to wake a sleeping system. Perhaps the network admins have made some changes that now block Directed Broadcast.
If so, and you can't get your network admins to turn that on, the only solution will be to set your systems not to go to sleep except for the monitors. -
Wake On Lan only works within a few minutes
Hi!
I have a problem...I left my MacPro sleeping for a few hours and now it will not respond to wake on lan...It does work to wake within a few minutes but not after a few hours.
Anyone have a solution for this? (I'n not using a router)Found the problem!! A nice person on logmein forums helped me. Thought i should post the solution in case somebody runs into this issue. I was forwarding the local IP of my computer (192.168.2.2) to a port (say port 9). It seems a router remembers the local IP's for a few minutes after the mac goes to sleep and after that its ARP table (which links MAC address to IP address) gets deleted. This is why it works for the first few minutes and not after that.
So the local IP being forwarded should be the 'broadcast address' and not the local computer's LAN address. It seems for subnet mask 255.255.255.0 the broadcast for IP range 192.168.2.x takes place for x=255. So i changed the router settings to forward local IP 192.168.2.255 to port 9. And it started to work. Hopefully this should help anyone with the same issue. -
How to Enable Wake On Lan over the Internet??
Hi, I am using RV220W with the latest firmware, I want to make "Wake on LAN" work for my NAS, I found the following description on Internet:
"If you wish to use Wake On Lan over the internet you will need to set up your destination firewall/router to allow "Subnet Directed Broadcasts". Most routers and firewalls disable this option by default.
You will then need to allow traffic through on your firewall/router on a specific port. The choice of ports is up to you."
So how can I enable "Subnet Directed Broadcasts" on RV220W??
Thanks.
RaymondHi Jasbryan,
If RV220W doesn't forward UDP to a broadcast address, could you ( i.e. Cisco) provide a tools for sending WOL Magic Packet to the LAN on Router Device Manager page?
I see many routers also provide this tools from their manager page.
Thanks.
Raymond -
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 -
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,
johnhehe, 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 -
I am running 6.2(2) on 7K. My woke on lan server is svi901 and physically on the 5K down stream. I am trying to setup wake on lan to sent direct broadcast from 7K out to the clients remote subnets. From other router WoL example it requires ip forward-protocol udp 7 in global config. I don't see that command availabe in 7K. Is this command available or is there other way to config WoL on 7K?
ThanksHere is a good doc on WOL:
http://www.cisco.com/en/US/partner/products/hw/switches/ps5023/products_configuration_example09186a008084b55c.shtml
https://www.ciscotaccc.com/kaidara-advisor/lanswitching/showcase?case=K74260926
Remember to configure ip forward-protocol udp 7 and ip directed-broadcast on the last hop router (nexus in this case).
WOL does not require directed-broadcasts unless you've got a host on a different subnet attempting to do it. if that is the case then you need to allow directed-broadcasts.
I have seen issues on access ports if ports were not set to auto auto.
Nothing special about the Nexus I am aware of.
In regards to possible conflict with the DHCP, make sure WOL is not using UDP/67 or you might run into some issues with DHCP snoop. I see the hosts using WOL and DHCP are on the same subnet but are the WOL and DHCP servers on the same subnet?
Fabienne. -
More of a comment then a query but I'm amazed that the WOL is not implemented correctly. Very frustrating that it only works when a system is in sleep mode. If a PC is off it can be woken up, so why Apple chose not to allow this is beyond me.
This means if I need to image some systems I have to go and switch each one on manually. I'd chose to have each systems default boot-device as the network card so if no netboot foud it'd go and boot off the HDD.Wake-on-LAN is implemented correctly, in that a sleeping Mac can be awakened by a signal across the network. What you want is Boot-on-LAN, and that's never been a feature of Macs (at least not any I can remember, back to the original Mac models) with the exception of the Intel-based Xserves. But you can submit your comment to Apple via their feedback pages:
http://www.apple.com/feedback -
Can linksys please incorporate support for wake on lan please?
Hallo Forumreaders,
WOL (Wake On Lan) works only through a router when it is capable to forward to broadcast LAN-IP-adres.
In my consideration only the good old BEFSR41 is capable to forward to the broadcast adres for example 192.168.1.255 (SM: 255.255.255.0)
Because there is no IP-adres in powerless PC's the "Magic Packet" (which WOL realy is) MUST be send onto your LAN by means of the broadcast-adres.
Other routers are NOT able to sumit a adres like 192.168.1.255 in a subnet of 255.255.255.0 because they are NOT allowed to use any broadcast-adres.(they can get trouble by means of a broadcaststorm!!!)
So do not get rid of that old router you have!!
More info;
The "Magic Packet" contains the MAC-adres of your recipient host and wil trigger the powersupply of that PC.
For Internet WOL, try http://www.dslreports.com/wakeup, submit your IP-adres of your home, your MAC-adres of your PC and klick on "Wake up".
Looking for an application for on a USB-stick, download the small tool; http://www.depicus.com/wake-on-lan/wake-on-lan-gui.aspx
Hope I helped,
Greetings
Maybe you are looking for
-
HD package confusion - sports channels and Extreme HD
I'm a recent FIOS convert from Optimum. After about 10 days I can say I am very pleased for the most part with the new service. Picture quality is better and I like the guide and DVR features better than my Optimum STB. The one problem I have had sur
-
How can i get my music to sync to my iPhone? all my music is saving into the cloud
i upgraded to iOS 8 on an Iphone 5s (from a 4s) and an iPad air and almost all of my music is now stored in the cloud, not on the device. All iCloud settings are turned off. I have one more 5s to upgrade (again, from a 4s). How can i upgrade and
-
IOS 5.1 bluetooth problem with LG HBS-700
After upgrading to iOS 5.1, my LG HBS-700 bluetooth headset still plays music from my iPhone, but the music controls no longer work (play/pause, next/last track). The phone functionality (start/answer call) still works. Is anyone else having these
-
Query Builder in Web application
Hi, I want to develop a web application, which include query builder for database using Jdeveloper nad ADF. In this application must be page with this queries and execute them. The problem is that i have no idea how to realize it, Please help me Manu
-
Upgrade version of swype for droid x2
Dear Verizon, I have a droid X2. The version of swype on it is 2.24.66.17859 . I contacted Swype and i asked them what the current version of swype they are shipping is. They said v3.0 just started shipping to OEMs. They said they are still shi