Unsolved
This post is more than 5 years old
2 Posts
0
25030
June 10th, 2005 06:00
Optiplex 170L - remote wake up
Hi all!
I'm experiencing some difficulties in waking up my Optiplex 170L with magic packet.
The setting is enabled both in the BIOS setup and in the Intel PROSet diagnostic tool.
I'm using PCnet Magic Packet Utility to send the magic packet over my LAN.
What to do?
I'm experiencing some difficulties in waking up my Optiplex 170L with magic packet.
The setting is enabled both in the BIOS setup and in the Intel PROSet diagnostic tool.
I'm using PCnet Magic Packet Utility to send the magic packet over my LAN.
What to do?
No Events found!
Suldao
3 Posts
0
July 14th, 2005 02:00
I have successfully used the WOL feature on our OptiPlex 170L XP PCs with Intel PRO/100 VE network interface adapters, so know that it should work.
Add these configuration options to the 2 you have already made:
On the ADVANCED TAB of the NIC properties sheet in Device Manager select "Wake On Settings" and check that the value is set to "WAKE ON MAGIC and DIRECTED PACKET"
On the POWER MANAGEMENT TAB of the NIC properties sheet in Device Manager check ONLY the first two selection boxes:
"ALLOW THE COMPUTER TO TURN OFF THIS DEVICE TO SAVE POWER"
"ALLOW THIS DEVICE TO BRING THE COMPUTER OUT OF STANDBY"
Lastly, remember WOL only works when the computer has been shut down through the Windows OS shut down procedure. (If you initiate power off from the power button on the chassis you may not be able to wake the computer up via WOL).
This should make your configuration identical to my successful one. I use the free Command Line utility WOL COMMAND LINE from Depicus Software (http://www.depicus.com/wake-on-lan/wake-on-lan-cmd.aspx) to remotely power on our many OptiPlex 170Ls on our LAN.
I hope this helps you - Best wishes for success.
ztm
2 Posts
0
July 14th, 2005 07:00
May be I have some networks problems, but I cannot imagine what kind of problem! I used WOL in the past with the same PC and it was working.
Thank you anyway for you help!
speedstep
11 Legend
•
47K Posts
0
July 15th, 2005 20:00
WOL doesnt work in Switched environments with standard antismurf security settings.
It only works on hubs or networks with WIDE OPEN FIREWALLS.
Magic packets in a swtitched environment tend to be looked at as DOS SMURF attack directed broacasts and so they are disabled at the border and between segements on a switched lan.
Cisco IBNS supports WoL functionality through the 802.1x with Wake On LAN
http://www.cisco.com/application/pdf/en/us/guest/netsol/ns75/c685/ccmigration_09186a0080259020.pdf
Wake-on-LAN
No need to open any ports if used within multicast distribution job
Within a targeted multicasting based push distribution job, there is an option to have the Wake-on-LAN "magic packet" generated by the MDR (multicast domain representative). This allows WoL to work across routers and firewalls. In other contexts (WoL from the console or in non-multicast distribution jobs), WoL is based on a UDP packet (default port 9, see console, Configure, Services, Scheduler) sent as a subnet directed broadcast - which is not firewall friendly.
The reason is that subnet directed broadcasts are interpreted as SMURF ATTACKS.
Smurf is a simple attack based on IP spoofing and broadcasts sent as a directed broadcast to a subnet on the network.
If WoL also needs to work outside the context of a targeted multicasting based software distribution job, configure your routers to allow subnet directed broadcasts. However if you do that you are VUNERABLE to SMURF ATTACKS.