Windows WOL

[LiteWaiter]

Struggling getting my Windows 7 fileserver working with WOL.

The montherboard is ABit ip35-e and the network card is Dlink DFE538tx.

I've checked the BIOS...the only setting for WOL is something about the onboard Marvel Yukon controller which I think is bad since it isn't being recognized, that is why I added the Dlink card.

Windows 7 sees the Dlink card and does give me the option to enable WOL (with/out magic packet).

When I put the machine into sleep (or hibernate) the machine refuses to WOL. I've tried with the magic packet on/off hitting it's IP/MAC from another machine but it refuses to wake up.

I see one of four possible issues:

1. The Dlink card is somehow not seeing the packet.
2. The motherboard is not keeping the card "hot" in some way so it can see the packet.
3. Something about the onboard LAN being bad has some effect.
4. Something else in Windows 7 I forgot to configure.

Can someone lend some advice?

 

[JackMDS]

The D-link might not be WOL capable with the Motherboard.

The onboard Yukon is a "Quirky" card.

However it should work download the recent Drivers form Yukon.

http://www.marvell.com/support.html the card model is 88E8056

Download the specific Driver for your versin of Windows (not th whole driver package) and install it this way.

Download the drivers and unpack them to a folder of your choice.

In the Device manger, right click on the adapter.

Click on Update Drivers, and choose the Browse my computer for drivers,

Choose let me pick from a list , Click on Have a Disk and point to the folder with the Drivers.

.

 

[LiteWaiter]

The problem there is I don't even see the 88E8056 device in the device manager. How can I update the driver for it?

 

[Nothinman]

Boot a Linux Live CD/USB stick and see if the Yukon is detected, at least that'll tell you if it's a hardware or Windows issue.

 

[JackMDS]

The last BIOS from Abit are from few years ago.

Check if you have the last release.

Then boot one time to the BIOS disable the Card and boot without it.

Then Boot down, enable the card and try Nothinman idea.

That will give you an indication if the hardware works.

If it works boot to Windows make sure that there is No Ghost related to the card in the Device Manger and then scan for new hardware Device.

As far as PCI card, log to this page and scroll down to
Hardware implications.

 

[LiteWaiter]

Jack,
Onboard Marvell Yukon doesn't show in lspci in unbuntu. Since this device was working in XP and Windows 7 at some point in the past (machine was on the shelf for a year before I decided to make it a file server).

I can only assume I've trashed it somehow.

So with the DFE-538tx it is working perfectly with the exception of WOL. No matter how I configure it (magic packet or not) hitting it in sleep/hibernate mode will not bring the machine up.

I guess the MB likely isn't keeping the network card alive or something.

I guess my choices are:
1. Get another NIC and hope it is the DFE-538tx not responding to WOL
2. Get another MB with an integrated LAN that supports WOL.
3. Punt.

 

[Emulex]

you sure the o/s isn't keeping the card alive? at which dream state? S1/S3/S5?

what are your o/s and settings to keep the card alive.

dell is the same way. hell my inspiron 530 just dies when it goes into deep sleep. but it does something unique which my switch doesn't seem to like. it switches to 10/half in sleep and the switch is AUTO so it doesn't really matter. if you have a smart switch i'd seriously take a look at diagnostics to see if its throwing CRC errors in sleep(usually also seen at boot when pxe booting).

 

[JackMDS]

WOL and other wake-up means are pretty much a crap shoot with old Hardware.

This is an example to the confusion, http://answers.hackaday.com/how-can-i-convert-pci-wol-signal-to-wol-header

It is only recently with push to "Green" that manufactures started to pay more attention to his feature.

Few month ago I needed a countable WOL to be able to wake-up a computer through the Internet and use it with special switching system to control temperature in remote location.

I went through 10 different old computers until I found one with a Biostar mATX P-4 board that is working OK.

If the IP-35 does not support WOL through the pci you need a new Mobo.

 

[Dahak]

On thing that I remember I had to look at trying to get wake on lan to work is sometimes you have to go into the power management options of bios and enable pci wake up, from the manual of your board its under Power Management and enable Wake Up by PME of PCI

 

[LiteWaiter]

Whoa....

I updated the BIOS and boom the Marvell Yukon shows up again. It is like the BIOS somehow hid it.

Things are a bit better setting the BIOS option to enable WOL on On Board LAN allows me to wake the machine from sleep....however only if I turn OFF the magic packet in the device manager for the NIC.

I only want the machine to wake when I browse to it in Windows Explorer. This works, but I am worried other packets will hit it and wake it up as well, yes?

Not sure why the magic packet doesn't work (or if I needed cause this server is only use on the lan), but I've tried a couple of WOL apps and either they don't work or I am not getting the parameters correct.

Thanks for the help!

 

[JackMDS]

If it is not set to wake only by Magic Packet every LAN traffic will wake it up.

I.e., if you have other computer on the network depending on the type of traffic the computer might periodically wake up on it own.

Try the Magic Packet with full Hibernation. I.e, the computer is really off not just a sleep.

This result is an additional 20-30 second of boot time, but it usually works better.

How do you send the Magic Packet?

 

[LiteWaiter]

Tried a program "Wake on LAN Ex2"

Input the IP (192.168.1.50), Macaddress (00-50-8D-BC-01-01), netmask (255.255.255.255) and port 7.

Machine is hibernated using: shutdown /h

 

[JackMDS]

Did you open port 7 toward the IP of the computer?

Try also netmask 255.255.255.0

 

[LiteWaiter]

This is on the LAN so no issues with open ports.

I tried 255.255.255.0 for the netmask (and even 192.168.1.255) but no help.

I did notice that the NIC connector light is flickering so clearly it is powered on.

Just can figure out what it's listening for :-(

 

[JackMDS]

Download this and let it run on the computer that is suppose to sleep.

Send to it Magic Packet (while every thing is running) and it will tell you if it gets there.

There is a lot of other goodies of WOL on the same site.

http://www.depicus.com/wake-on-lan/wake-on-lan-monitor.aspx

 

[LiteWaiter]

The saga continues....

Here are the things I have done.

1. Verified in sleep or hibernate the 88e8056 Lan (integrated) is flashing.
2. Made sure Wake-up using magic packet is set. Made sure in the advanced tab that wakeup using magic packet is set and wake up from shutdown are set.
3. Install a WOL monitor and it is seeing packets.
4. Tried 3 or so WOL clients trying a variety of ports (0,5,7,9) and netmask (255.255.255.0,0.0.0.0,192.168.1.255, 255.255.255.255) in both shutdown and hibernate AND IT NEVER WORKS
5. Removes the magic packet checkbox and from sleep the machine will wake (far too often) from any LAN access.

I guess I am just going to give up.

Thanks for your help anyway.

 

[JackMDS]

I went few times through the the same frustrating process.

End-User Networking life is Not easy.

802.11g WIFI data sheets state that it can do 300' indoor.

802.11n WIFI data sheets state that it can do x10 more than 802.11g

That means 3000' indoor, Right? - -

Well guess what? WIFI distance is Not the only thing that we are lied/decived with.