For this to work you gotta have ports open on both sides (if you wanna talk both ways, sorry best I could do)
zips:
http://www.vulnwatch...cat/nc111nt.zip
http://xset.tripod.com/xset551.zip
nc.exe shows up as a "hacktool" with norton. I told it to ignore it somehow (I have norton corp) I can tell you if you want to know.
The computer recieving the message is called the server, the computer sending is called the remote (techincally client but whatever). Just to be clear.
Make a folder on the server
put XSET.exe, XSET32.CMD, nc.exe in the folder
Also you need to make a file (I called it bat.bat)
@echo off CALL XSET32 string caller.exe %string%
Also that folder put caller.ahk
tooltip, %1% Sleep, 1000You need to compile this file.
open a cmd window, cd to your folder, and run this:
nc.exe -L -p 100 -t -e bat.batovbiously you would run this from an ahk script
next on the remote computer, make a folder, and put nc.exe in it
Also put a txt file like this named command.txt:
yayA newline at the end of the file is crucial
Still on remote computer, open a cmd window, cd to the folder, and run
nc.exe 192.168.198.129 100 < command.txtchange your ip ovbiously
Ok so a little more info about this setup:
On the server, you would run nc without runwait, b/c it's a server so it idles.
On the remote, you should use runwait.
I haven't actually used this setup in my script yet, so I will have more info about it later.
Idealy you would have one parent script running on the server, and then you would use caller.exe to post/sendmessage to your parent script.
I want + and - FEEDBACK PLEASE!!! Thanks