impero wol issue

[dalehopper]

Morning edugeeks, just trying to get some answers or to see if any persons have had similarities with an issue i'm experiencing regarding using WOL via impero.

 

Basically i start the machines up and they stall/crash/pause at the BIOS boot screen i have to manually press the restart switch, it's all very odd!

 

Its only happened in the last release or possibly the one before, old releases used to work fine.

 

All settings (are as the were) are correct in the BIOS, on-board intel network adapter drivers are up-to-date and all setting enabled in the Power management tab, even tried powering machines on using a different port in impero (7 rather than 9)

 

Cant get on impero's support forum so though id ask here first???

 

I must add that it doesn't happen on every computer but the majority (looked for differences in the settings of working and non-working pcs, but nothing that i can see)

 

many thanks

Dale

[dalehopper]

@russdev any ideas?

[russdev]

Strange if starting up and then crashing means getting wol packet. After that bios takes over my best guess is network drivers as this has lot of effect on wol (if using default drivers) due to how they power save, firmware and all sorts..

 

Russell

[ZeroHour]

Does a normal WOL tool work successfully?

There are a number of free ones out there you can test. Its possible a Windows Update borked it as they can sometimes embed microcode updates for various processors etc.

[dalehopper]

thanks for your comments fellas but it works fine using a free WOL tool so the suggestion is its impero

[Steve21]

There are some issues with certain motherboards/BIOSs that if you receive multiple WOL attempts within a set frame they'll crash and hang

 

So it might be that Impero sends a few at once, and the other tool does a single one? Maybe @russdev can confirm?

 

Steve

Edited August 6, 2015 by Steve21

[dalehopper]

that sounds about right @Steve21 from what ive seen anyway

 

as i said earlier, it used to work with impero

Edited August 6, 2015 by dalehopper

[russdev]

I think you hit the nail on the head there... We did make a change around that a few releases back. I am currently out the office but will check when get back in and update the thread etc...

 

If got an example of a board might be useful..

 

Russell

Edited August 6, 2015 by russdev

[dalehopper]

@russdev can tell you that the onboard NIC is a Intel 82578DC gigabit adapter

 

if there was an impero setting say (send 1 packet or multiple) i could test it out

[Steve21]

@russdev can tell you that the onboard NIC is a Intel 82578DC gigabit adapter

 

if there was an impero setting say (send 1 packet or multiple) i could test it out

 

Same theory should work if you for example open 4 of your WOL test programs and hit them quickly together But obviously depends on the exact specifics, so might be easier to wait if it's not a huge problem

 

Steve

[dfergusson]

We have this issue also, only effect three computer models we have.

 

RM CC4 wol would do this, and as listed above free wol tool available doesn't do this.

 

Had no issue originally with Impero when we got it last year, but started to see this issue again with Impero in last 6 months.

Nice to know that I'm not alone with this issue, hope to see work around with Impero.

Edited August 6, 2015 by dfergusson

[Joh619]

I've seen a similar issue on an RM One before but a BIOS update fixed it.

[dalehopper]

interestingly a newer driver has fixed the issue for some of the computer also, many thanks