Start .exe from a Server with params
-
wuah :doh: again: I sit with my laptop in the sun, enjoy the sun :laugh: connect to network with vpn. Now I have a connectivity to the Server. I want to work Remote on my desktop pc from work. But the desktop pc is turned off. Now I want to start my desktop pc to connect to it! I start "starter.exe" and my desktop pc turns on. ----- Now how I realize this: I have 2 .exe 1. starter.exe is on my laptop 2. WOL.exe is on the server ----- Now how my tool works: starter.exe start the WOL.exe on the server with IP or MAC adress from my desktop pc as a parameter. WOL.exe sends a magic packet to desktop and this turns on! ----- Problem: starter.exe starts on my laptop starter.exe starts wol.exe which lay on the server but if starter.exe start wol.exe, wol.exe will be started on my laptop instead of the server. And cause my laptop is in an another subnet my laptop can not root packets directly. I hope this would help ;P
Mschauder wrote:
I hope this would help
Well you still seem to be saying: "I do this and it works". Then you say: "I do this and it does not work". So where are we? Let us go back to the original sequence.
- Laptop: run starter.exe (on the laptop)
- Laptop: starter.exe sends a message to the server with the IP address of the desktop
- Laptop: starter.exe terminates - its work is done
- Server: receives the message and runs wol.exe (on the server) with the desktop IP address as parameter
- Server: wol.exe sends a WOL message to the IP address of the desktop
- Server: wol.exe terminates - its work is done
- Desktop: receives WOL message and boots
- Laptop, Server and Desktop are now all booted and ready for action
Or maybe this is not what happens?
It's time for a new signature.
-
Mschauder wrote:
I hope this would help
Well you still seem to be saying: "I do this and it works". Then you say: "I do this and it does not work". So where are we? Let us go back to the original sequence.
- Laptop: run starter.exe (on the laptop)
- Laptop: starter.exe sends a message to the server with the IP address of the desktop
- Laptop: starter.exe terminates - its work is done
- Server: receives the message and runs wol.exe (on the server) with the desktop IP address as parameter
- Server: wol.exe sends a WOL message to the IP address of the desktop
- Server: wol.exe terminates - its work is done
- Desktop: receives WOL message and boots
- Laptop, Server and Desktop are now all booted and ready for action
Or maybe this is not what happens?
It's time for a new signature.
It doesn't work... I try to describe like you :P 1. Laptop: run starter.exe 2. Laptop: starter.exe start wol.exe with ip adress of the desktop 3. Laptop: starter.exe terminates now the problem begin 4. Because starter.exe runs wol.exe the wol.exe will run on the laptop... what should do: 4. Server: runs wol.exe 5. Desktop: boots 6. Laptop: connect to desktop and is ready for action --- for example sitting in school your neighbour looks bored then you start a program like media player and this program should pop up on HIS screen not yours! If I start media player (installed on his desktop pc) it will pop up on my screen, this I wouldn't have...
-
It doesn't work... I try to describe like you :P 1. Laptop: run starter.exe 2. Laptop: starter.exe start wol.exe with ip adress of the desktop 3. Laptop: starter.exe terminates now the problem begin 4. Because starter.exe runs wol.exe the wol.exe will run on the laptop... what should do: 4. Server: runs wol.exe 5. Desktop: boots 6. Laptop: connect to desktop and is ready for action --- for example sitting in school your neighbour looks bored then you start a program like media player and this program should pop up on HIS screen not yours! If I start media player (installed on his desktop pc) it will pop up on my screen, this I wouldn't have...
Mschauder wrote:
4. Because starter.exe runs wol.exe the wol.exe will run on the laptop...
Well this is obviously wrong. As I showed in my previous posts
starter.exeshould send a message to the server with the IP address, the server then runswol.exeto send the WOL message to the desktop machine.Mschauder wrote:
sitting in school your neighbour looks bored then you start a program like media player and this program should pop up on HIS screen not yours!
I'm not sure exactly how you would do this unless you have some program running on your neighbour's PC that will accept commands and act on them. In general this is considered to be hacking and is not encouraged.
It's time for a new signature.
-
Mschauder wrote:
4. Because starter.exe runs wol.exe the wol.exe will run on the laptop...
Well this is obviously wrong. As I showed in my previous posts
starter.exeshould send a message to the server with the IP address, the server then runswol.exeto send the WOL message to the desktop machine.Mschauder wrote:
sitting in school your neighbour looks bored then you start a program like media player and this program should pop up on HIS screen not yours!
I'm not sure exactly how you would do this unless you have some program running on your neighbour's PC that will accept commands and act on them. In general this is considered to be hacking and is not encouraged.
It's time for a new signature.
Well... ... thanks a lot but you don't know what I mean :laugh: I solved this otherwise 3 *.exe 1. starter.exe *new* 2. RemoteStarter.exe (some Telnet function to start Software on other systems) 3. WOL.exe There is no other solution... or how would you solve something like this when a user is not allowed to use VNC to view the server. And they know nothing about wake on LAN ;P
-
Well... ... thanks a lot but you don't know what I mean :laugh: I solved this otherwise 3 *.exe 1. starter.exe *new* 2. RemoteStarter.exe (some Telnet function to start Software on other systems) 3. WOL.exe There is no other solution... or how would you solve something like this when a user is not allowed to use VNC to view the server. And they know nothing about wake on LAN ;P
Mschauder wrote:
thanks a lot but you don't know what I mean
I think I do.
Mschauder wrote:
or how would you solve something like this when a user is not allowed to use VNC to view the server. And they know nothing about wake on LAN
I would not solve it. If you are not allowed access to the server then you should not try to hack into it. Case closed, I think.
It's time for a new signature.
-
Mschauder wrote:
thanks a lot but you don't know what I mean
I think I do.
Mschauder wrote:
or how would you solve something like this when a user is not allowed to use VNC to view the server. And they know nothing about wake on LAN
I would not solve it. If you are not allowed access to the server then you should not try to hack into it. Case closed, I think.
It's time for a new signature.
-
Nobody try to hack into it... its just ja medium that both (Laptop & desktop) can reach... But would you give an user the chance to "play" on a server? :confused:
-
Hey guys, I programmed a tool which sends a WOL packet to boot a Client. 3 devices: 1. laptop (at home) 2. Server 3. Desktop PC I connect with the laptop to the network with vpn. So I can reach the server, but not the desktop. I have to turn on the desktop pc to run a remote software from laptop to reach the client. But now the problem: I can not boot desktop pc from laptop! So I have the application on a server which both can reach. There are 2 .exe 1. starter.exe (start the WOL.exe on server) 2. WOL.exe (send WOL message to desktop pc) How can I start the WOL.exe local on the server? (If I run it with the starter.exe it would run local on the Laptop) greets, Mschauder
modified on Thursday, July 15, 2010 12:54 AM
Pretty confusing thread! Anyway, I give it a try. You need to create a service to install on the server that listens on a predefined port for messages on which desktop computer to start. As this service starts automatically at the start of the server the users don't need to interfere with the server, they only need to run a program on their home computer connecting to this service on the server, which tell their desktop to start via WOL.
"When did ignorance become a point of view" - Dilbert
-
Pretty confusing thread! Anyway, I give it a try. You need to create a service to install on the server that listens on a predefined port for messages on which desktop computer to start. As this service starts automatically at the start of the server the users don't need to interfere with the server, they only need to run a program on their home computer connecting to this service on the server, which tell their desktop to start via WOL.
"When did ignorance become a point of view" - Dilbert
-
Mschauder wrote:
But would you give an user the chance to "play" on a server?
Sorry, but I am totally lost now; I have no idea what you are trying to do as it seems the description changes with every posted message.
It's time for a new signature.