Start .exe from a Server with params
-
Mschauder wrote:
english is not my native language
No problem, we try to help everyone.
Mschauder wrote:
do you have an idea how I can solve this?
I think you need to try and explain your problem again as I cannot see where your difficulty lies. You keep mentioning something about ".exe on server" but I cannot see what that means.
It's time for a new signature.
:laugh: ok lets try again! I sit at home with a laptop. The laptop is connected to a server. Then I want connect with my PC at work (Remote). But my PC is turned off when I go home. So I have to turn it on. So I develop for our users a application that they only have to start 1 icon. the *.exe works if I have a direct link to the other client. So they start the "WOL_starter.exe" local on the laptop. the "WOL_starter.exe" should start the "WakeonLAN.exe" on the SERVER with the parameter (IP or MAC). But if "WOL_starter.exe" start the "WakeonLAN.exe" this .exe will start local on the laptop and the laptop had no direct link to the Client. I hope this will help ! :D
-
:laugh: ok lets try again! I sit at home with a laptop. The laptop is connected to a server. Then I want connect with my PC at work (Remote). But my PC is turned off when I go home. So I have to turn it on. So I develop for our users a application that they only have to start 1 icon. the *.exe works if I have a direct link to the other client. So they start the "WOL_starter.exe" local on the laptop. the "WOL_starter.exe" should start the "WakeonLAN.exe" on the SERVER with the parameter (IP or MAC). But if "WOL_starter.exe" start the "WakeonLAN.exe" this .exe will start local on the laptop and the laptop had no direct link to the Client. I hope this will help ! :D
OK, I think we are making progress: Laptop (user) ----> Server ----> Desktop (remote)
- Laptop: runs
WOL_starter.exe [IP address of Desktop] - Laptop:
WOL_starter.exeprogram sends message with IP address to the server - Server: receives message (from Laptop) with IP address
- Server: sends WOL message to IP address (Desktop)
- Desktop: wakes up, boots and is ready ...
- Laptop: ?
Mschauder wrote:
But if "WOL_starter.exe" start the "WakeonLAN.exe" this .exe will start local on the laptop and the laptop had no direct link to the Client.
This statement I do not understand, did I miss something?
It's time for a new signature.
- Laptop: runs
-
:laugh: ok lets try again! I sit at home with a laptop. The laptop is connected to a server. Then I want connect with my PC at work (Remote). But my PC is turned off when I go home. So I have to turn it on. So I develop for our users a application that they only have to start 1 icon. the *.exe works if I have a direct link to the other client. So they start the "WOL_starter.exe" local on the laptop. the "WOL_starter.exe" should start the "WakeonLAN.exe" on the SERVER with the parameter (IP or MAC). But if "WOL_starter.exe" start the "WakeonLAN.exe" this .exe will start local on the laptop and the laptop had no direct link to the Client. I hope this will help ! :D
-
OK, I think we are making progress: Laptop (user) ----> Server ----> Desktop (remote)
- Laptop: runs
WOL_starter.exe [IP address of Desktop] - Laptop:
WOL_starter.exeprogram sends message with IP address to the server - Server: receives message (from Laptop) with IP address
- Server: sends WOL message to IP address (Desktop)
- Desktop: wakes up, boots and is ready ...
- Laptop: ?
Mschauder wrote:
But if "WOL_starter.exe" start the "WakeonLAN.exe" this .exe will start local on the laptop and the laptop had no direct link to the Client.
This statement I do not understand, did I miss something?
It's time for a new signature.
1. Laptop: runs WOL_starter.exe 2. Server runs WakeonLAN.exe 3. Desktop boot 4. Laptop use remote-desktop on the Desktop pc There are 2 *.exe -- 1. WOL_starter.exe -> *.exe on the Laptop -> communicate to the server and start "WakeonLAN.exe" with parameter IP. 2. WakeonLAN.exe -> *.exe on the server -> send WOL message to the Desktop PC
- Laptop: runs
-
1. Laptop: runs WOL_starter.exe 2. Server runs WakeonLAN.exe 3. Desktop boot 4. Laptop use remote-desktop on the Desktop pc There are 2 *.exe -- 1. WOL_starter.exe -> *.exe on the Laptop -> communicate to the server and start "WakeonLAN.exe" with parameter IP. 2. WakeonLAN.exe -> *.exe on the server -> send WOL message to the Desktop PC
-
OK, so we both agree on the sequence of operations and where the programs are, but now I am more confused: what is the problem?
It's time for a new signature.
Well... 1. If the Laptop start the WOL_starter.exe the WOL_starter runs WakeonLAN.exe (from server) local on the laptop and this laptop can't communicate to the desktop PC! ;) so some error occurs. The User (Laptop) just should start my starter.exe and his desktop should turn on. They have no permission to connect to server via remote. The server should start his program on his system not on the Laptop :laugh:
-
Well... 1. If the Laptop start the WOL_starter.exe the WOL_starter runs WakeonLAN.exe (from server) local on the laptop and this laptop can't communicate to the desktop PC! ;) so some error occurs. The User (Laptop) just should start my starter.exe and his desktop should turn on. They have no permission to connect to server via remote. The server should start his program on his system not on the Laptop :laugh:
Mschauder wrote:
1. If the Laptop start the WOL_starter.exe the WOL_starter runs WakeonLAN.exe (from server) local on the laptop and this laptop can't communicate to the desktop PC!
This does not makes sense; how can the server start a program that runs on the laptop?
It's time for a new signature.
-
Mschauder wrote:
1. If the Laptop start the WOL_starter.exe the WOL_starter runs WakeonLAN.exe (from server) local on the laptop and this laptop can't communicate to the desktop PC!
This does not makes sense; how can the server start a program that runs on the laptop?
It's time for a new signature.
-
starter.exe send parameter to the wol.exe on the server and start it. But if I start the starter.exe local on my laptop, the WOL.exe will run there, too.
Mschauder wrote:
starter.exe send parameter to the wol.exe on the server and start it. But if I start the starter.exe local on my laptop, the WOL.exe will run there, too.
These two statements are mutually exclusive; if statement 1 is true how can statement 2 also be true?
It's time for a new signature.
-
Mschauder wrote:
starter.exe send parameter to the wol.exe on the server and start it. But if I start the starter.exe local on my laptop, the WOL.exe will run there, too.
These two statements are mutually exclusive; if statement 1 is true how can statement 2 also be true?
It's time for a new signature.
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:
which coincidence
Learning about two Germans with (almost) the same name in one day. :laugh:
It's time for a new signature.
-
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: