Wake on LAN/directed packet - waking too much!

I'm using an Intel DG965WH motherboard as the basis for a loft-based server. The onboard Gigabit NIC is an Intel 82566DC Gigabit Ethernet Controller, and I have the latest Intel Proset XP drivers installed...

Now, to the problem .

I want this machine to wake from S3 standby on attempted access to any of its files (i.e. not "traditional" WOL via Magic Packet) - Intel's wording for this is "Wake on directed packet" and, when this is selected under the "Power Management" tab on the Ethernet Controller's driver pages, that's exactly what it does; try to access a previously active share on the machine when the machine is in S3 and it powers up. However...

Under XP's general Power Management stuff I have the machine set to sleep after 10 minutes, which it does, but it won't stay asleep even if there are no other machines active that are mapped to its network shares i.e. there shouldn't be any packets directed to it to wake it up/keep it awake but, nonetheless, it does wake up. Similar story if I put it directly into standby, it usually comes out of standby after 20 seconds or so...

Looking at the networking logging stuff as part of the Windows firewall...

My router is on the usual 192.168.1.1, and the machine in question has a fixed IP of 192.168.1.103. Is this something to do with my router pinging the machine in question and waking it up? In the log I see entries like this:

2007-06-19 10:30:12 OPEN-INBOUND TCP 192.168.1.1 192.168.1.103 5541 2869 - - - - - - - - -
2007-06-19 10:30:12 OPEN-INBOUND TCP 192.168.1.1 192.168.1.103 5542 2869 - - - - - - - - -
2007-06-19 10:30:12 OPEN-INBOUND TCP 192.168.1.1 192.168.1.103 5544 2869 - - - - - - - - -
2007-06-19 10:30:12 OPEN-INBOUND TCP 192.168.1.1 192.168.1.103 5545 2869 - - - - - - - - -

Although I can't say whether these are related to the wake-up up or not as, ehh, I guess they're logged after the machine has woken up .

Googling around I've found mention of a "Only allow management stations to bring the computer out of standby" setting, that suggests it might prevent random pings from waking the machine, but the Intel Proset driver doesn't seem to supply this option, and elsewhere I've found that this limits operation to direct and explicit "Magic Packet" only, which I'm not interested in...

Is it possible to use "Wake on Directed Packet" in the way I'm expecting to use it i.e. just wake when an attempt is made to access a previously shared file/folder, but not waking up all of the time as a side-effect? I want something automatic (hence not Magic Packet) and had based my server idea around this working...at the moment though, it's in a continual wake/sleep/wake/sleep cycle...

I guess "Wake on Directed Packet" isn't something that many folk use then? To me it seemed an ideal way of building a server/NAS that would wake-up when accessed, but sleep when inactive...now I'm not so sure.

I've made a small bit of progress in that I've found if you pull the network cable the machine it will quite happily go to sleep as-per the Power Scheme settings. If you then re-connect the cable it doesn't wake up directly, and does just wake when an attempt is made to ping-it/access a previously open share on it - so that's kind of good.

The problem I'm having is getting the machine to sleep after a period of inactivity, with the network cable attached, without waking itself up again within 1-30 seconds, leading to a continual sleep/wake/sleep/cycle.

I'm currently suspecting that the router might be "pinging" the machine just after it goes to sleep, and hence waking it, but there's no diagnostic logs on the router itself to trace this... I've tried both Ethereal and Microsoft Network Monitor on a different machine on the network to try and see what's going on with the network at the time it wakes up, but nothing seems to be conclusively going towards the machine in question (at least I'm not seeing it).