Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[pookeyhead]

All connected devices are static, and DHCP is off on the router.

I will try the second NIC on the server later and report back.

[ironic77]

Pookey,

Don't know if you tried powercfg -LASTWAKE.  Sorry I didn't include more info.

If it is a network event, you should see something like this:

Wake History Count - 1
Wake History

  Wake Source Count - 1
  Wake Source

    Type: Device
    Instance Path: blah blah blah
    Friendly Name:
    Description: Network card
    Manufacturer: Manufacturer

[Cobra]

All connected devices are static, and DHCP is off on the router.

I will try the second NIC on the server later and report back.

Try a different port on the router as well.

[lotacus]

it was suggested in your NIC properties to disable WOL which isn't the solution your looking for, however, your NIC may have two WOL options? Wake On Pattern Match and Wake on Magic Packet? if so, just disable the Pattern Match option. However to wake your computer up now you my need a method to send a magic packet to the server.

[pookeyhead]

Pookey,

Don't know if you tried powercfg -LASTWAKE.  

It doesn't give any information away at all.

................ if so, just disable the Pattern Match option. However to wake your computer up now you my need a method to send a magic packet to the server.

Exactly...   I don't want to be messing around with programs to send a magic packet.  I just want to be able to click on the mapped network drive, and it wakes up.

[pookeyhead]

Tried every other ethernet socket on the router.  Problem persists.

[Cobra]

There are other options in the command powercfg that you can use to make sure it is not the OS sending something to wake the computer.

powercfg /?

That will show you a list of all things you can do or monitor.

[lotacus]

You could always run wireshark and do a packet capture.

[pookeyhead]

Ok..  run wireshark

I stopped the trace as soon as the server woke up.



The server is on 192.168.0.4

Looks like it it's the server's ARP broadcast that's waking it.

Now what do I do?  LOL

Can't edit ARP table...  grrrr


Is there a way I can filter that somehow?

[lotacus]

Hmm. don't think there is a way unless you have another switch and put the computer behind the switch. At least in theorty, then the router would broadcast the who has 192.168.0.4 and the switch would pick it up and check it's address table and send the reply  back without ever touching your server. But that's just a work around of course and doesn't solve the issue itself directly.

The only other way would be to set static arp entries in the 655 itself, which we are unable to do. I'll check into something else that may help solve the problem.

[pookeyhead]

Thanks pal!  Any help appreciated.

Putting the server behind a switch would be OK, as I need to add a switch at some point, as all 4 ports are used on the DIR-655 now (my rig, wife's rig, server and a NAS box).

[grewy]

Hi guys.

This is a great thread. I am having the exactly same problem with two different friends i am supporting.

Both their setup:
Windows 7 OS - D-Link 655 router.
No router - server sleeps fine
Only router and server - server keeps waking up.

This seems to be a general problem with the 655 router(and perhaps other?).

I really look forward to following this thread to find a solution, and perhaps even hear some comments from D-Link on this issue.

[EddieZ]

If I remember correctly, there must be a setting to disable broadcast, since all my W7 systems go to sleep without problem.

OK, let me see....

Under DHCP Server Settings there is a setting Always broadcast. Is this checked or unchecked?

[lotacus]

That's what I was thinking might help.

[brianvigh]

Hey
I have the same problem and have just tried and disabled the always broadcast but with no luck.
I have 2 machines and they both turn on within 30 seconds after the suspend.