This is quite stupid... im having trouble using a RAT (remote administration tool)
Everything is set perfectly, (port forwarding, server configuration etc.)
Although the client doesn't seem to be picking up reverse connections.
After exploring my ports i think i found the cause.
As you can see- the rat runs on local ip "0.0.0.0" when its actually ment to be "192.168.0.2"
What can i do to fix this?
Thanks for reading
Setting up a RAT problems
- str33tl0rd
- Fame ! Where are the chicks?!
- Posts: 241
- Joined: 04 Jul 2008, 16:00
- 15
- Location: somewhere
- str33tl0rd
- Fame ! Where are the chicks?!
- Posts: 241
- Joined: 04 Jul 2008, 16:00
- 15
- Location: somewhere
well, the only possibilities i could give are:
1. Firewall that you are using doesn't allow transmission
2. You have created a server with a ip 0.0.0.0 on port 12345.
1. Firewall that you are using doesn't allow transmission
2. You have created a server with a ip 0.0.0.0 on port 12345.
Last edited by str33tl0rd on 26 Jan 2009, 20:11, edited 1 time in total.
A fools mind is at the mercy of his tongue and a wise mans tongue is under the control of his mind.~ Imam Ali (A.S)
1. can be cut off because i have disabled both firewall and security center
2. can be cut off because it has nothing to do with the server. Its the client that listens local ip 0.0.0.0. I need it to listen on 192.168.0.2 because port forwarding directs incomming reverse connections to that ip.
so unless the client listens on port 192.168.0.2 i wont be recieving any connections
2. can be cut off because it has nothing to do with the server. Its the client that listens local ip 0.0.0.0. I need it to listen on 192.168.0.2 because port forwarding directs incomming reverse connections to that ip.
so unless the client listens on port 192.168.0.2 i wont be recieving any connections