K9A2 CF Wake On Lan / WOL issue

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

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

Similar Messages

H77MA-G43 wake on lan (WOL) issue

Hi guys,
I need WOL to be enabled on 4 machine h77ma-g43 based, I3 3220 CPU.
I have last BIOS installed , 1,9, I've disabled eup, tryn' for half an hour to enable WOL on the integrated NIC but nothing seems to work...
I think the only way is to buy a new PCIE NIC... (because there's "wake on pcie" on the bios settings) and this is very disappointing.
PS. When mobo is turned off, I see no led activity, WOL software is well configured and I often use it with other mobos/PCs.
Any suggestion? If not... this is the first mobo I ever see that not support WOL!!
thank you

Check the sticky >>Wake on LAN<<

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

WRT160Nv3 Wake On Lan Forwarding Issue

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

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

MSI P45 Diamond (MS-7516) Wake On LAN (WoL)

Hello,
I buy a new computer with this motherboard (MSI P45 Diamond (MS-7516) BIOS v1.5) and try enable Wake on LAN function in bios, but i can't find it. Can be WoL enabled on this motherboard? How?
Thanks for any help

There is no option for it. Access the Device Manager and configure WoL there.

Wake-on-LAN (WOL)

Does anyone have Wake-on-LAN working? I downloaded a program called 'Wake550.app' which seems pretty straight forward. I have 'Wake for Ethernet network administrator access' enabled on the target computer. The computers are on the same subnet, but I just can't get it to work. This is a simple home network and its not worth investing in Apple's Remote Access software. Any suggestions?

I would also really like to know if it is possible to power-on a Mac via LAN. I haven't been able to get it to work, though I can wake my Macs from sleep. The Wikipedia article on Wake-on-LAN notes that a machine needs to reserve power for the ethernet card in order for WOL to work, so my guess is that the power management option that allows for WOL on Macs doesn't include reserving power for the ethernet card when the Mac is off.
Greg

Wake on lan (wol), uswsusp and 8139too

hello,
i want to get wake-on-lan working with uswsusp (or pm-utils, both don't work). when i halt the computer (like described here: http://gentoo-wiki.com/Wake_on_lan#Manual_method) and sent a magic packet with "wol", the computer starts, but when i suspend through "s2disk" (or pm-hibernate or "echo disk > /sys/power/state") the network card settings get somehow erased so it does not receive the magic packet.
what i've done so far:
1.) ethtool -s eth0 wol g
2.) in my /etc/modprobe.conf i have: "install 8139too /sbin/modprobe -i 8139too; ethtool -s eth0 wol g"
3.) echo -n PCI1 > /proc/acpi/wakeup # (to get: "PCI1 S4 enabled")
4.) echo -n shutdown > /sys/power/disk # (default is platform)
for shutting down the computer the first and third entry and then simply running "halt" did the trick, but for hibernating it simply doesn't wnat to work. i've tried every combination of things above. nada!
i've also tried this https://lists.linux-foundation.org/pipe … 10472.html:
Rmmod 8139 driver before suspend and use shutdown, not platform, mode
that also didn't work (no driver, no interface).
there are thousands of howtos out there, but most of them concentrate on shutting down not hibernating the computer.
wol is a really nice feature. i often use ssh, my computer is always running when i'm not at home. and i want to use hibernate.
using wol would save a lot of power.
my network card:
Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
Subsystem: D-Link System Inc DFE-528TX 10/100 Fast Ethernet PCI Adapter
though lshwd says:
8139too : D-Link System Inc.|DFE 530 TX+ Fast Ethernet Adapter
any other suggestions or hints?
please...
vlad
ps: and no, i don't want to use tuxonice.
Last edited by DonVla (2008-01-31 13:28:11)

i think the problem is that when hibernating the system is powered off by:
poweroff -d -f -h -i
with flags:
-d Don't write the wtmp record. The -n flag implies -d
-f Force halt or reboot, don't call shutdown(8)
-i Shut down all network interfaces just before halt or reboot
-h Put all harddrives on the system in standby mode just before halt or poweroff
i want to get rid of the -i flag. i don't know how to change this. there is no such configure option for uswsusp.
where can i change this for pm-utils if possible.
oh, as i see poweroff is a symlink to halt.
now i'm totally confused...
vlad
EDIT:
gentoo has this
RC_DOWN_INTERFACE="no"
entry which, as a friend of mine using gentoo told me, also works with hibernate.
is there a similar setting for arch?
Last edited by DonVla (2008-02-01 03:05:25)

