Unmanarc Remote Control Server (URCS) - 1.0.2 - howto 0.Licence All server files are copyrighted to unmanarc.com you can distribute, reimplement source, change source, and all specified under GNU/GPL Licence. Usage of this server are totaly your responsability. This server is AS IS. im not responsable for bugs, and others techniques that can compromise your security 1. Installing. ------------------------------------------------------------------------------------------------------- Installation of this server are very simple. you must have permition to run servers on your computer. and the more important rule: DON'T INSTALL IT IF YOU DON'T HAVE EXPLICIT PERMITION OF OWNER TO INSTALL. owner must read: -This server can bring total access of your computer, and may have bugs, security holes and errors that can compromise your DATA. if you agree (after read this), and owner agree, procced to install: ------------------------------------------------------------------------------------------------------- *-1.copy URCS.EXE (you can rename), to safe folder *-2.Run URCS.EXE on computer that you want to control (must have permition) *-3.Run Client.exe from where you want that control your server. as: client in example, a server ip is 10.0.0.1 for run client, copy it to safe folder such as: c:\folder and go to MSDOS (running cmd.exe) ex. C:\>cd folder C:\folder>client 10.0.0.1 *-4.When you run first time the server, you will see something as: Welcome to server... first running mode Installation program if you don't see some like this message, you need to verify network firewalls (there exist some method for install between proxy, but is a theme of other howto). *-5.Next step is follow instructions that this script bring to you, some thinks may be confused, i'll explain here: Start on windows: this creates a key on registry and copy this program to windows folder for start every time that this specific user log on to the computer. Banner : Banner is an text that is showed every time that user connect to your server ($ format explained bellow). server Name: A server name is a name that identify your server on proxy connections, and more. its for know what server is what. A port [3359]: I recommend to only press enter without change this value, becuase is a default port for do operations, if you need (for firewall rules) change this port to other, you can. (write only numbers between 1-65535), otherwise server can be damaged. Mother Name: Mother name, are hostname of computer that you want to manage your proxy connection. im bringing a service for you... you can use: proxy.unmanarc.com as mothername, and account to proxy.unmanarc.com are: route:route (user:pass format) Mother Port [3359]: leave blank, press entrer for default. otherwise you need to specify valid port that have running server. Username and password, will'be administrative (admin) account to create another's accounts, and more. *-6. when you finish this script you have an option to don't write (if you make a mistake, you can revert changes), if you are ready, press write and server will be completly functional for you. At this section, if you don't have permition to do some disk/registry operations, the installation will fail. remove server from processes, delete %windir%\urcs.ini and run it again with privileges. 2. Starting your first session with the server. learning to use: When you install the server, the next step, is use it for your own pourporses. you first need to learn how to use it. *-1. Running client. for run client only run: client.exe if you dont specify ip, it'll try to connect to 127.0.0.1, if you don't specify port, it'll intend to connect to 3359. example: client 10.0.0.2 *-2. When you see the "logon" interface, enter your admin user and password created on installation. logon interface: Connecting to: proxy.unmanarc.com, at port 3359 URCS - Unmanarc Remote Control Server 1.0.2 Banner username:route password:****** logged on. [C:\winnt route]# *-3. When you are logged on (as admin), you have access to all functions, then, do help to see the common command's Connecting to: proxy.unmanarc.com, at port 3359 URCS - Unmanarc Remote Control Server 1.0.2 Unmanarc.com Principal Server username:unmanarc00 password:***************************** logged on. [C:\winnt unmanarc00]#help Welcome to unmanarc remote control server... list of commands: echo : Echo characters introduced by command line MD5 : MD5 string introduced in command line Sleep : Wait [n] milliseconds ls : list files winexec : run process in [n] mode cp : Copy File in another location mv : Move File in another location rm : remove file ps : List Proccesses cd : change directory cat : show file who : show information about users connected to the system passwd : change's password of local user kill : terminate PID(must be admin) prompt : change prompt(must be admin) mkuser : creates another user (must be admin) rmuser : remove user from database(must be admin) net_lookup : resolves name into dotted ip addr. net_opensocket : Open TCP raw connection to IP(must be admin) net_send : Send data to TCP socket(must be admin) net_receive : Receive data from TCP socket(must be admin) net_closesocket: Close opened socket(must be admin) prx_connect : tunnel to specified server prx_who : List tunnels prx_close : Restart connection to tunnel downloadfrom : download file from CTOOL fileserver uploadto : upload file to CTOOL fileserver help : show this help NOTE: some program's may not work if you don't have privilege. [C:\winnt unmanarc00]# you can probe this commands, it's too easy. *-4. now, you need to do "some" standart users at server: mkuser -l route -p route route mkuser -l public -p public public with that, the server will have two new users for public. that's mean that every that know this, can access to you proxy, and can do few inoffensive commands (echo, md5, sleep, net_lookup, prx_who, prx_connect). Remember that have access to the proxy not mean that you have access to servers connected to proxy. there are protected by user-pass as normal logon. *-5. Remember that exit command work at logon proccess entering exit by username, and also work at logged with any user. 3. Downloading/Uploading files to my computer... Warning: Ctool2 has not revised to evites some UNICODE bugs/port bugs. if you want to contribute with that, please sendme a patch. Now, my recomendation is open ctool2 only when you need to transfer files between server and your computer and close inmediatly. well, for file-transfer operations, you need to know some concepts. The file-transfer are not supported between client-server only. with client you tell to the server to open outgoing connection to some CTOOL2. that's mean that you need to open ctool2. -Client send command to server to make a connection to ctool2 and upload file -Server connect to specified ctool2 server, and put the file in this -Finish connection, return to shell. there is an example to transfer file between server to your computer: My IP: 169.254.0.2 server: unmanarc.com first, i run ctool2: UNTT2 client tool console. 1.0 listening on port 1980... next step: [C:\winnt unmanarc00]#uploadto -d 169.254.0.2 -f render.ini myrender.ini uploading file...uploaded [C:\winnt unmanarc00]# in your computer you'll see: UNTT2 client tool console. 1.0 listening on port 1980... Connected in: 169.254.0.1:1980 The server invoked upload command: Filename: myrender.ini Receiving... Closed Command... Received.+ Closed connection to 169.254.0.1 ---------------- listening on port 1980... and myrender.ini will be in directory that are located ctool2.exe Well, this example ilustrates how tranfer a file from server to client. you may put ctool2 at computer that you want. now we illustrate how to download file from Ctool2 to server the first law: the file must be at same directory of ctool2.exe example (ctool2 already openned): [C:\ unmanarc]#downloadfrom -d 169.254.0.2 -f myrender.ini rds.ini Downloading file...downloaded well, this download file to server. ctool2------->server Ctool2 output.: Connected in: 169.254.0.1:1980 The server invoked download command: Filename: myrender.ini Sending... Closed Command... Sended.+ Closed connection to 169.254.0.1 ---------------- listening on port 1980... there is the actual method to transfer files. 4. Proxy. well, proxy is a method to connect to unaccesibles computers. theory: Unaccesible computer------TCP--------->accesible computer(proxy)<--------TCP------------client. |_________________________________proxy______________________________| by example, one computer are under firewall, and this connect's to proxy (such as: proxy.unmanarc.com) then... you only need route account (or more) at accesible computer. by example: c:\>client proxy.unmanarc.com Connecting to: proxy.unmanarc.com, at port 3359 URCS - Unmanarc Remote Control Server 1.0.2 Unmanarc.com Principal Server username:route password:****** logged on. [C:\ route]#prx_who ID SOCK IP Name of server 0 344 127.0.0.1 core-00 1 376 10.129.223.254 unma-core-01 [C:\ route]#prx_connect 1 URCS - Unmanarc Remote Control Server 1.0.2 Unmanarc.com Core Server username:unm password:*********************** logged on. [C:\unmanarc unm]# and buahala, i'm connected to some computer that are under NAT. there is a good reason for use proxys, and reverses proxys. the method is that: -connect to "mothername" of the server -prx_who for view son-servers. (view specially ID #) -with ID# of wanted server, we do: prx_connect at this case, is: prx_connect 1 -and logon to your unaccesible server. 6. well, some question at forum (see the page). next realeases will include memory operations, shellscripting, more commands, etc. enjoy.