![]() |
|
Despite the port being forwarded, server still cant connect - Printable Version +- Hack Forums (https://hackforums.net) +-- Forum: Hacks, Exploits, and Various Discussions (https://hackforums.net/forumdisplay.php?fid=45) +--- Forum: Blackhat • Red Team • Offensive Security (https://hackforums.net/forumdisplay.php?fid=447) +---- Forum: Remote Administration Tools (https://hackforums.net/forumdisplay.php?fid=114) +---- Thread: Despite the port being forwarded, server still cant connect (/showthread.php?tid=5472714) Pages: Pages
1
2
|
Despite the port being forwarded, server still cant connect - wat iz dat - Nov 23, 2016 Hello. I have downloaded the Quasar Rat and forwarded the port 6661. canyousemee.org confirms its open, I use a dynamic dns and it seems to work as well (whenever i ping it via cmd it gives me my IP address back) but still, when I use Quasar on myself it wont connect to my client. However, when I use 127.0.0.1 as the host, it works flawlessly. What could be the problem? * - Purple Kief - Nov 23, 2016 Enable NAT loopback in your router settings. This happening is perfectly normal with certain routers. * - Tee Plow - Nov 23, 2016 (Nov 23, 2016 12:02 PM)Purple Kief Wrote: Enable NAT loopback in your router settings.+1 * - Skiezo™ - Nov 23, 2016 Most likely reason you don't show up when you test it on yourself is the fact your probably using your external address when testing, (Eg, your WAN IP, or your DNS) and most likely your router/gateway/modem doesn't have NAT loopback support. Nothing to worry about, just when you test within your network use internal addresses, (eg, if your testing on the computer that is running the client use 127.0.0.1, if your testing within your network on a different computer use the address of the computer hosting the client). But like Purple Kief said, if your router does support NAT loopback, you're lucky in that case. * - wat iz dat - Nov 23, 2016 Thanks for all the replies. I tested it on a different computer (not even in my network) and it still didnt connect to me. Any ideas? * - Skiezo™ - Nov 23, 2016 (Nov 23, 2016 12:26 PM)wat iz dat Wrote: Thanks for all the replies. I tested it on a different computer (not even in my network) and it still didnt connect to me. Any ideas? Then it's either your DNS or you're not port forwarded correctly. * - Da Mango - Nov 24, 2016 I'm having the same issue as OP and I cant figured it out. My DNS succesfully resolves to my IP and my port is open and listening (according to CanYouSeeMe) * - mistarp - Nov 24, 2016 Are you guys using a vm or just the host machine? * - Da Mango - Nov 24, 2016 (Nov 24, 2016 10:37 AM)mistarp Wrote: Are you guys using a vm or just the host machine? I am using a VM and have tested on a separate machine as well. Only Localhost works, but when I put in my DNS then it does not. I am using No-Ip as my DNS. * - Skiezo™ - Nov 25, 2016 (Nov 24, 2016 05:24 PM)Da Mango Wrote: I am using a VM and have tested on a separate machine as well. Don't use No-IP as your DNS Service, it's something you already should know by now * - Da Mango - Nov 25, 2016 (Nov 25, 2016 05:21 AM)Skiezo™ Wrote: Don't use No-IP as your DNS Service, it's something you already should know by now I'm not using the RAT for infecting. I am using it as an educational tool. I will not be spreading it at all, I will only be using it in my own testing environment. That being said, using No-IP as a DNS service shouldn't cause connectivity issues between my server and my stub correct? * - warpje - Nov 25, 2016 If you set it up Right then it shouldnt * - Da Mango - Nov 25, 2016 (Nov 25, 2016 10:48 AM)warpje Wrote: If you set it up Right then it shouldnt Canyouseeme can see njRat listening. No-ip has my correct IP and Ive recently installed they're DUC so it stay updated. I cant see the problem. Im not envrypting the file in any way either. * - warpje - Nov 25, 2016 And how are you testing it? Because if you try your own system then you should use 127.0.0.1 Else in VM your real IP or your local router ip! * - Da Mango - Nov 25, 2016 (Nov 25, 2016 01:45 PM)warpje Wrote: And how are you testing it? Because if you try your own system then you should use 127.0.0.1 I have tested it with another laptop on the same network. I have also tested it with a laptop on a separate network. None of them seem to have a connection. |