Cisco RV180 and Wake-On-Lan (WOL)

Hello,
I got a RV180 (firmware version: 1.0.1.9) and I am bit surprised by the lack of the configuration flexibility...
I am trying to use Wake-On-Lan (from internet) to wake up a machine in my home (trying to be green and not keep the machine on all the time, just when i need it).
The configuration is quite simple:
Work machine ----> (internet) ----> (WAN) RV180 (LAN) ----> Home Machine (off, linux, wol enabled for UNICAST and Magic Packet - flags "ug")
What i tried so far:
1. All the following RV180 settings together:
   a. Used Port Forwarding from the WAN IP to the Home Machine IP (UDP port 7 and 9)
       - i had no choice but to put the Home Machine's IP address, since i cannot put the BROADCAST address (xxx.xxx.xxx.255) <- forbidden in the configuration page (i wonder if a new version of firmware allows this)
   b. Used Static DHCP to pair the Home Machine's IP to it's MAC address
   c. Used IP/MAC binding for the Home Machine
2. All the following RV180 settings together:
   a. Created a PPTP VPN connection
   b. Connected from the Work machine (obtained a LAN IP, can ping the Home Machine if it is on)
   c. Tried to send a broadcast message to LAN (no success !)
3. I also tried to activate the MULTICAST and BROADCAST WOL flags on the Home Machine but it seems that it receives some messages and the machine wakes up in a very short amount of time after i shut it down (it seems that RV180 sends some messages over LAN by itself).
In all the 3 possibilites above i was not successful in using WOL....
Is there any possibility to use WOL from internet in this configuration ?
Are there new options that will allow WOL from internet in the latest firmware ?
Any advice is appreciated
Thank you
Mircea

Dear Mircea,
Thank you for reaching the Small Business Support Community.
I was researching about your concern and found several people with the same inquiry where they were told WoL is not a supported feature on these Small Business Routers and that I think is a correct assumption, however I found the below threat where someone with a similar case scenario as yours were able to make it work, it's on a different RV router but I thought I may be interesting for you to check;
https://supportforums.cisco.com/thread/2188810
Please let me know if there is any further assistance I may help you with.
Kind regards,
Jeffrey Rodriguez S. .:|:.:|:.
Cisco Customer Support Engineer
*Please rate the Post so other will know when an answer has been found.

H55M-E21 LAN off (LED off) in S3 state, can't use wake on LAN (WOL)

I'm using H55M-E21 and Win7.
I can put PC to sleep mode (S3) and can wake it up by PS2 keyboard. Now I want to try remote desktop to wake up and connect to the slept PC. I can't connect to it.
The LAN link is down, the link LED from the back of PC is off.
In BIOS -> Power management -> ACPI on, BIOS on, ACPI Stanby state = S3, EuP2013 diabled
In Wakeup Event -> Resume by PCIor PCI-E device enbled.
Please help.

There are a few things you should check. Go into device manager and open the properties for the NIC you are using for this remote connection. First click on the Power Management tab and make sure the options are checked to "Allow this device to wake the computer". I would uncheck the option to "Allow the computer to turn off this device to save power" if it won't work while it's checked. You should also check the magic packet box.
Click on the Advanced tab and enable the option for "Wake on Magic Packet" and "Wake on pattern match". I can't recall if the "Shutdown Wake-On-Lan" option is supposed to be enabled or disabled but try enabled first.
- D

Windows 10 PC starting automatically due to Wake On LAN (WOL) Setting

If you have a PC randomly waking up after upgrading to Windows 10, you can run this command in an elevated command prompt to see what last woke the computer up:
powercfg /lastwake
In my case, there were 2 issues: one is Windows has a scheduled task called mcupdate_scheduled which is set to wake the computer up. Here is a picture which shows where to disable this:
I also had an issue with TeamViewer, which may be fixed with a future update. I even disabled the WOL feature within TeamViewer but it didn't help. The only way I was able to stop it was to go into Services and disable the "TeamViewer 10" service.
This will still allow you to use TeamViewer to connect to other machines, but will disable remote access to the machine itself, which is all I needed in my case. Other alternatives I use to connect remotely are Splashtop, VNC, and RDP.
This topic first appeared in the Spiceworks Community

