Print

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

[kthaddock]

pookeyhead

Have you setup: "Wake-On-LAN" on VIRTUAL SERVERS LIST


kthaddock

[pookeyhead]

I just tried that now.  It made no difference.

I assumed that was to allow WOL from outside the local network though.  Is it not?

[pookeyhead]

Ok..  I put the server behind a switch....   but the switch just forwards the ARP request...  it still wakes up.


Oh well...  I guess that's pretty much everything tried now.


I'd love to know the reasoning behind a ARP broadcast every minute. 


Can I suggest a means to edit the ARP table in future models please D-Link?..  not that I'll be buying one...


Anyone wanna buy a DIR-655? LOL

[kthaddock]

Have you tried to disable:

Dynamic IP (DHCP) Internet Connection Type : Use Unicasting : (compatibility for some DHCP Servers)

DHCP Server Settings : Always broadcast: (compatibility for some DHCP Clients)


I may worth to try !

kthaddock

[HenryJohn2000]

Hi, pokeyhead if you still have the same problem I found a workaround on another forum.
Simply change network setting to "public". This solved my problem at least. I'm runing win7 with a 88E8056 Marwel Yukon Gbit networc card.

Anny tech savy persson who might be able to explain why this solved the waking up after 30 sek problem for me so we might really get to the bottom of this. What settings on the network card for example changes when you change it to public?

[Alexandero2]

Hi,

I just joined to tag into this thread.  I'm having the same issue, except, it seems to occur in waves.

I'll have the Server sleeping for days at a time and only waking when I need to use it (ie. I access the network drive).  It'll go back to sleep once inactive and no funny behaviour.

But then, on some weird random chance, it'll wake up on its own.  When it does, I get the exact same behaviour as Pooky, where even if I try putting it back to sleep, it stays for about 30 seconds and then comes right back up again.  Much like Pooky, I have verified and isolated any other variables and can advise that it is the router that's sending a signal (as proved a couple of posts ago).

I've sometimes ignored it and after a day or so, the odd behaviour stops but it tends to re-occur every so often.  I'm going to try setting the network to "Public" as the previous poster suggested, but I'm somewhat skeptical of that solution as it doesn't seem to make any sense.  The alternative, of course, as mentioned is to set WOL to only occur with Magic Packets.   But that tends to defeat the purpose with devices that can't send Magic Packets (I'm crossing my fingers that the squeezebox Duet I ordered can)

Anyways, my apologies for the long post, will report back tonight.

[Alexandero2]

Well, of course, I get home today and its sound asleep.  I will post back again when it starts acting up and see if the "Public" setting makes a difference at all.

[Alexandero2]

Well, I'm back.   

As it would happen, my server started acting up again today and wouldn't stay "Sleeping" (in S3) for more than 30 seconds.  I tried the suggestion from a poster above to go change the Network type to "Public" (from "Home") and somehow, I don't know how, it works.  It stays asleep.

I tried tinkering a little with the Advanced Settings before changing to "Public" to try and discover what the difference is.  Upon some reading, the primary difference appears to be "Network Discovery", as it states that under "Public" it disables network discovery.  Simply turning this feature off under "Home" doesn't seem to have the same effect as switching to "Public" as my server exhibited the same behaviour (ie it kept waking via the PCIe LAN).

To make sure it wasn't a fluke, I kept toggling back and forth between "Home" and "Public" and without fail, "Public" always kept the computer asleep.  I'm not sure what the difference is but it works, for whoever has the same issue, I highly recommend trying it out.  If anyone figures it out, I'd love to hear the explanation.

[Alexandero2]

Ok, *sigh*, I'm sorry to keep bringing this up but I'm just documenting my findings in the spirit that it may help someone else (as this thread did help me).

One thing I should note from my above post.  Setting the network as "Public" (I should also mention, I'm doing this all under Windows 7) will disable file sharing with other PCs by default.  Meaning, in my case as I'm dealing with a server, I obviously need to allow other PCs access to the HDDs.

To re-enable it, go under the "Advanced" settings an turn on "File and Printer Sharing".  That's all you need to do and file sharing is re-enabled under "Public".

[kricker]

I've had problems with the DIR-655 waking PCs that have "Directed Packet enabled" as well. I've managed 4 of these router at various locations and all of them exhibited this behavior. I never knew it was the ARP requests causing this until stumbling on this thread a little while back. I tried changing the Windows 7 PCs to a Public Network, but they still get woken up by ARP requests.

While Googling I found this tidbit from MS:

One kind of special data packet contains a wake-up pattern. By default, Windows 7 and Windows Vista listen for the following packets when you enable WOL:
A directed packet to the MAC address of the network adapter
A NetBIOS name resolution broadcast for the local computer name
An Address Resolution Protocol (ARP) packet for the IPv4 address of the network adapter
An IPv6 Neighbor Discovery packet for the network adapter's solicited-node multicast address

I also found this little nugget:

ARP offload. ARP offload is the ability of the network adapter to respond to an IPv4 ARP request without waking the computer. Both the hardware and the driver must support ARP offload to enable this feature.

[kricker]

I entered the follwing at a command prompt:

>netsh interface ipv4 show interfaces

Idx     Met         MTU          State                Name
---  ----------  ----------  ------------  ---------------------------
  1          50  4294967295  connected     Loopback Pseudo-Interface 1
 11          10        1500  connected     Local Area Connection

This showed the Index number for my Adapter.

Then I issued the following command:

>netsh interface ipv4 set interface 11 forcearp=disabled

This I hope prevents the adapter from waking by ARP requests. A quick test proved promising. I will do some further testing to make sure though.

EDIT:
That appears to NOT have worked. DANG!