For some reason when I use Darkcomet, everything is portforwaded and setup but when I run my server on myself I don't show up. Why is this happening?
Echo Official Help Desk | RAT Expert | Free | Spreading Tips |
(Dec 26, 2013 10:21 PM)PyramidXI Wrote: For some reason when I use Darkcomet, everything is portforwaded and setup but when I run my server on myself I don't show up. Why is this happening? Run it via localhost (127.0.0.1) and then try testing on yourself. (Dec 26, 2013 08:32 PM)Vampiresa a Wrote: When im trying to Remote desktop(s) Just close and reopen your Darkcomet and your issue should be fixed mate. (Dec 27, 2013 12:40 PM)Froast Wrote: can you forward my port on team viewer Throw me a PM with your join.me link. (Dec 27, 2013 05:25 PM)narb123 Wrote: My RAT isn't working when I run it on my self, I've portforwarded everything and done everything that I should I have done yet it doesn't work. Can you TV me and help me set it up please? Are you running it on yourself via localhost? (127.0.0.1)
thx 4 the thread design george ur da bess
(Dec 27, 2013 08:52 PM)Kansas Wrote: thx 4 the thread design george ur da bess shoutouts 2 my main man george. #gfxguru
I have 2 windows 8 machines on my wireless LAN.
The client I wish to administer (IP 192.168.0.100) and the server I wish to admin the client from (IP 192.168.0.50) I've tried building the stub using both localhost (127.0.0.1:23) and the client IP (192.168.0.100:23) and if I run DC admin tool on the client PC I can see it in the user list with either IP setup. However, the client doesn't show up in the user list of the DC admin tool of my admin PC (IP 192.168.0.50). I've setup the listen port in the "socket/net" tab to port 23 but still no luck. What am I doing wrong? Windows defender and firewall are disabled on both systems Ideally I'd like DC to only be accessible via the LAN (no traffic passing to the internet). Thanks in advance. (Dec 28, 2013 11:58 AM)UserUS Wrote: I have 2 windows 8 machines on my wireless LAN. Use the port 1604 and retry it all please. It should work now. (Dec 28, 2013 05:06 PM)Understalker Wrote: Use the port 1604 and retry it all please. I rebuilt a new stub with the settings 172.0.0.1:1604 and 192.168.0.100:1604 and changed the listening socket to match. I'm still having the same problem. The client is visible from my .100 PC but not from my .50 PC. Thoughts? Thanks. |
|
|