Hi all!I have Windows Server 2012 R2. From start i have a little problem with my user profile, because usualy when i log in after reboot(or simple turn on computer) on my domain account on the server i log in ontemporary profile, but after i log out and log in again i have my standard account.And when i check my users folder i see something weird, because every users have standard folder icon, and my user have something other:When i check properties this folder i see "Volume installed"(from polish to english):
I don't know this folder have name "891100.000" because name of user is just "891100"
And when i open bitlocker i see something like this:And i don't know what is this, because on other computers i don't have this option...Yesterday i encrypt my drive using bitlocker and today i must log in 6times to have my standard profile, so i...

Wake-On-Lan (WOL) after sleep causes high CPU usage

Hi,
I noticed a problem with constant high CPU usage on one of my cores.
As much as 60% was used.
The problem occures after I put the system to "sleep" (S3 state) and perform a WOL with a "magic packet".
I discovered that ACPI.sys+0x1af44 thread was responsible (using sysinternals ProcessExplorer) under the System process.
If i perform WOL while the machine was shut down everything works perfectly.
My NIC is "Realtek PCIe GBE Family Controller" and I'm using the latest drivers.
I discovered that if I disabled the option in Power Management for the device: "Allow this device to wake the computer", the CPU usage immediately went to normal (without restarting). But enabling it back the high CPU usage resumes. Performing
another sleep and awaking the system with power button "resets" the CPU usage issue for "good". Until i WOL from sleep again ofcourse..
I contacted the motherboard manufacturer of the problem but so far no real answer.
I'm saddened because I need the WOL feature.
I'm hoping somebody who has more insight in the behaviour of ACPI on W7 can answer my questions.
Regards
Specs:
Model Name : GA-X58A-UD7(rev. 2.0)
M/B Rev : 2.0
BIOS Ver : FC
Serial No. :
Purchase Dealer :
VGA Brand : Nvidia      Model : 7950GT
CPU Brand : Intel      Model : i7 950      Speed : 3.06GHz
Operation System : Win 7 64-bit      SP :
Memory Brand : Corsair      Type : DDR3
Memory Size : 6GB      Speed : 1600MHz
Power Supply : 450 W

Hi,
I noticed a problem with constant high CPU usage on one of my cores.
As much as 60% was used.
The problem occures after I put the system to "sleep" (S3 state) and perform a WOL with a "magic packet".
I discovered that ACPI.sys+0x1af44 thread was responsible (using sysinternals ProcessExplorer) under the System process.
If i perform WOL while the machine was shut down everything works perfectly.
My NIC is "Realtek PCIe GBE Family Controller" and I'm using the latest drivers.
I discovered that if I disabled the option in Power Management for the device: "Allow this device to wake the computer", the CPU usage immediately went to normal (without restarting). But enabling it back the high CPU usage resumes. Performing another sleep
and awaking the system with power button "resets" the CPU usage issue for "good". Until i WOL from sleep again ofcourse..
I contacted the motherboard manufacturer of the problem but so far no real answer.
I'm saddened because I need the WOL feature.
I'm hoping somebody who has more insight in the behaviour of ACPI on W7 can answer my questions.
Regards
Specs:
Model Name : GA-X58A-UD7(rev. 2.0)
M/B Rev : 2.0
BIOS Ver : FC
Serial No. :
Purchase Dealer :
VGA Brand : Nvidia      Model : 7950GT
CPU Brand : Intel      Model : i7 950      Speed : 3.06GHz
Operation System : Win 7 64-bit      SP :
Memory Brand : Corsair      Type : DDR3
Memory Size : 6GB      Speed : 1600MHz
Power Supply : 450 W
same prob here. has anyone found a solution?
...stephen

Strange on - Wake on LAN (WOL) works with Win2K3, but not Windows 7

