Wake-on-LAN Magic Packet broadcast
I would like to use Wake-On-Lan to send a Magic Packet to my PC to power it up - from a distant location over QuickVPN. WOL is working locally, and I can see running devices from a remote location with the QuickVPN client. But I can not broadcast my magic packet from the remote location. Is this because the known NetBIOS problem? How could I make the broadcast work?
This is not going to work with Quick VPN Client and a Linksys branded device. The reason is the software creates what is called a split tunnel instead of a full tunnel.
In a full tunnel setup, there is a pool of addresses to have assigned to vpn clients. When you are assigned an ip address from this pool you essentially become part of the local network (meaning all broadcasts and unicasts go thru the tunnel), where as with a split tunnel setup you only send traffic to the tunnel that is destined for the remote subnet VIA UNICAST.
If you try this with a Small Business Pro device it may work, because you have the ability to do a full tunnel. The broadcast of the WOL will go out of your internet connection, not your virtual tunnel connection.
Hope this helps.
Bill
Similar Messages
-
Wake on LAN - ip directed broadcast
We're looking at deploying a Wake-on-LAN solution for software distribution. The first alternative to distribute the 'magic packet' is enabling 'ip directed-broadcast' in each router, which presents a security risk (man in the middle attack, ARP table poisoning), the second alternative is to extend ARP aging time in the routers which presents the same security risk.
My question is, how can be this security risk reduced or minimized (options I've heard of: 'dynamic ARP inspection' in the switches, ACL on the router associated with the ip directed-broadcast command allowing only software distribution servers to convert directed-broadcast packets into unicast packets). I have a concern extending ARP aging time and its impact with current or future application.
I'll appreciated any comment. Thanks.IP directed broadcasts are used in the popular "smurf" denial-of-service attack and derivatives thereof. An IP directed broadcast is a datagram that is sent to the broadcast address of a subnet to which the sending machine is not directly attached. The directed broadcast is routed through the network as a unicast packet until it arrives at the target subnet, where it is converted into a link-layer broadcast. Because of the nature of the IP addressing architecture, only the last router in the chain, the one that is connected directly to the target subnet, can conclusively identify a directed broadcast. Directed broadcasts are occasionally used for legitimate purposes, but such use is not common outside the financial services industry. In a "smurf" attack, the attacker sends Internet Control Message Protocol (ICMP) echo requests from a falsified source address to a directed broadcast address, causing all the hosts on the target subnet to send replies to the falsified source. By sending a continuous stream of such requests, the attacker can create a much larger stream of replies, which can completely inundate the host whose
address is being falsified. If a Cisco interface is configured with the no ip directed-broadcast command, directed broadcasts
that would otherwise expand into link-layer broadcasts at that interface are dropped instead.
If you are behind a firewall and are confident in your security policy, then I don't see this as being a problem. -
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 -
Dv6-7014nr Does it support Wake-on-LAN, WoWLAN, or Wake on USB.?
I am not finding Bios settings for any of these features. Inn fact the BIOS looks prettypaltry. Am I missing a hidden menu or something or is the BIOS really that bad feature-wise? I found the USB "allow this device to start the computer" setting in the USB device powermanagement settings but I can't select it. Is there a way to enable that setting?
wake-on-lan must be enabled already and no option for customers to configure in BIOS because these are consumer units and not many users use such options on this platform.
I can see that network driver in device manager gives you option to configure Wake-on-Lan under device propertties>Advanced tab. several options such as wake-on-lan magic packet - Shutdown wake-on-lan etc...
yes the options may be limited to driver used. if its factory image or drivers are used from hp.com; that should give you options.
Regards,
WW
“I am an HP Employee“
***** Click the KUDOS star on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem*** -
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 -
I have an MSI H87M-G43 with BIOS v.1.8 running Windows 8.1 64-bit. I cannot get Wake On Lan to work with this motherboard. Can anyone confirm this is working with the MSI H87M-G43 motherboard?
Here is the PC Configuration:
CPU Intel Core i5-4440 3.1GHz
PSU Corsair CX430
DIMM1:
DIMM2: Corsair XMS3 DDR3 4GB CMX4GX3M1A1333C9
DIMM3:
DIMM4: Corsair XMS3 DDR3 4GB CMX4GX3M1A1333C9
SATA Port 1: SSD Samsung 840 EVO 120GB
SATA Port 2:
SATA Port 3: HDD Samsung 1TB SATA II
SATA Port 4: HDD Samsung 1TB SATA II
SATA Port 5: DVD Liteon IHAS124-14 24X
SATA Port 6:
SATA Port 3+4 RAID1 (Mirror)
BIOS v1.8:
01. F6 Restore Defaults: Load Optimized Defaults
02. LAN Option ROM: Enabled
03. SATA Mode: [RAID Mode]
04. SATA3 Hot Plug: Enabled
05. SATA4 Hot Plug: Enabled
06. Initiate Graphics Adapter: [IGD]
07. Serial (COM) Port 0: Disabled
08. Parallel (LPT) Port: Disabled
09. EuP 2013: Disabled
10. Windows 8/8.1 Feature: Enabled
11. Wake Up Event By: [BIOS]
12. Resume by PCI or PCIe Device: Enabled
13. Resume from S3/S4/S5 by USB Device: Enabled
14. GO2BIOS: Enabled
I have installed the following drivers:
01. Intel Chipset Driver 10.0.20
02. Intel SVGA Driver 10.18.10.3960
03. Realtek PCIE Network Drivers 8.35.716.2014
04. Intel RST RAID Driver 13.1.0.1058
05. Realtek HD Audio Drivers 6.0.1.7111
06. Intel Management Engine Components 9.5.15.1730
In the Realtek PCIe GBE Family Controller properties I have set:
01. Allow the computer to turn off this device to save power: Ticked
02. Allow this device to wake the computer: Ticked
03. Only allow a magic packet to wake the computer: Ticked
04. Energy Efficient Ethernet: Disabled
05. Green Ethernet: Disabled
06. Shutdown Wake-On-Lan: Enabled
07. Wake on Magic Packet: Enabled
08. Wake on pattern match: Enabled
I have also tested that when I send Wake On Lan magic packet data from another PC, this PC successfully receives the Wake On Lan magic packet data. However, when the PC is in Sleep/Hibernate/Shutdown state, it does not wake when it receives the Wake On Lan magic packet data.
TIAQuote from: mville on 10-February-15, 02:16:43
No.
It is difficult to identify where the problem is then
Quote from: mville
... and to make matters worse, during extensive testing of this Wake on LAN issue, I set:
Wake Up Event By: [OS]
Resume From S3 by USB Device [Enabled]
and my USB keyboard is also unable to wake from S3/Sleep. When Wake Up Event By: [BIOS] is set, the USB keyboard is able to wake from S3/S4/S5.
Well mine does not wake up by keyboard, which is what I want, I need to see if keyboard with power key will work.
Quote from: mville
Last week, I submitted a support ticket with MSI, who responded with a basic set of wake on LAN instruction. I explained that, although I have followed the instructions, it still does not work. MSI have now gone silent on me.
I had somewhat similar experience with ASUS, but they just kept repeasting themselves, seems like language barrier or they just pretending. -
Hi,
does MacPro support wake on lan - "magic packets"?
I am trying to wake up MP from sleep from another location (because of Apple Remote Desktop):
http://www.dslreports.com/wakeup (there are many sites like this)
Wake for Ethernet network administrator access is enabled in the System Preperences pane.
Is it possible?
Thanks!
edit: maybe this can solve the problem, but I don't know how to use it:
http://www.macupdate.com/info.php/id/20110/wakeonlan-command-line
Message was edited by: cooolorRegarding the different remote wake-up behaviour within or after a certain amount of time since when the machine went to sleep, this is most likely related to entries in the ARP tables of some router expiring. After some time that a router doesn't see traffic for your machine's IP address, it forgets that data for that address has to be forwarded on that physical port. Therefore, when trying to wake up a machine from remote, the "magic packet" does not pass through the router to the machine at all.
This can be solved by introducing some always-on low-power programmable appliances that can generate the magic WoL packet from inside the LAN on request. For example, routers that can mount OpenWRT ( http://wiki.openwrt.org/TableOfHardware?action=show&redirect=toh ), e.g. La Fonera and some Linksys, can do this after installing the "wol" package.
There is still the problem that despite the supported features of the Apple Remote Desktop, wake on lan does not wake up the machine when it's completely shut down and not just in sleep mode. -
Does ZCM use Magic Packets for Wake On Lan?
Hello,
not sure if this is the correct forum...
can someone please refer me to the technical documentation of wake on lan from ZCM or tell me how Zenworks has internally implemented Wakeonlan - is it simple Magic Packets or is there some other mechanism?
thx,
hugoI also remembered there is this TID that has some good info.
http://www.novell.com/support/kb/doc.php?id=7004716
Jim
"susehoush" wrote in message
news:[email protected]..
Hello,
not sure if this is the correct forum...
can someone please refer me to the technical documentation of wake on
lan from ZCM or tell me how Zenworks has internally implemented
Wakeonlan - is it simple Magic Packets or is there some other
mechanism?
thx,
hugo
susehoush
susehoush's Profile: http://forums.novell.com/member.php?userid=75757
View this thread: http://forums.novell.com/showthread.php?t=462915 -
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 -
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 -
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). -
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) -
Wake On Lan Feature - How to enable??
Hi..
I would like to enable WoL feature in certain part of our network. Is there a global command to enable that?. or does it only require 'dot1x control-direction in' interface configuration?..
Also does the WoL Magic packet get forwarded through routers??
Any help appreciated.
Thanks.
GTCould I just clarify the answer that Rick gave? I fear that it might give the impression that the ip helper-address is on the remote LAN, which it is not.
You should put the ip helper-address on the LAN where you have the management server that is trying to wake up the remote PCs. If the remote PCs are distributed across several remote LANs, you will need one ip helper-address command on the "central" LAN for each and every remote LAN you are trying to get to. You can have as many ip helper-address commands as you need to cover the remote LANs you have.
As Rick says, if you have multiple routers between the server and clients, then the ip helper-address commands only need to be on the LAN that hosts your management server.
What the ip helper-address command does, is to recognise broadcasts on the server LAN, and convert them into unicasts to the address you specify: in my example 192.168.42.255. These unicasts are routed through the network in the normal way until they reach the destination LAN. When they get there, the client LAN's router say "eh-up, this is my IP subnet broadcast address; I had better put a broadcast MAC header on it." But it will only do that if you have configured ip directed-broadcast on the target LAN.
If you think of the way it works, you could even do WoL across the Internet, where you do not have the hand on the intermediate routers.
Is that OK?
Kevin Dorrell
Luxembourg -
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 -
How may I enable Wake On Lan on the B570-1068AFU
Hi all, I have the B570-1068AFU. I want to enable Wake on Lan on this laptop, but I do not see a bios setting for it. Is it possible with this Laptop? Thanks.
Hi 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
Maybe you are looking for
-
HP Envy merge C on MBR1 and D on MBR2
I have an HP Envy 17 3D. The hard drive is partitioned into 2 MBR's. MBR 1 has the C: & E: MBR 2 has the D: & F: I have Partition Master 9.2.2 Can I take some of the space off of Drive D: for Drive C:? Partition Master says the drives need to be si
-
SRM SC Workflow is not working as per BRF expressions
We are having SRM 7.0 SP5 Based on SC item values, We are determining whether the process level is required or not using BRF expressions. For a particular data, only 2 process levels are selected. But I go into debugger mode and skip one process leve
-
Forgot to turn off FIND MY IPHONE before restoring to another iphone
I restored all my data to my husband's iphone 5S after he got a new iPhone 6 but I forgot to turn off FIND MY IPHONE in my old device. Now I can't do it in the old device because the apple ID and other setting are associated with the new device. The
-
Buying TV shows from US store, but I'm in Canada
Hi all, Please forgive me for asking, as I'm sure someone has asked this somewhere else, but I can't find it. I live in Canada, and I wanted to buy some seasons of TV shows. They are not listed in the Canadian iTunes store (actually, there aren't any
-
Concrete class name in StackTraceElement
Does anyone know how to get information about concrete classes on the java stack trace? It is customary to get stack traces that list abstract classes or interfaces, but in the example below what was the concrete class implementing HttpServlet or ext