New Stone PC wont wake up on lan

[newpersn]

I dunno if im missing something. But we are replacing the computers in 2 of our IT Rooms.

 

The motherboards are Intel DH61WW's (i3's 4gb ram, Intel HD)

 

I Looked in the bios i cant see anything that stands out. I've checked device manager and it looks like everything is fine in there..

 

The computers i took out of the rooms woke up on lan alright.

 

we are using impero to wake the computers. (works fine for the dells and the old stone computers)

 

Any ideas? Im at a stuck point!

[russdev]

I dunno if im missing something. But we are replacing the computers in 2 of our IT Rooms.

 

The motherboards are Intel DH61WW's (i3's 4gb ram, Intel HD)

 

I Looked in the bios i cant see anything that stands out. I've checked device manager and it looks like everything is fine in there..

 

The computers i took out of the rooms woke up on lan alright.

 

we are using impero to wake the computers. (works fine for the dells and the old stone computers)

 

Any ideas? Im at a stuck point!

 

First thing to check is are using default windows 7 network card drivers if so then goto manufacturer website and install latest as when it comes to WOL that is number one factor.

 

Russell

[twin--turbo]

WOL is usualy a hardware function found in the ACPI or power management setting in the BIOS.

 

Rob

[newpersn]

Intel Card. Intel Drivers. Will see if there an update on intel website.

 

 

I checked the bios. Its all turned on.

[twin--turbo]

And the MAC address is correct for the magic packet?

 

Rob

[glennda]

I think its called something like wake from S3 or wake from S4 from under the power menu.

 

There is a full PDF with bios info here.

 

Then boot windows. open up the nic and select config and choose the advanced tab. there is an option in there for wake on lan.

[EvLPhenom]

Is this on all the machines?

[twin--turbo]

I think its called something like wake from S3 or wake from S4 from under the power menu.

 

There is a full PDF with bios info here.

 

Then boot windows. open up the nic and select config and choose the advanced tab. there is an option in there for wake on lan.

 

S5 State Soft powe off.

 

S1-4 Are Sleep states.

[mac_shinobi]

I thought WOL ( Wake On LAN ) was a combination of the above

 

1. Enabled and configured correctly in the bios ( assuming the NIC and bios support WOL ). Can possibly try a BIOS update on motherboard but depends on what fixes said update resolves.

2. Latest NIC Drivers ( and NIC has to support WOL )

3. Correct settings applied to said NIC in windows ( once drivers are up to date )

[twin--turbo]

Realy, the windows driver should have nothing to do with it. Other than perhaps enabling a function the bios can't see (sometimes the case).

 

You should be able to wake from all S1-5 states, but S5 is the power down state where the machine will boot a fresh instance of the operating system rather than restoring a previous session.

 

Rob

[mac_shinobi]

Realy, the windows driver should have nothing to do with it. Other than perhaps enabling a function the bios can't see (sometimes the case).

 

Rob

 

Like you said with regards to the driver - although I just update said driver if there is a later version of it available from the original manufacturers website so if it is an Intel NIC I go to the intel website and download the driver from Intel not the driver from stone / dell / hp etc as although it may work from stone / hp / dell or whoever at least if I get it from Intels website, I know intel made the card and hence the driver so it should be the correct and original driver intended for said card or device.

[sted]

how were the pcs turned off ive found that if they werent shut down properly (ie not just holdng down the power button/yanking out the cord) that wake on lan fails to unction (same sometimes goes if they have been off at the plug so say been moved after a propper boot up shutdown it works again)

[russdev]

Realy, the windows driver should have nothing to do with it. Other than perhaps enabling a function the bios can't see (sometimes the case).

 

You should be able to wake from all S1-5 states, but S5 is the power down state where the machine will boot a fresh instance of the operating system rather than restoring a previous session.

 

Rob

 

Your are sort of right and not as well and is a common misconception even by me until I started working at Impero.

 

Drivers play a massive part in this (based on diagnosing WOL issues for past 12 months). The reason is that WOL on pure function is hardware however the invention on power management functions on a network card that interact at hardware level plus some driver updates also do firmware updates as well if running default drivers that come installed with OS you are going to run into issues with WOL this more case with Windows 7 than Win Xp.

 

