Connect to a computer remotely, be it from the other end of the office or halfway around the world. AnyDesk ensures secure and reliable remote desktop connections for IT professionals and on-the-go individuals alike.

Outstanding Performance

PC2 can access PC1 by Anydesk successfully without extra firewall or NAT settings. PC2-Internet- (WAN)USG40 (LAN)-PC1 (Anydesk) If there are lots of 'abnormal TCP flag attack detected, DROP' logs, you can follow the instruction from Alfonso to enter the.

• Well, if this list from the Anydesk website doesn't tell you anything, TCP Tunneling is not for you: Tunnel Applications. Internal web services. Bypass gateway or firewall. Controlling industrial devices. You can use it to tunnel connections directly between two hosts, essentially bypassing any firewalls. It's like an ad-hoc VPN.
• We love anydesk, we deployed anydesk on 250+ machines and now we are facing a whole lot of trouble organizing the machines. Set-up: Custom Anydesk installer is being deployed on our clients machines. After installation, those machines automatically show up in Address Book X (AB-X).
• Blocking the listening port doesn't block Anydesk. It just blocks the direct connection between the two clients. When the listening port is blocked, it will connect via an outgoing connection to port 80 to an Anydesk relay server, essentially punching through your firewall (assuming that port outgoing TCP 80 is allowed).
• Check the original PowerShell script here, and the fully obfuscated one here. After manual obfuscation, the original PowerShell script was obfuscated with Invoke-Obfuscation.Credits to the author! Search the Internet for additional obfuscation techniques and methods. As the PowerShell is constantly being updated some regular expressions (e.g.ke-E.) might start to throw errors due to.

Ever experienced our innovative DeskRT codec in action? Low Latency and high Framerates are critical for working remotely. Don’t wait for your remote desktop to respond - even at high screen resolutions or low bandwidths of just 100 kB/s.

Lean and Elegant

No administrative privileges or installation needed. Get started within seconds on any operating system. Work on the go with your mobile devices.

Superior Security

Security is our priority. We use military-grade TLS technology to ensure your device is protected from unauthorized access. RSA 2048 asymmetric encryption verifies every connection. For maximum reliability, our servers run on purpose-built Erlang telecommunication technology.

All Platforms

AnyDesk runs on all common operating systems and devices on the market without any additional charge. Apps for Windows, macOS, iOS, Android, Linux, Raspberry Pi and more.

In Cloud or On-Premises

AnyDesk offers maximum flexibility adapting to your security or policy requirements.

• Maintenance and updates included
• Independent global server infrastructure
• Reliable Service with 99%+ uptime
• Customized Clients available

On-Premises Solution

Suits businesses with individual security policies

• Customizable solution
• Advanced API integration options
• Self-hosted and self-managed by your IT Team
• Data remains within your company network

Still not convinced? Try it now!

No signup required

CEO, Spidercam

'spidercam® Producer uses AnyDesk Remote Desktop Tool for Worldwide Equipment Support.'

CIO, Airport Münster/Osnabrück

'It wasn't until we tried AnyDesk that we were able to solve the data security problem.'

IT-Security Officer, AIP

'After searching for a bit, we found AnyDesk with its in-house-solution, offering exactly what we were looking for.'

By downloading and using AnyDesk, you accept our license agreement and our privacy statement.

Please consider taking our survey to help us make AnyDesk even better!

If the download does not start automatically, please click the Download link below.

Double-click the downloaded AnyDesk file and AnyDesk will start immediately.

Enter the ID or Alias of the remote device into the field under 'Remote Desk'.

Click the green 'Connect'-Button and enjoy our fast and simple remote software solution.

Use a Protocol Tunnel Jump to Make a TCP Connection to a Remote System

Anydesk Tcp Tunneling

Using a Protocol Tunnel Jump, make a TCP connection from your system to an endpoint on a remote network. Because the connection occurs through a Jumpoint, the administrator can control which users have access, when they have access, and if the sessions are recorded.

Create a Protocol Tunnel Jump Shortcut

Anydesk Tcp Tunnel Rdp

To create a Protocol Tunnel Jump Shortcut, click the Create button in the Jump interface. From the dropdown, select Protocol Tunnel Jump. Protocol Tunnel Jump shortcuts appear in the Jump interface along with Jump Clients and other types of Jump Item shortcuts.

