Automatically wake W7 PC for fileshares/remote desktop/etc without “magic packet”Windows 7 Pro Computer...
How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?
Why are only specific transaction types accepted into the mempool?
What is the offset in a seaplane's hull?
Representing power series as a function - what to do with the constant after integration?
Can a German sentence have two subjects?
Can I interfere when another PC is about to be attacked?
Shell script can be run only with sh command
What defenses are there against being summoned by the Gate spell?
Pronouncing Dictionary.com's W.O.D "vade mecum" in English
How do I create uniquely male characters?
Why is the design of haulage companies so “special”?
Why CLRS example on residual networks does not follows its formula?
Why was the small council so happy for Tyrion to become the Master of Coin?
Why can't I see bouncing of a switch on an oscilloscope?
How can bays and straits be determined in a procedurally generated map?
Is it possible to do 50 km distance without any previous training?
TGV timetables / schedules?
How long does it take to type this?
How did the USSR manage to innovate in an environment characterized by government censorship and high bureaucracy?
How to add power-LED to my small amplifier?
Disadvantages of online checking accounts?
A function which translates a sentence to title-case
Japan - Plan around max visa duration
Can an x86 CPU running in real mode be considered to be basically an 8086 CPU?
Automatically wake W7 PC for fileshares/remote desktop/etc without “magic packet”
Windows 7 Pro Computer won't wake on LAN via Magic Packet from outside networkWake on Lan works from LAN but not WANWake on LAN to specific requests (ports?)Wake On Lan works w/ Magic Packet But Not w/ Network ActivityWhat packets other than the “magic packet” can wake up the PC?Windows 10 identify wake from sleep ethernet sourceWake on Lan doesn't work on wanHow to prevent immediate wake ups when using Wake On Phy / Unicast?IGMP and Wake On LanMagic Packet Waking wrong computer “Wake on Lan”
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'd like to store all my media (photos/images/videos/music) on a shared network drive on my media PC (hooked up to the TV, it's not often used) for everyone in my home to use, however I'm edgy about leaving it on 24/7 so people can access it.
I tried disabling the "Only allow a magic packet to wake this computer" check box so it would respond to network traffic, but it seems my router (or something on the network) wakes the computer back up almost immediately. powercfg confirms this, is there a way to find a balance here without having to manually send a magic packet? I'd prefer it if it turned on for traffic, but that doesn't seem to be doable with the E3000 router I have.
Would it be more worthwhile to just let it run all the time? It is just a P4 stripped down to the motherboard and hard drives, but I'd prefer it went to sleep when it wasn't working, which to be fair is 90%+ of the day...
windows-7 wake-on-lan
add a comment |
I'd like to store all my media (photos/images/videos/music) on a shared network drive on my media PC (hooked up to the TV, it's not often used) for everyone in my home to use, however I'm edgy about leaving it on 24/7 so people can access it.
I tried disabling the "Only allow a magic packet to wake this computer" check box so it would respond to network traffic, but it seems my router (or something on the network) wakes the computer back up almost immediately. powercfg confirms this, is there a way to find a balance here without having to manually send a magic packet? I'd prefer it if it turned on for traffic, but that doesn't seem to be doable with the E3000 router I have.
Would it be more worthwhile to just let it run all the time? It is just a P4 stripped down to the motherboard and hard drives, but I'd prefer it went to sleep when it wasn't working, which to be fair is 90%+ of the day...
windows-7 wake-on-lan
add a comment |
I'd like to store all my media (photos/images/videos/music) on a shared network drive on my media PC (hooked up to the TV, it's not often used) for everyone in my home to use, however I'm edgy about leaving it on 24/7 so people can access it.
I tried disabling the "Only allow a magic packet to wake this computer" check box so it would respond to network traffic, but it seems my router (or something on the network) wakes the computer back up almost immediately. powercfg confirms this, is there a way to find a balance here without having to manually send a magic packet? I'd prefer it if it turned on for traffic, but that doesn't seem to be doable with the E3000 router I have.
Would it be more worthwhile to just let it run all the time? It is just a P4 stripped down to the motherboard and hard drives, but I'd prefer it went to sleep when it wasn't working, which to be fair is 90%+ of the day...
windows-7 wake-on-lan
I'd like to store all my media (photos/images/videos/music) on a shared network drive on my media PC (hooked up to the TV, it's not often used) for everyone in my home to use, however I'm edgy about leaving it on 24/7 so people can access it.
I tried disabling the "Only allow a magic packet to wake this computer" check box so it would respond to network traffic, but it seems my router (or something on the network) wakes the computer back up almost immediately. powercfg confirms this, is there a way to find a balance here without having to manually send a magic packet? I'd prefer it if it turned on for traffic, but that doesn't seem to be doable with the E3000 router I have.
Would it be more worthwhile to just let it run all the time? It is just a P4 stripped down to the motherboard and hard drives, but I'd prefer it went to sleep when it wasn't working, which to be fair is 90%+ of the day...
windows-7 wake-on-lan
windows-7 wake-on-lan
edited 2 days ago
Hennes
59.4k793144
59.4k793144
asked Oct 18 '11 at 4:57
Jane PandaJane Panda
62441028
62441028
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you disable "only allow magic packet" then any traffic at all will wake the computer, and networks will have chatty packets flying around no matter what.
So you'll have to control what packets actually land on the interface that can trigger the wakeup. Something like a firewall in between the router and the server that only permitted targetted packets through to the server - so no broadcasts. If there are other Windows machines on the network they might try to contact it directly too, so tuning the rules may take some trial and error - block ports 139/tcp 137/udp and 137/tcp.
The firewall needn't be complex, if you have an old router lying around that has wan/lan interfaces, you could install dd-wrt or similar on it and set up the firewall rules with it.
This would add an extra routing hop in your network though which increases the complexity you have to deal with.
The other thing you might consider is lots of bios's will support a wake up at a specific time. So if there are times of day (such as night) where the PC is always off, then you could schedule a suspend in Windows, and a wake-up in the morning via the bios. The wakeup time can often be set from Windows with the right utility, which means you can have different wake/sleep schedules on different days.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f347719%2fautomatically-wake-w7-pc-for-fileshares-remote-desktop-etc-without-magic-packet%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you disable "only allow magic packet" then any traffic at all will wake the computer, and networks will have chatty packets flying around no matter what.
So you'll have to control what packets actually land on the interface that can trigger the wakeup. Something like a firewall in between the router and the server that only permitted targetted packets through to the server - so no broadcasts. If there are other Windows machines on the network they might try to contact it directly too, so tuning the rules may take some trial and error - block ports 139/tcp 137/udp and 137/tcp.
The firewall needn't be complex, if you have an old router lying around that has wan/lan interfaces, you could install dd-wrt or similar on it and set up the firewall rules with it.
This would add an extra routing hop in your network though which increases the complexity you have to deal with.
The other thing you might consider is lots of bios's will support a wake up at a specific time. So if there are times of day (such as night) where the PC is always off, then you could schedule a suspend in Windows, and a wake-up in the morning via the bios. The wakeup time can often be set from Windows with the right utility, which means you can have different wake/sleep schedules on different days.
add a comment |
If you disable "only allow magic packet" then any traffic at all will wake the computer, and networks will have chatty packets flying around no matter what.
So you'll have to control what packets actually land on the interface that can trigger the wakeup. Something like a firewall in between the router and the server that only permitted targetted packets through to the server - so no broadcasts. If there are other Windows machines on the network they might try to contact it directly too, so tuning the rules may take some trial and error - block ports 139/tcp 137/udp and 137/tcp.
The firewall needn't be complex, if you have an old router lying around that has wan/lan interfaces, you could install dd-wrt or similar on it and set up the firewall rules with it.
This would add an extra routing hop in your network though which increases the complexity you have to deal with.
The other thing you might consider is lots of bios's will support a wake up at a specific time. So if there are times of day (such as night) where the PC is always off, then you could schedule a suspend in Windows, and a wake-up in the morning via the bios. The wakeup time can often be set from Windows with the right utility, which means you can have different wake/sleep schedules on different days.
add a comment |
If you disable "only allow magic packet" then any traffic at all will wake the computer, and networks will have chatty packets flying around no matter what.
So you'll have to control what packets actually land on the interface that can trigger the wakeup. Something like a firewall in between the router and the server that only permitted targetted packets through to the server - so no broadcasts. If there are other Windows machines on the network they might try to contact it directly too, so tuning the rules may take some trial and error - block ports 139/tcp 137/udp and 137/tcp.
The firewall needn't be complex, if you have an old router lying around that has wan/lan interfaces, you could install dd-wrt or similar on it and set up the firewall rules with it.
This would add an extra routing hop in your network though which increases the complexity you have to deal with.
The other thing you might consider is lots of bios's will support a wake up at a specific time. So if there are times of day (such as night) where the PC is always off, then you could schedule a suspend in Windows, and a wake-up in the morning via the bios. The wakeup time can often be set from Windows with the right utility, which means you can have different wake/sleep schedules on different days.
If you disable "only allow magic packet" then any traffic at all will wake the computer, and networks will have chatty packets flying around no matter what.
So you'll have to control what packets actually land on the interface that can trigger the wakeup. Something like a firewall in between the router and the server that only permitted targetted packets through to the server - so no broadcasts. If there are other Windows machines on the network they might try to contact it directly too, so tuning the rules may take some trial and error - block ports 139/tcp 137/udp and 137/tcp.
The firewall needn't be complex, if you have an old router lying around that has wan/lan interfaces, you could install dd-wrt or similar on it and set up the firewall rules with it.
This would add an extra routing hop in your network though which increases the complexity you have to deal with.
The other thing you might consider is lots of bios's will support a wake up at a specific time. So if there are times of day (such as night) where the PC is always off, then you could schedule a suspend in Windows, and a wake-up in the morning via the bios. The wakeup time can often be set from Windows with the right utility, which means you can have different wake/sleep schedules on different days.
answered Oct 18 '11 at 5:17
PaulPaul
48.6k14122150
48.6k14122150
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f347719%2fautomatically-wake-w7-pc-for-fileshares-remote-desktop-etc-without-magic-packet%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown