By Jett Peters
When remote imaging, having a robust way to access your computer no matter where you are, or what device you have access to, is essential. Not only does it provide an added sense of security, but it also allows you to take advantage of your remote instrument whenever the sky is clear. With this in mind, let’s discuss one of the best solutions to this problem.
There are a plethora of remote desktop services that are incredibly easy to use and provide a balance of resolution and speed. To list a few: TeamViewer, AnyDesk, Chrome Remote Desktop, and Parsec. Like most aspects of astrophotography, opinions on the best option vary. Craig Stocks, the owner of Utah Desert Remote Observatory, believes Google Remote Desktop is the best all-around solution for most people, given there are no worries about IP addresses and it’s pretty bulletproof.
For the majority of my time being remote, I have used Parsec as a main platform. I say main platform since it is always good to have a second platform in place should you encounter a problem with your primary method of remote connection. I recently shifted Parsec to my backup, however, as a friend introduced me to another method for connecting remotely that has the same ease of use but provides higher image quality and lower latency. If you are an astrophotographer who doesn’t mind investing extra time and effort on the front end, this may be an approach worth trying.
Before I dive into what this method is and how to install and use it, it is important to understand the difference between local and non-local remote desktops. The remote desktop services I listed in the previous section are all non-local remote desktops. This means that they will work whether your two computers (remote and home) are on the same network or not. These software programs are very straightforward, but they cannot provide the same quality as a local remote desktop.
If you have ever remoted into a computer on the same network as your own computer you might be familiar with the “Windows App.” This is a free app made by Microsoft that allows you to connect between computers on your own network with very low latency and a high-quality connection. The quality of the connection is superior, but the connection is only possible between two local computers.
In order to obtain this superior connection with two computers not on the same network, the solution is a VPN. This essentially allows your two computers to act like they are on the same network, opening up the option of local remote desktop software. VPNs can get quite complicated, and the ins and outs of networking is a whole field in its own right, but thankfully there are certain software options that simplify the process.
The Windows App is the actual remote desktop software we will use, as it’s easy to set up a connection and works on all platforms, including smartphones. For the VPN component, Tailscale is an obvious choice. It is straightforward to set up, and like the Windows App, will work on all platforms. A high-level overview of the procedure follows:
- Install the Windows App on the home computer
- Make a Tailscale account
- Install Tailscale on the home computer, login, and connect to the VPN
- Install Tailscale on the remote computer, login, and connect to the VPN
- Enable the remote desktop feature in Windows settings
- Make sure Tailscale is configured to connect on startup for the remote PC (this is important, as if this setting is not enabled the remote connection will not work after a restart)
Once this procedure is complete, you should be able to go to the Tailscale “Admin Console” (which is web-based) and see both computers online. If both computers appear, you can now connect to the remote PC using the Windows App as usual, but by using the IP address given for the remote PC in the Tailscale admin console. You can also connect using just the computer’s name. If devices appear in Tailscale but you cannot connect, it’s likely a setting is not configured correctly. A good troubleshooting technique is to ping the remote computer using the terminal.