C# send windows messages to a networked computer

Question

1.00/5 (2 votes)

See more:

hello everyone!
i want to know how to:
A. start a process on a remote machine directly ~~without using a client app~~.
B. send WinAPI messages from the local workstation to the process i just on the remote pc
i know how to send messages to an app on the local machine but i don't know how to send a message to a remote machine(its on the same network) but there is a ~~golden rule: there can't be a client app running on the remote machine~~(this due to the fact that i am trying to pull a prank on the user of the remote machine)
i think this would be implemented by UDP right?
i would like to do thin in C#.NET(version 4)
also i am a standard user, and i don't have any administrator privileges(this is on the local machine)
--UPDATE--
i the 2 solutions below i have been told that doing this without a client app running on the other pc is impossible. so how would i build an app that can revive windows messages and execute them on a remote machine?
thank you for your help in advance,
MasterCodeon

Posted 5-Jan-15 13:02pm

MasterCodeon

Updated 6-Jan-15 3:25am

v3

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Jeremy Falcon · Answer 1 · 2015-01-05T13:15:00

Solution 1

Assuming you're not trying to write a virus...

What you're asking for is impossible without a receiver program on the remote machine. Nowhere does Windows automatically process sockets and execute them as a Windows API call. You'd need a program to receive the packets and them process commands in them to translate them into the appropriate calls.

Posted 5-Jan-15 13:15pm

Jeremy Falcon

Comments

MasterCodeon 5-Jan-15 19:29pm

no i am not trying to write a virus, i am trying to play a prank on someone(i am trying to make the other person think this is a virus, and freak out).
couldn't you use explorer.exe to execute commands?

Sergey Alexandrovich Kryukov 5-Jan-15 20:31pm

You cannot do this. What you call the "golden rule" can be formulated like this: your "golden rule" is never true. :-)
Technically speaking, your supposedly innocent prank is no different from the worst really malicious trick. In other words, it you could trick some system users into having some software which would allow such attack as yours, it would be almost like kissing the affected system good bye.
By the way, if you wanted to initiate communication on your side, the software running on the client machine would have to be server, not client. Client is always active, and server (in narrow sense of this word) is always passive.
—SA

MasterCodeon 6-Jan-15 9:22am

ok then how would i do this with a client app running on the other machine?
and i promise this is just a prank.

Sergey Alexandrovich Kryukov 6-Jan-15 10:47am

But, just because there is no a technical difference, the remote computers won't allow you to play this prank. You would need to add a bit of social engineering to it. :-)
—SA

MasterCodeon 6-Jan-15 11:51am

i know how to do the social engineering part of the prank, i just don't know how to do the technical part of it.

Sergey Alexandrovich Kryukov 5-Jan-15 20:31pm

5ed.
—SA

Dave Kreskowiak · Answer 2 · 2015-01-05T15:12:00

1) You can launch a remote process using WMI, but it can NOT be an interactive process. This means that the user logged into the console will NOT see it running at all. For example, you can launch Notepad, but it'll sit there waiting for input it'll never get and the user will not see it.

2) It's impossible to remotely execute "window messages" without a client application listening for commands.

... oh, and you say that you don't have admin priv's? Well forget it all because you can't do anything on the remote machine without them.