Protocol Tunnel Jump shortcuts are enabled only if their Jumpoint is configured for the Protocol Tunnel Jump method on the /login > Jump > Jumpoint page.

Anydesk Tcp Tunneling

Enter a Name for the Jump Item. This name identifies the item in the session tabs. This string has a maximum of 128 characters.

From the Jumpoint dropdown, select the network that hosts the computer you wish to access. The access console remembers your Jumpoint choice the next time you create this type of Jump Item. Enter the Hostname / IP of the system you wish to access.

Specify a Local Address. The default address is 127.0.0.1. If you need to connect to multiple systems on the same remote port at the same time, you can enable that connection by changing each Protocol Tunnel Jump Shortcut's address to a different address within the 127.x.x.x subrange.

In Local Port, specify the port that will listen on the user's local system. If you leave this as automatic, the access console allocates a free port.

In Remote Port, specify the port to connect to on the remote system. This is dictated by the type of server you are connecting to.

You can define multiple pairs of TCP Tunnels as necessary for your setup.

Move Jump Items from one Jump Group to another using the Jump Group dropdown. The ability to move Jump Items to or from different Jump Groups depends upon your account permissions.

Further organize Jump Items by entering the name of a new or existing Tag. Even though the selected Jump Items are grouped together under the tag, they are still listed under the Jump Group in which each is pinned. To move a Jump Item back into its top-level Jump Group, leave this field blank.

Jump Items include a Comments field for a name or description, which makes sorting, searching, and identifying Jump Items faster and easier.

To set when users are allowed to access this Jump Item, if a notification of access should be sent, or if permission or a ticket ID from your external ticketing system is required to use this Jump Item, choose a Jump Policy. These policies are configured by your administrator in the /login interface.

Organize and manage existing Jump Items by selecting one or more Jump Items and clicking Properties.

To view the properties of multiple Jump Items, the items selected must be all the same type (all Jump Clients, all Remote Jumps, etc.).To review properties of other types of Jump Items, please see the appropriate section in this guide.

Use a Protocol Tunnel Jump Shortcut

To use a Protocol Tunnel Jump shortcut to start a session, simply select the shortcut from the Jump interface and click the Jump button.

A session appears in your access console. Click the Protocol Tunneling button to establish the connection.

If screen recording is enabled, a prompt appears, informing you that your desktop will be recorded. Click OK to continue. If you click Cancel, the Protocol Tunnel will not be created.

If screen recording is enabled, an indicator appears at the top of your session screen.

The Current Tunnels section displays current connections and their statuses. You also can view brief Network Statistics.

You can now open a third-party client to perform tasks on the remote system. Use the ports indicated to connect through the Jumpoint.

Stipulations to Correct Functioning

The Protocol Tunneling feature tunnels network traffic in a way that places some restrictions on how communication must occur between the user's system and the endpoint.

• All traffic must be TCP.
• No more than 256 simultaneous connections can be handled.
• All TCP connections must originate from the endpoint and must be accepted by the listening user's system. The application's protocol cannot require that the user's system make a separate connection back to the endpoint.
• Any TCP connections that the endpoint is to make back to the user's system must be made over tunnels already defined within the Protocol Tunnel Jump Item properties.
• Operating systems typically disallow non-elevated processes from listening on ports less than 1024. Therefore, the local port must generally be greater than 1024. The endpoint software connects to the server by connecting to the local port on which the access console (a non-elevated process) is listening.
• The endpoint software cannot make connections to any system on the remote network other than the one specified in the Protocol Tunnel Jump Item properties.
• The protocol must be agnostic toward the hostname that the endpoint used to connect to the server. Otherwise, other means must be made to satisfy the protocol's requirements, such as mapping a hostname to 127.0.0.1 in the hosts file or applying special configuration to the endpoint client.
• If the tunnel definition has a local port that is different than the remote port (namely, when the local port must be greater than 1024 because the server's port is less than 1024), the protocol must be agnostic toward the port that the endpoint client used to connect to the server.
• Any protocol which goes beyond the case of making a single TCP connection from the endpoint client to the user's system requires the administrator's understanding their specific protocol and the stipulations listed above.