Hi,
I have a PC that I originally had Windows 2003 on. With Win2K3, I can send a wakeonlan (magic) packet (WOL) and get it to power on remotely from my home network/LAN.
I just installed Windows 7 Ultimate 64-bit, in a dual-boot configuration, i.e., so I can boot the machine to either Windows 7 Ultimate 64-bit or Win2K3.
As mentioned, I can power the machine up remotely (from my home network/LAN), but if I've LAST booted into Win7, then shutdown, it doesn't respond to the WOL packet.
I've confirmed that if I boot into Win2K3, then shutdown, the WOL works fine.
I have another PC that has both Win2K3 and Windows 7 (also dual boot), and that works fine with WOL.
One difference between the one that doesn't work vs. the one that works is that the one that works is a machine that I just built a couple of weeks ago, which uses an MSI 880gm-E43 motherboard.
The one that doesn't work also has an MSI motherboard, but it's an older one, an MSI K9NBPM2-FID.
I've cross-checked the various Windows power management settings between the one that works, and the one that doesn't work, but I just can't get WOL to work with Win7 on that older machine. I've even turned the Windows Firewall off completely on the machine where WOL isn't working, but no matter what I've tried thus far, no joy :(...
The only thing that I can think of is that the network card driver (it's the MS one, from the Win7 distribution) might not work with WOL, but I've checked, and it's the latest driver from MS (Nvidia Nforce Networking Controller - 10/17/2008 - 1.0.1.211), and MSI doesn't have a specific Win7 64-bit driver for this motherboard.
So, I was wondering if anyone has any ideas about this?
Is there some registry setting or something that might allow WOL to work?
Thanks in advance,
Jim

Hi,
Unbelievable!
Just for the record, I got WOL working with the older machine, JUST after I posted the original msg.
Here's what I did:
- I was in Device Manager, and did Update Driver, but
- I selected to let me choose, and then I checked the "Show Compatible devices" checkbox
Then, a 2nd, older (10/6/2006 - 6.2.0.127) driver appeared, so I figured, "what the heck?" and tried that. I then shut the machine down, and sent a WOL packet to it, and kind of forgot about it (machines in a different room), but a few minutes later "bing!", the machine had powered up and booted into Win7!!
Anyway, as I said, for the record, and hope that this helps someone in the future.
Jim

K9A2-CF Wake-on-LAN

Hi all.
Does this Mobo support WOL? I am trying to wake a machine remotely (from off, not standby) for remote admin purposes, but it does not respond to the magic packet. I can find no options for it in the BIOS, although the onboard NIC does stay powered when the machine is off.
Any ideas?

In the manual, under BIOS settings I found this which may be related:
Resume By PCI Device (PME#)
When set to [Enabled], the feature allows your system to be awakened from the
power saving modes through any event on PME (Power Management Event).
Resume By PCI-E Device
When set to [Enabled], the feature allows your system to be awakened from the
power saving modes through any event on PCIE device.
Not sure if the Realtek NIC is PCI or PCI-e device.....

Disabel Wake on Lan (WOL)

Hi,
I'm playing with pwersaving options of my Laptop.
Everything is working quite well, but i'm not able to disable WOL.
I tried this, which has no effect:
https://wiki.archlinux.org/index.php/Po … interfaces
Then i recognized, that NetworkManager is making changes to the card. So I made a dispatcher script, which works, when the enp5s0 is activated:
$ cat /etc/NetworkManager/dispatcher.d/90-wol
#!/bin/bash
if [ "$2" = "up" -a "$1" = "enp5s0" ]; then
/usr/bin/ethtool -s enp5s0 wol d
fi
For setting wol disabled after boot I made a systemd unit
$ cat /etc/systemd/system/enp5s0-wol-d.service
[Unit]
Description=Disable wol on enp5s0
After=network.target
[Service]
Type=oneshot
ExecStart=/usr/bin/ethtool -s enp5s0 wol d
[Install]
WantedBy=multi-user.target
which also works, but after suspend wol is set to state "g" again! grrrrr.
Does anybody have some suggestions who else could be fiddling around with the wol-settings?
There have to be some simpler solutions to disable wol.
Any suggestions and ideas are welcome.
Thanks.

If everything goes good you can always go back to Linksys firmware. You simply have to flash the latest Linksys firmware and then reset the router to factory defaults pressing the reset button for 30 seconds. Then it's back to what it was.
Of course, there is a certain risk that the 3rd party upgrade won't go through properly and maybe even damage the router. 3rd party fimware is of course not covered by warranty. Thus you want to be careful and read the instructions carefully.
Downgrading to older firmware is also always possible except in a very few rare cases I guess where a firmware upgrade changes something to the hardware (flash a different BIOS, boot loader, flash firmware in an internal chipset). But I think this is more a theoretical problem. If there was, you should find competent help in the dd-wrt forum.
The hardware version is printed on the label underneath the router. It says WRT610Nv2 or similar. If it only says WRT610N you have a v1.

Wake On Lan Issue

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

Anyone?

K9A2 CF Wake On Lan / WOL issue

Similar Messages

Maybe you are looking for