D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: pookeyhead on January 17, 2010, 05:45:01 AM
-
As the title suggests, I'm having trouble keeping my server asleep. I've been thorough in my process of elimination, and have narrowed it down the DIR-655.
I am trying to get my server to go to sleep after say, 30 mins.. and stay asleep until either me, or my wife try to access a file on it. However, it wakes up around 30 seconds after going into sleep... every time.
I've disconnected everything else from the network, and it still does it.
I've disconnected my modem from the router, thus having no WAN access, and it still does it.
No other software is running on the server that is waking it up.
No tasks are running that can wake it up.
However, if I pull the ethernet cable from the back of the rig, it sleeps just fine.
I've disabled DHCP as all machines have a static IP.
I'm at a loss as to what else to do now. Clearly the router is broadcasting something that keeps the server awake.
Any suggestions?
I hope so, otherwise the DIR-655 goes into the trash. I need the server to sleep when not required.
-
However, if I pull the ethernet cable from the back of the rig, it sleeps just fine.
You answered your own question.
You need to go into device manager > network adapter > power management
Disable any "wake the computer" or "wake on magic packet".
-
You answered your own question.
You need to go into device manager > network adapter > power management
Disable any "wake the computer" or "wake on magic packet".
Errr... then it would never wake on LAN LOL
You didn't read my post fully did you :)
I WANT it to wake on LAN... when the server is accessed. The problem I am having is that it will come out of sleep after 30 seconds for no damned reason. I want it to stay asleep until either myself, or my wife access the server.
-
Another thing that can cause this is mouse power management wake.
Wake on LAN is real flakey IMO so I just disable it.
-
Put the PC on standby, then immediately yank the cord. You'll be able to tell for sure if it's because of something that only runs when the network is hooked up.
Check the BIOS to see if wake-on-LAN is set to something like "any activity" too.
If that fails, you'd probably have the exact same problem no matter what network gear you use. Instead of putting it on standby, try dynamically clocking the cpu and northbridge down as much as possible with a tool like RMClock or CrystalCPUID, to minimize power draw. A small investment in quieter fans goes a long way if it's a living room PC, too.
-
It's already underclocked. It's a Celeron E3200 and it's running at 1.2GHz and heavily undervolted, but even so, I don't want it "on" when for 60% of the time it's not actually doing anything, especially as the LSI RAID card seems to lack provision for spinning the drives down.
I've pulled the ethernet cable as soon as it goes into sleep as you suggest. In fact, I've pulled it, rebooted, and then put it to sleep. There are no issues when there is no network cable attached, which makes me assume that it is not an issue with the server's hardware, with the Vista install, or the BIOS. The BIOS has very few settings for WOL anyway.
I've attached my DSL modem directly to my server just to see if having ANY network device attached causes this wake from S3 issue, but it stayed soundly asleep.
As soon as I connect it to the router, despite nothing else being connected to the router, it starts waking up 30 seconds after being put to sleep. This router is broadcasting something... anyone got any ideas what it could be? As stated earlier, DHCP is off.
Mouse and keyboard wake is disabled in the server's BIOS.. so that rules that out.
Does anyone from D-Link read these forums?
-
Try disabling UPNP in the advanced network settings of the DIR.
Also disable the "Multicast Streams"
-
Mouse and keyboard wake is disabled in the server's BIOS.. so that rules that out.
That is not always the case.
I have everything in bios related to WOL disabled in bios but until I disabled "allow this device to wake the computer" in device manager/mouse properties my PC would wake up without any interaction.
-
Thanks for the replies guys... greatly appreciated.
I've just got home after a 13 hour shift, so my priorities are: Food, Jack Daniels, sleep. In that order.
I'll give them all a go tomorrow and report back :)
-
I'm afraid none of the above worked :(
In fact, even if UPNP did work, it stopped Azureus from working, so that wouldn't have been a solution anyway.
Anyone else got any ideas?
-
I think what the problem is, is that it's sending out ARP messages.
There is a hidden setting in the firmware that you can access by pressing alt+v then y then n (view>style>no style)
You are able to disable WOL. Not sure if it will affect the internal network or if it's a WOL passthrough for waking the computer up outside the network.
You can access this configuration at http://dlinkrouter/Advanced/Firewall.shtml
It's a hidden setting under ALG Configuration.
I think someone else had a similar problem about a year ago and was able to solve it by forwarding the port used, to a non-existant IP address. Unless that was you and still was not able to solve the problem.
Unfortunatly I dont' know why it's happening because i have tested the WOL and it worked fine. Did you check any settings within the computers bios?
-
Yeah I've been through the BIOS with a fine toothed comb... but that doesn't mean I didn't miss anything.
If anyone more knowledgeable wishes to take a look, here's a link to the server's motherboard manual.
http://www.gigabyte.com.tw/Support/Motherboard/Manual_DownloadFile.aspx?FileType=Manual&FileID=19430
I'll try the other suggestions later.
Once again, thanks for trying to help.
David
-
If you're running Windows 7, try powercfg.exe utility. It will tell you exactly why the machine woke. If it is indeed networking, then you will probably want to sniff your network and look for the packet that caused the machine to wake.
In general, any directed packet (unicast directed to the machine itself) will wake the machine. Something as simple as a ping or ARP could cause it to become an insomniac.
I got so frustrated I just turned off WOL except magic packet. I just hit the machine with WOL tool if it's snoozing. I'm sure you and others can figure out the cause here, but it just wasn't worth it to me as I have bigger problems.
-
Did you disable mouse "allow device to wake computer" power management in device manager?
Optical mice sometimes wake PC for no reason.
-
Yes I did that... I've even pulled the mouse entirely.
I've not tested the "hidden" settings yet. Will do that when I get back from work.
-
I disabled WOL in that hidden menu by turning CSS off in my browser, and it's made no difference :(
Getting annoyed now. Who makes a router that makes it impossible for someone to use WOL on their network?
I've run powercfg to see what last woke it, and nothing is even listed!
I suppose I need to use something that sniffs out the packets on the network to see what's going on, but tbh, I'm not really knowledgeable enough to start getting in that deep.
What I feel like doing is taking my £100 router outside, pouring lighter fuel over it, and cremating it. Then buying one that actually works properly.
I'm also annoyed that this thread has been running for a week, always on page 1, and not a single person from D-Link has deemed it worthwhile to even venture a single comment.
I'd ask them myself if their support website actually worked properly!
I work hours that are outside of their phone helpline hours so I can't even do that. I'm just stuck with this useless white plastic, very expensive brick.
Last D-Link product I buy, ever.
Anyone from D-Link care to comment? LOL. After all, it's YOUR support forum.. I mean.. I don't want to put you to any trouble or anything.
In your own time D-Link.
Thanks to all that have tried to help, but I think it's time me and D-Link parted company.
-
After testing....Has to be something on the PC as I can use WOL without issue if I want to.
-
This is primarily a "users help Users" forum, not an official support channel. Just to manage your expectations, it's not their fault you work those hours of use a crippled browser. From my personal experience (yes they are all installed in my personal ET environment) the website works fine with: IE7/8, Opera 9/10, Chrome official and dev build, Apple Safari for Windows and FF 3.5/3.6 beta. Anything outside these mainstream browsers might cause issues with a lot more sites.
I've tested WOL too (even though I don't use it) and it works OK.
Possible culprits:
- the modem/internet gateway (which device does DHCP on your LAN?),
- Any virtual servers routed to the PC?
- the NIC that responds: because there's only limited user interaction features that does not mean the feature isn't there on the NIC. You can search for possible extra registry settings on the net.
- Any background process running on the PC? This will prevent many machines from going to sleep.
-
This is primarily a "users help Users" forum, not an official support channel. Just to manage your expectations, it's not their fault you work those hours of use a crippled browser. From my personal experience (yes they are all installed in my personal ET environment) the website works fine with: IE7/8, Opera 9/10, Chrome official and dev build, Apple Safari for Windows and FF 3.5/3.6 beta. Anything outside these mainstream browsers might cause issues with a lot more sites.
I've tried with Firefox 4.5 and IE8... it doesn't work.
I've tested WOL too (even though I don't use it) and it works OK.
Possible culprits:
- the modem/internet gateway (which device does DHCP on your LAN?),
- Any virtual servers routed to the PC?
- the NIC that responds: because there's only limited user interaction features that does not mean the feature isn't there on the NIC. You can search for possible extra registry settings on the net.
- Any background process running on the PC? This will prevent many machines from going to sleep.
Ok.. so nothing to do with this ******ed router making constant ARP broadcasts, and having no way to access the ARP table?
DHCP is disabled on everything, and everything has a static IP.
It's not the gateway... I've unplugged everything from the router except the server in question. There is nothing installed on the server whatsoever... except Vista. It serves no other purpose other than to.... errr.. serve :)
If it was the NIC waking the computer up, why does it only wake it up when the DIR-655 is connected to it?
Maybe only certain firmware has this problem. What version you using? I'm on 1.20EU.
I'm certainly not alone in this. It appears PS3 owners have been *****ing about this for some time.
More reading to be found at http://www.broadbandreports.com/forum/r21470560-Help-Me-DIR655-ACCESSING-ARP-TABLE
I mean.. I don't know what other methods I can employ to prove it's the router. I said early on in this thread I had connected the modem directly to the server to test this, and it goes into S3 fine... and stays there. That also rules out NIC problems.
I promise you it's the damned router.
I'm sorry if I seem harsh over the last couple of posts, and I do really appreciate all the suggestions I have has so far, but this isn't a cheap ass router, and I bought it because it was regarded by many of a decent piece of kit. However, for me, it's actually useless, because there's no way I can stand to have the server on all day when no one is in to use it... and no... I won't manually turn it off, and on when I leave/get home, because once I knowI can get it to drop into S3 reliably, it's going into the attic.
After testing....Has to be something on the PC as I can use WOL without issue if I want to.
LOL.. no it's not! It sleeps just fine when directly connected to the modem/gateway. It sleeps just fine when not connected to anything. What on earth makes you so sure it's the PC, when the ONLY time I have a problem is when it's connected to the DIR-655?
-
I can't help it that my PC's go to sleep without a problem, all connected to the DIR655. As does Cobra's...
So if it is the router I would appreciate an explanation why my PC's just go to sleep. No modifications on the router. SOo if the phenomenon is not generic your conclusion (or promise) is a bit premature, wouldn't you say?
And when I say modem/internet gateway: there must be a deivce that connects you to the internet (unless you have an ISP that delivers ethernet with RJ45 to your home). If that device triggers the DIR, well that would explain everything.
-
I can't help it that my PC's go to sleep without a problem, all connected to the DIR655. As does Cobra's...
So if it is the router I would appreciate an explanation why my PC's just go to sleep. No modifications on the router. SOo if the phenomenon is not generic your conclusion (or promise) is a bit premature, wouldn't you say?
And when I say modem/internet gateway: there must be a deivce that connects you to the internet (unless you have an ISP that delivers ethernet with RJ45 to your home). If that device triggers the DIR, well that would explain everything.
Well.. I did also ask you what firmware you have. Have you not considered that it may be an issue with a specific firmware version(s)?
Your logic (Mine doesn't do it, so therefore all routers must be OK) is a little flawed, when you consider that mine does.. and I only get the problem when the computer is connected to the router. I've also posted links to other forums where other people are having the same problem... twice, yet despite this, you're adamant that the router is fine, based on nothing more than "I have one and it's OK".
Also, I have mentioned TWICE now, that I am NOT connected to the internet in any way, shape or form when this happens. I have tested this.. it was one of the first things I did test.. many, many posts ago.
You ignore pertinent information, and adamantly drive home a point that I've already covered, and proved to be not so.
Despite your insistence... it IS the router.
After testing....Has to be something on the PC as I can use WOL without issue if I want to.
Same again. I own a Ford Mustang. I keep reading on Forums that there's a problem with the battery going flat after a couple of weeks of disuse. However, mine doesn't do it... so therefore.. the fault plainly doesn't exist and all these people must be imagining it.
Just LOL. I love this.... you can go through life convincing yourself that you, and everything you own is perfect. Thanks, I'll give that a go!
So... anyone who isn't a fanboi got any more ideas? Should I try a a different firmware?
[edit]
I've just read something interesting. That I can not flash back to an older Firmware version, and trying to can cause problems. Is this true?
I hope not, because I was going to go back to the original version the router came with to rule out firmware problems.
-
Once you go to a 1.3X firmware- you can not go down to a version below it. You can use any in the 1.3 family but no going below.
-
Just LOL. I love this.... you can go through life convincing yourself that you, and everything you own is perfect. Thanks, I'll give that a go!
So... anyone who isn't a fanboi got any more ideas? Should I try a a different firmware?
Why do you call me a fanboy?
Just because I can solve my problems and you can not?
I have solved problems with this router and other brands (many are on the networks I run not just home) and I have not found any I could not solve. Sometimes as easy as changing out an NIC. You do not want to listen to what people say as you are SURE it is the router.
If you are so damn sure it is the router then what you do is follow Lycans advice as he gives the phone#.
As far as I am concerned you can fix this problem yourself.
http://forums.dlink.com/index.php?topic=10620.msg62737#new
-
Once you go to a 1.3X firmware- you can not go down to a version below it. You can use any in the 1.3 family but no going below.
Thanks... I'll try going down a few versions just to rule out FW probs.
Why do you call me a fanboy?
Just because I can solve my problems and you can not?
No.. because you insist that I am mistaken in thinking it is the router, when I have clearly done everything logical, and everything asked of me to ascertain that it is; Despite the problem only occurring when the router is connected, and despite having nothing else connected - including my gateway/modem... and all this just because YOURS works... therefore MINE must work also. In addition, you insist it's not the router despite not even knowing what HW revision, or FW I'm running, which, in balance would have been pertinent information to request before arrogantly dismissing my enquiry.
Incidentally, this evening I dug out my old Netgear DG834, and guess what? Yep... server sleeps perfectly fine, and stays asleep until woken up.
If you wish to withdraw your help, then go ahead... because you've offered none so far anyway, other than asking me to disable WOL.. (duh)... disable mouse power management, and then after informing me that optical mice are flakey, established that the router is actually fine, and it's obviously my computer... despite all of the above.
Well... however will I manage without such sage advice?
-
If you wish to withdraw your help, then go ahead... because you've offered none so far anyway, other than asking me to disable WOL.. (duh)... disable mouse power management, and then after informing me that optical mice are flakey, established that the router is actually fine, and it's obviously my computer... despite all of the above.
Well... however will I manage without such sage advice?
I gave you a link to the last option you have but you are so busy with your smart remarks that you probably do not read everything.
I bet you did not even go to the link I provided which has the phone number you have to call for support. People here have done all they can so now it is time for you to get off your duff and call D-Link.
If they also feel it is the router they will give you a RMA then send you a new router.
-
I always read everything... unlike you, which is evident in your first reply to this thread.
However.. thank you for the link. I shall phone D-Link as soon as I am able.
I have just re-flashed to 1.31EU, which was released yesterday apparently. No change.
-
Well.. I did also ask you what firmware you have. Have you not considered that it may be an issue with a specific firmware version(s)?
Your logic (Mine doesn't do it, so therefore all routers must be OK) is a little flawed, when you consider that mine does.. and I only get the problem when the computer is connected to the router. I've also posted links to other forums where other people are having the same problem... twice, yet despite this, you're adamant that the router is fine, based on nothing more than "I have one and it's OK".
Also, I have mentioned TWICE now, that I am NOT connected to the internet in any way, shape or form when this happens. I have tested this.. it was one of the first things I did test.. many, many posts ago.
You ignore pertinent information, and adamantly drive home a point that I've already covered, and proved to be not so.
Despite your insistence... it IS the router.
Same again. I own a Ford Mustang. I keep reading on Forums that there's a problem with the battery going flat after a couple of weeks of disuse. However, mine doesn't do it... so therefore.. the fault plainly doesn't exist and all these people must be imagining it.
Just LOL. I love this.... you can go through life convincing yourself that you, and everything you own is perfect. Thanks, I'll give that a go!
So... anyone who isn't a fanboi got any more ideas? Should I try a a different firmware?
[edit]
I've just read something interesting. That I can not flash back to an older Firmware version, and trying to can cause problems. Is this true?
I hope not, because I was going to go back to the original version the router came with to rule out firmware problems.
Have you ever heard of a signature that's embedded in every post I make? Should give you a clear answer... But I have not had sleep issues throughout the whole 1.3x series.
If it is the router, yours might be defective. Firmware faults tend to be generic and since the digital world is really binary that means that if our common element (the firmware) is at fault, the issue should also arise with other users. If it doesn't there's another element in play that is not shared. Otherwise you've invented a new firmware: the adaptive AI firmware ;)
But try this test: PC connected wired to router, no other wires or wireless devices connected (not even WAN). Does the issue still occur?
The 1.3x firmware cannot be downgraded because of a new SDK that's locked into the kernel.
-
Yeah, I tried this a couple of posts back. I disconnected everything from the DIR655: All other computers, NAS boxes etc... and left only the server in question connected. I also disconnected the gateway from the DIR-655, so basically all that is left connected to the server, is the router... which in turn is connected to nothing else. Even the keyboard and mouse disconnected.
It still comes out of sleep every 30 seconds. I've timed this now.. it's dead on 30 seconds. From when it wakes up, I started a stop watch, and then immediately put it back to sleep. when the stop watch reaches 30 seconds, it wakes up.
If I disconnect the router from the server, it stays asleep just fine.
I'll be the first to confess that I'm not a network expert, but surely it's making ARP broadcasts at 30 second intervals?
The router is otherwise perfect. My back ups go from my main rig to the server at over 110MB/sec, almost maxxing out the LAN. It's reliable, cool, looks great... fantastic on every other respect, which is why I'm loathe to get rid of it.
I can't return it, because it's an old revision A2 model. I've had it for some time, but only very recently required WOL. It's out of warranty.
I've tried my old Netgear router, and that allows the server to sleep just fine, which is what makes me so certain it's nothing on the server causing this. I can't use this netgear router either, because I require the gigabit speeds, and the Netgear is 100Mbit... that's why I upgraded from that in the first place.
-
Yeah, I tried this a couple of posts back. I disconnected everything from the DIR655: All other computers, NAS boxes etc... and left only the server in question connected. I also disconnected the gateway from the DIR-655, so basically all that is left connected to the server, is the router... which in turn is connected to nothing else. Even the keyboard and mouse disconnected.
It still comes out of sleep every 30 seconds. I've timed this now.. it's dead on 30 seconds. From when it wakes up, I started a stop watch, and then immediately put it back to sleep. when the stop watch reaches 30 seconds, it wakes up.
If I disconnect the router from the server, it stays asleep just fine.
I'll be the first to confess that I'm not a network expert, but surely it's making ARP broadcasts at 30 second intervals?
The router is otherwise perfect. My back ups go from my main rig to the server at over 110MB/sec, almost maxxing out the LAN. It's reliable, cool, looks great... fantastic on every other respect, which is why I'm loathe to get rid of it.
I can't return it, because it's an old revision A2 model. I've had it for some time, but only very recently required WOL. It's out of warranty.
I've tried my old Netgear router, and that allows the server to sleep just fine, which is what makes me so certain it's nothing on the server causing this. I can't use this netgear router either, because I require the gigabit speeds, and the Netgear is 100Mbit... that's why I upgraded from that in the first place.
Also tried a different LAN port? Sometimes one of the router ports can be flakey. The A2 does not have the 'green' LAN port management so that isn't it.
Be glad you have the A2, I consider it the best version looking at the hardware used ;)
And the ARP on the 655 is every 60 seconds if I remember well....
-
Is your server using a static IP address? Can you try turning off DHCP, and set your server for a static ip address and see if it wakes your computer?
-
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.
-
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
-
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.
-
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.
-
Pookey,
Don't know if you tried powercfg -LASTWAKE.
It doesn't give any information away at all. :(
(http://i16.photobucket.com/albums/b26/pookeyhead/name%20the%20car%20quiz/Untitled.jpg)
................ 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.
-
Tried every other ethernet socket on the router. Problem persists.
:(
-
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.
-
You could always run wireshark and do a packet capture.
-
Ok.. run wireshark
I stopped the trace as soon as the server woke up.
(http://i16.photobucket.com/albums/b26/pookeyhead/name%20the%20car%20quiz/Untitled-1-6.jpg)
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?
-
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.
-
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).
-
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.
-
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?
-
That's what I was thinking might help.
-
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.
-
pookeyhead
Have you setup: "Wake-On-LAN" on VIRTUAL SERVERS LIST ???
kthaddock
-
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?
-
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
-
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
-
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?
-
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.
-
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.
-
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.
-
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".
-
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 (http://support.microsoft.com/kb/941145):
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 (http://technet.microsoft.com/en-us/library/ee617165(WS.10).aspx):
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.
-
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!