Skip to main content

Tech Tip: Set up Remote Desktop on 443 to Get Through a Restrictive Firewall

 

I often connect to the Internet through a guest wireless account. These guest wireless networks are typically very restrictive and block all ports except for 80 (http) and 443 (https) .  This is a big pain when I need to remote desktop into a remote machine, or perform other tasks which also might be restricted by the firewall like accessing my online email, searching the Internet for helpful blog posts, etc.

Here is an awesome tip to get to the resources you need: Set up a remote machine and change the Remote desktop port from the default of 3389 to 443. To do this just change a registry key and then reboot your machine. See this Microsoft KB article for details. You will also need to configure your router to forward inbound traffic for 443 to your machine. Instructional videos on port forwarding with a Linksys router.

Another benefit of this approach is that the traffic between you and the website is not exposed to the guest network which is usually a low security, public network and vulnerable to packet sniffing. The guest network only sees RDP packets being passed between your laptop and your remote machine.

Comments

Arun said…
Awesome idea, I am totally going to do this. I have been mucking around with an HTTP-Tunnel program for most things like this but this is a great idea if you don't need port 443 forwarded to another machine.

Thank you!
3:48 AM
Arun said…
This comment has been removed by the author.
3:49 AM
Post a Comment

Popular posts from this blog

How to Create and Run Tableau Bridge on Linux Containers

Tableau Bridge is now availble on Linux Containers. Yay! Now what does this mean and how do I build and run Linux Containers? We will discuss the advantages of running Bridge on Linux Containers the steps to build them, and finally, we will provide some automation script ideas for monitoring and scaling Linux Bridge agents. Tableau Bridge Today Until recently, Tableau Bridge was only available as a Windows application running on a Windows VM. It supported only one bridge agent per Virtual or Physical Machine. Advantages of Bridge in Containers Better Hardware Utilization: Linux containers are more efficient than Windows VMs, requiring only about 1/50th of the disk space. Ability to Spin Up Multiple Bridge Agents: With Linux Containers, it becomes easier to spin up multiple bridge agents on a single machine, improving scalability and resource utilization. Infrastructure Automation: Linux Containers enable easier automation of provisioning bridge agents and upgrading Tableau Bridge, the...
1 comment
Read more

Unleashing Tableau’s Semantic Layer with AI Agents

⚡ TL;DR I helped built a tool that lets you query Tableau’s semantic layer  using natural language and AI. By integrating a LangChain agent with Tableau’s VizQL Data Service (VDS), we can repurpose Tableau’s trusted data model for conversational analytics . This means you can ask questions in plain English and get answers backed by the same definitions and security that your Tableau dashboards use. In this post, I’ll introduce this open-source agentic tool ( tableau_langchain ), why it’s transformative for analytics, and how it works under the hood. Why Connect LangChain Agents to Tableau? As a user of Tableau, I’ve seen how powerful Tableau’s semantic layer is. It encapsulates our organization’s business logic: things like predefined metrics, calculations, data relationships, and even row-level security rules. Traditionally, that semantic layer is only accessible through Tableau’s interface – you drag and drop fields to build a viz, and Tableau generates the query for you. Rece...
Post a Comment
Read more

RAM Disks do not speed up Visual Studio

  The limiting factor for Visual Studio is disk IO. I got a tip to speed up Visual Studio from Channel 9 by creating a RAM disk which sounded like a great idea. However, when I ran a thorough set of tests, I found that the performance difference between the Ram disk and the hard disk were not appreciably different. This was a big surprise since RAM is 240,000 times faster than disk (see my previous blog post). But the reason is because Visual Studio and Vista do a lot of caching. So compile times for the same project in RAM disk and on hard disk were pretty similar. I also tested the time it took to search the entire solution for a word, and times to open a solution. There was no discernable difference!   If you still want to try it out and create your own RAM disk, you can download a simple RAMDISK.EXE utility to create a RAM disk in just a few minutes. What is a RAM Disk ?   Ramdisk is a virtual drive created in RAM.   Performance Analysis Creating f...
10 comments
Read more