I have three PCs which import data between two databases. When there is no data waiting, a server removes a file from a shared directory. The import PCs check the existence of this file and if it's not there they suspend themselves using the command 'rundll32 powrprof.dll,SetSuspendState'. The power settings in control panel are all set to 'always on'.
When data is waiting to be imported the server wakes the import PCs up using a WoL command.
This works fine on two of the PCs, but one of them goes back to sleep after a few minutes of being woken up. The only way to keep it awake is to move the mouse/press a key once it's been woken up via WoL.
I'm using a program called fullresume.exe to wake the PCs up fully once the WoL command is received, but this still isn't enough to keep this one PC awake.
All the PCs have different hardware so I'm guessing this particular configuration is causing this, but I've got no idea how to solve it! Just being able to view a log file with the reason it's gone back to sleep would be a start (nothing in event logs).
The PC in question is a Dell Optiplex 170L running XP Pro SP3 with all updates installed. The other two PCs that behave as expected are a much older Compaq and a slightly newer Dell.
Can anyone shed any light on this please?
Thanks in advance.
When data is waiting to be imported the server wakes the import PCs up using a WoL command.
This works fine on two of the PCs, but one of them goes back to sleep after a few minutes of being woken up. The only way to keep it awake is to move the mouse/press a key once it's been woken up via WoL.
I'm using a program called fullresume.exe to wake the PCs up fully once the WoL command is received, but this still isn't enough to keep this one PC awake.
All the PCs have different hardware so I'm guessing this particular configuration is causing this, but I've got no idea how to solve it! Just being able to view a log file with the reason it's gone back to sleep would be a start (nothing in event logs).
The PC in question is a Dell Optiplex 170L running XP Pro SP3 with all updates installed. The other two PCs that behave as expected are a much older Compaq and a slightly newer Dell.
Can anyone shed any light on this please?
Thanks in advance.