Connecting via RDP on port 3389 from within the port.
Connecting via RDP on port 3389 from within the port.
Hello everyone, here’s a brief overview. I’m currently a student who recently relocated from my parents’ house, gaining full control over the router and its configurations. I set up port forwarding from ‘X’ to 3389 so that when I connected to the public IP via that port, it would redirect to 3389 for security reasons. This setup ensures multiple layers of protection, even though I need admin access or be part of a specific user group.
Now, since I’m in student housing with a firewall blocking RDP connections and no direct access to the nearest network device, I can’t use the previous method. I assume the firewall only restricts incoming traffic, not outgoing ones. I’d like my desktop to initiate an RDP callout for connecting to the remote machine. I’m unsure how to achieve this, especially on a Linux-based system, and I appreciate any guidance.
Thanks in advance! P.S. Sorry if my explanation is unclear—I’m not always the best at putting it together.
Considering a method to link the RDP protocol via port 443 without interference from the firewall. Still unclear on the steps, but it’s something I’m thinking about.
You could connect to a router located elsewhere with OpenVPN, creating an internet link through your home network, then routing it via your parents' house to access the server.
Yes, you can modify the port that RDP listens on: Doc on Microsoft. The main concern is understanding how your RDP connection relates to the RDP service itself. You might be able to test with rdsserver:443. OpenVPN remains a viable alternative, though I’m certain they’d also block it. For your case, I recommend exploring SoftEther Azure (using MS Azure routing) if you want to host something locally, or ZeroTier—it’s user-friendly, free, open-source, and can work around most firewalls. If you need assistance setting up any of these options, feel free to reach out anytime. Hope this clears things up!
Thanks for the encouragement! I plan to give it a shot tomorrow when I have some spare time. It’s reassuring to see so many choices available, and I appreciate your support. I’ll update you on my progress.
Cool will handle as per the reserved port number. My thought is it might not work because the port is either closed or the firewall blocks untrusted traffic on that port. For example, the company staff’s IT team uses TeamViewer for remote access even though they have a basic ADDS setup. Additionally, I used to connect via the public IP:port number, and the router forwarded the port to 3389. The DNS query through the router likely resolved it to my PC, which enabled RD connections.
I really prefer places with strong WAP connections, and that’s all. My access is quite limited, and most features aren’t admin-related. I also need to manually enter the MAC addresses for each device I use—something I’m not sure about since even a basic CAM table stores them as soon as they connect. I’ll attempt openVPN, even though I haven’t heard of it before, and I’ll explore other options if that doesn’t work.
It's a clever approach! You'd want to use a VPN to connect to the remote site, like your parents' house, and if that's the intended destination, you could set it up. Using OpenVPN, then connecting via RDP, and with PFSSL you could host an OpenVPN server there.
I understand they use monitoring tools, but I’ll handle it myself if needed. I won’t use it for any harmful purposes, and if they ask me to stop, I’ll comply and look for an alternative solution.