If it is number one cause of WOL not working on calls to the Impero helpdesk.

 

Russell

[twin--turbo]

how were the pcs turned off ive found that if they werent shut down properly (ie not just holdng down the power button/yanking out the cord) that wake on lan fails to unction (same sometimes goes if they have been off at the plug so say been moved after a propper boot up shutdown it works again)

 

I found something similar but I can't remember the details, had something to do with a difference between the soft power button and Start>Shutdown IIRC.. But it was 2 years ago that I was doing the testing and not done so since..

 

Rob

[russdev]

I found something similar but I can't remember the details, had something to do with a difference between the soft power button and Start>Shutdown IIRC.. But it was 2 years ago that I was doing the testing and not done so since..

 

Rob

 

Here is paste from part of a document created a while go to help support guys diagnose these issues as said number 5 is most common cause of WOL issues.

 

1. Make sure that WOL is enabled in the BIOS

2. Check that ACPI enabled in the BIOS.

 

Please note that Microsoft® Windows® XP should be installed on systems with ACPI enabled in the BIOS. Systems which do not support ACPI or are set to APM in the BIOS may not work correctly. If your system is set to APM, you must change this to ACPI and rebuild the workstation - you cannot simply change the setting without re-installing Windows.

 

 

3. Make sure that the computer is powered in some way for example turned off but plugged into the mains supply.

4. Check to see if the system is alive even when powered off by checking that both the network card and the hub/router link light are flashing.

5. Check the drivers of network card are the latest manufactures network drivers and not the default ones from the operating system.

 

Check that within Windows that the network adapter has been configured to allow WOL.

Check in Control Panel - System - Hardware - Device Manager - (select network adaptor) - Properties - Advanced.

6. Some computers must be powered up before they will respond and they have to be correctly shutdown in a controlled manner. For example if you disconnect the mains supply, you must reconnect the mains supply and power up the system at least once.

 

Russell

[Ashm]

Realy, the windows driver should have nothing to do with it. Other than perhaps enabling a function the bios can't see (sometimes the case).

 

I used to think exactly the same thing but I've had WOL issues in the last year and found that changing the network drivers solves the issue with two types of PCs I've had the problem with. It's strange because with the old driver that caused WOL not to work everything else worked perfectly except WOL.

[twin--turbo]

In reality it's not the driver, it can't be as that's never in play at boot.

 

However the hardware is not being fully controled by the bios and is needing software input to config the card..

 

Linux has some support to enable the options.

 

Some NICs can be set to boot from WOL even after total power failure.

 

As usual, the "STANDARD" is open to vast differences in it's interpretation.

 

We once had it working nicely for our fully automated re-image solution on zenowrks, but changing one thing made it all fall appart.

 

Surely they can come up with a simple one stop solution for this, but I think that there is no consumer power to drive a solution out of the vendors.but i guess it's way down the priority list for all vendors and unless one says "Lets Get it right" then it will never be 100% reliable.

 

Rob

[sjatkn]

We have the same machines and found that with newer drivers (not quite the latest at the moment) WOL works find after you set it. Our problem is getting the WOL settings to be enabled after SysPrep in XP. I really must try the latest drivers to see if there is an option to set it at install time, I seem to remember that being their is a different Intel LAN driver.

[bodminman]

We had this same board and found that out of the box the BIOS was several updates behind so please make sure this has been updated.

 

Also just as a test, can you boot the PC up and try booting to LAN. At the same time have a look at the lights on the NIC. Are both staying on and flashing or is just one light on or at the point of selecting LAN are the lights going out?

 

I ask this because we had an issue similar to this and at the point of hitting F12 to boot to LAN the lights on the NIC would go off. In a nutshell it was a cabling issue and once we addressed this the PC booted to LAN etc fine.

 

Different fault but it maybe the same solution!

[newpersn]

I updated the bios and the nic driver then tested my computer from home. It worked. But i will test it on 52 computers this week.