What's new

inbound proxy domain.com:123 --> internal 192.168.1.500:456 (RDP)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

jochenthomas

Occasional Visitor
Hi,
I was searching the thread but without any result (hopefully nothing missed).

I am planning (or thinking over) to activate RDP access from public web without any VPN and as much secure as possible (please no discussion like VPN yes/no).

As I am working in different companies I need to use typical open ports like 80 or 443.
Therefore I would like to allow any RDP request only for a specific domain (e.g. abc-domain.com) and port (e.g. 443) similar to the following:

abc-domain.com:443 --> RT-AC87U --> 192.168.1.100:3389 (Windows box with RDP port)
xyz-domain.org:443 --> RT-AC87U --> 192.168.1.555:443 (Web server SSL)​

But on the other hand the usual web server should still be accessible (second example)
Typically you can achieve this with an Apache proxy or similar solutions.

Is there a way to route or proxy incoming traffic based on domain and port to an internal IP/port? Beneficial would be to include a source IP-range as well...

Thanks for any suggestions.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top