starred/Quasar

Fork 0

mirror of https://github.com/quasar/Quasar.git synced 2026-04-25 15:25:59 +03:00

[GH-ISSUE #10] unable to get xRat to connect through external IP with port forwarding working properly #2

New issue

Closed

opened 2026-02-27 15:48:13 +03:00 by kerem · 6 comments

kerem commented

2026-02-27 15:48:13 +03:00

Owner

Originally created by @ghost on GitHub (Nov 24, 2014).
Original GitHub issue: https://github.com/quasar/Quasar/issues/10

I have port forwarding setup through my modem and router to my desktop for the standard remote desktop port 3389.

When xRat is running, the service at http://www.canyouseeme.org/ can successfully see my service on port 3389.

When I create a client for IP/Hostname localhost and run that client on my desktop I get a connection.

When I create a client for my hardcoded external IP address (no DNS lookup) and run that on my desktop I do not get a connection.

I've been hacking at this all morning and can't get past the point where the client can't connect to an external IP with proper port forwarding configured and externally visible.

windoze, router, and modem firewalls all disabled.

Originally created by @ghost on GitHub (Nov 24, 2014). Original GitHub issue: https://github.com/quasar/Quasar/issues/10 I have port forwarding setup through my modem and router to my desktop for the standard remote desktop port 3389. When xRat is running, the service at http://www.canyouseeme.org/ can successfully see my service on port 3389. When I create a client for IP/Hostname localhost and run that client on my desktop I get a connection. When I create a client for my hardcoded external IP address (no DNS lookup) and run that on my desktop I do not get a connection. I've been hacking at this all morning and can't get past the point where the client can't connect to an external IP with proper port forwarding configured and externally visible. windoze, router, and modem firewalls all disabled.

kerem

2026-02-27 15:48:13 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 15:48:14 +03:00

Author

Owner

@ghost commented on GitHub (Nov 25, 2014):

I am available for testing if you want to try to hit my server with a remote client

@ghost commented on GitHub (Nov 25, 2014): I am available for testing if you want to try to hit my server with a remote client

kerem commented

2026-02-27 15:48:14 +03:00

Author

Owner

@MaxXor commented on GitHub (Nov 25, 2014):

Hey!
Please try another port than the standard remote desktop port 3389, for example 1773.

Tell me the result. :)

@MaxXor commented on GitHub (Nov 25, 2014): Hey! Please try another port than the standard remote desktop port 3389, for example 1773. Tell me the result. :)

kerem commented

2026-02-27 15:48:14 +03:00

Author

Owner

@ghost commented on GitHub (Nov 25, 2014):

I just now have it working through external IP and on the original port in question. I had previously experimented with many ports and many settings. The solution was to blow away my modem settings and turn the modem into a dumb bridge. Previously I was setting the modems port forwarding for both TCP and UDP traffic to my router, and I was port forwarding from the router to the PC, and that all worked as far as canyouseeme.org (which only tests TCP, not UDP). I have no other explanation for why it was previously failing and why it now works. Thanks!

@ghost commented on GitHub (Nov 25, 2014): I just now have it working through external IP and on the original port in question. I had previously experimented with many ports and many settings. The solution was to blow away my modem settings and turn the modem into a dumb bridge. Previously I was setting the modems port forwarding for both TCP and UDP traffic to my router, and I was port forwarding from the router to the PC, and that all worked as far as canyouseeme.org (which only tests TCP, not UDP). I have no other explanation for why it was previously failing and why it now works. Thanks!

kerem commented

2026-02-27 15:48:14 +03:00

Author

Owner

@MaxXor commented on GitHub (Nov 25, 2014):

Alright, good to know it's working now!

@MaxXor commented on GitHub (Nov 25, 2014): Alright, good to know it's working now!

kerem commented

2026-02-27 15:48:14 +03:00

Author

Owner

@ghost commented on GitHub (Nov 26, 2014):

Digging through the source code, fascinating stuff in here, the ClientBuilder is a thing of beauty. I'm wondering what options there are for encrypting or obfuscating code sections of client.bin during the client build. Drop me a line, I'd love to chat.

@ghost commented on GitHub (Nov 26, 2014): Digging through the source code, fascinating stuff in here, the ClientBuilder is a thing of beauty. I'm wondering what options there are for encrypting or obfuscating code sections of client.bin during the client build. Drop me a line, I'd love to chat.

kerem commented

2026-02-27 15:48:14 +03:00

Author

Owner

@MaxXor commented on GitHub (Nov 26, 2014):

Thanks!
Sent you a mail.

@MaxXor commented on GitHub (Nov 26, 2014): Thanks! Sent you a mail.

kerem referenced this issue

2026-02-27 15:52:31 +03:00

[PR #2] [CLOSED] Refactored Code & Extracted Types #932

kerem referenced this issue

2026-02-27 15:52:32 +03:00