|
Some people actually gave it 1 start...what the hell were they thinking?
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
Delivery charges? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Delivery charges from Rivendell at not cheap my friend.
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
Aye. The Eagles of the Misty Mountains have been raising prices steadily for a few years now.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Bah. The bastards have been outsourcing to a bunch of vultures that used to hang out in Mordor, led by some Nazgul wanna-be orc who got passed up for promotion.
Software Zen: delete this;
|
|
|
|
|
One does not simply outsource into Mordor.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I'm in love with my typewriter 
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Hello all,
We will try to use a remote connection to a computer in the office for a remote worker.
In order to do that we were planning to use any free VNC flavor or the same RDP that comes in Windows 7.
The problem with that is that we don't want the computer to be automatically started at a certain time as the idea is to give maximum flexibility to that remote worker.
So the goal is to allow the remote worker to start (wake on lan) remotely the computer.
I'm worried about the public IP changing each time the router gets disconnected.
And sending the WOL package through the Internet and the router (I guess this should be the easy part and would require only port forwarding).
Which kind of solution would you recommend?
Thank you all! 
|
|
|
|
|
Joan M wrote: So the goal is to allow the remote worker to start (wake on lan) remotely the computer.
..how much electricity does that thing eat?
Might not be worth the effort. Most of us in the office don't power down the machines when going home, to save some time starting it up in the morning.
Aight, being in a similar position where even the IP of my desktop at work can change during projects - I'd mail a coworker and ask them to turn the machine on.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
|
Any heavy object is, if required.
Even that hamster yonder.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Thank you Eddy,
It's not only the amount of electricity... I can see the situation: "it's saturday morning and I do need to finish that before Monday and o #$%& I've just shut the computer down without reason and now I can't work anymore..."
I've installed a dyndns-like service into the server, now it's only a matter of configuring the router and then it should be easy to send the WOL packet through internet.
Thanks!
|
|
|
|
|
A hammer
|
|
|
|
|
Nailed it.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Now I do need to figure how to send it through the router...
I've installed a dyndns-like service into the server, now it's only a matter of configuring the router and then it should be easy to send the WOL packet through internet.
Thanks!
|
|
|
|
|
I'm doing this for my box at home with only windows configuration and of course a firewall rule on my router.
I only allow my 1&1 virtual machine's fixed IP wake-on-lan packages through. This has worked flawlessly for the last four years. If the remote worker doesn't have a fixed IP you might just take the risk that the machine gets turned on involuntarily.
Cheers!
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
|
|
|
|
|
Thank Manfred,
I've installed a dyndns-like service into the server, now it's only a matter of configuring the router and then it should be easy to send the WOL packet through internet.
Thanks! 
|
|
|
|
|
I can only assume you're trying to save money? The RDP situation really requires a server to connect to IMO.
Jeremy Falcon
|
|
|
|
|
Thank you Jeremy,
It's not only the amount of electricity/money involved... I can see the situation: "it's Saturday morning and I do need to finish that before Monday and #$%& I've just shut the computer down without reason and now I can't work anymore..."
I've installed a dyndns-like service into the server, now it's only a matter of configuring the router and then it should be easy to send the WOL packet through internet.
Thanks!
|
|
|
|
|
Since you raise the question, and there seems to be lack of a suitable solution suggested, I would like to introduce our solution. It just for your information, if you don't like it, just ignore it.
We had developed a SOCK 5 based inter-LAN tunneling system that only requires the installation of a server software. It's under internal tests now and will be published online soon (for a while, since it's kind of complex on our side). We are happy with its performance at present ...
|
|
|
|
|
Thank you Shuquian,
I've installed a dyndns-like service into the server, now it's only a matter of configuring the router and then it should be easy to send the WOL packet through internet.
Thanks!
|
|
|
|
|
Yeah, I know this is a solution. But the process is a little involved, don't you agree?
In general, VPN type of solutions are not scalable ones since one must make sure each of the LAN connected LAN to have different private address ranges. Otherwise, the system will not know how to route a data package. On the other hand, most LANs are most likely to use the same default private address spaces (like 192.168.1.*, etc) during initial setup. So there is the problem of reset them consistently ...
It may not be a problem for your situation, but in general it is not a small issue in an organization in which the networks have already been setup.
|
|
|
|
|
|
  
Hi raddevus!
Impressive!
At the end though... I've installed a dyndns-like service into the server, now it's only a matter of configuring the router and then it should be easy to send the WOL packet through internet.
In my case the shut down will be performed by the remote worker so it won't be needed to control it auto-magically.
Thanks!
|
|
|
|
|
You could setup the router with DynDns so that you then have an address e.g. joansoffice.dyndns.info that will always point to the correct IP.
You can then do whatever port forwarding or WOL stuff you need on the router to push the magic packet in the correct direction.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
