This tunnel will be activated as soon as you connect to the corresponding AnyDesk ID. The exact port number doesn’t matter, we use 2222 as an example in this case.

In the example above, we are forwarding the TCP port 22 of the remote machine (the remote port used by SSH) to the local port 2222. To forward the SSH port we need to add a rule into the setup window: TCP tunneling setup For our purpose, we select the direct tunnels.

In the dialog box, you’ll see the settings for direct and reverse tunnels. To do so, open the TCP tunneling settings from the context menu of the address tile: Context menu in Recent Sessions Using the TCP Tunneling Feature of AnyDesk you can set up a tunnel to the remote computer and use SSH almost as if the two computers were in the same network. With AnyDesk, however, one can connect to any computer regardless of any firewalls or NATs. Usually this is not the case when you are connecting to your office PC from home. This happens, for example, if the host is on the same local network or has an external IP address. SSH, like any other TCP connection, is only possible when the host you are connecting to is visible from your local computer.

Setting Up a Direct Tunnel Connection With SSH This solution is much more CPU and traffic-efficient than the classical Remote Desktop Access. In this article I will show you how to mount a remote folder locally using TCP Tunneling with AnyDesk for Linux but it’s also available for Windows and macOS devices. With AnyDesk you can set up a TCP tunnel connection which allows you to access files on a remote device locally without having to download them on your local machine. Being able to access a source code locally can often make things faster and more comfortable. Mount Remote Folders Locally With an AnyDesk TCP Tunnelįor a software developer, Remote Work can be a challenge.

Anydesk remote connection step by step