RealmJoin Classic
  • Welcome
  • Installation
    • Install Using Microsoft Intune
    • Interactive Installation
    • Connecting a Tenant
  • Infrastructure
  • RealmJoin Windows Client
    • User Interface
    • Client Menu
  • RealmJoin Portal
    • Roles in RealmJoin
    • Clients
    • Users and User Settings
    • Groups and Group Settings
    • App Store
    • Software Packages
    • Request Package
  • Multi-User Devices
  • Core Features
    • Local Admin Password Solution
      • KeyVault
      • Application Insights
    • AnyDesk
      • Internal Tasks
      • Customer Tasks
      • AnyDesk Cloud Connections
    • Notifications
    • Software Report
    • Delivery Optimization for Windows Update
    • BitLocker
    • Intranet Zone
    • Domain Connect
    • Settings
  • Outlook Signatures
  • FAQ
  • Troubleshooting
  • Appendix
  • Changelog
  • Packages
    • Package Lifecycle
    • Package Types
    • Prepare Packages
    • Chocolatey Package
    • Craft Package
    • Updating Packages
    • Core Extension
    • Packaging In-Depth
    • Specialised Packages
    • Workflow (internal GK)
    • JSON - Short Overview
    • 3rd Party NuGet Packages
Powered by GitBook
On this page
  1. Core Features
  2. AnyDesk

AnyDesk Cloud Connections

PreviousCustomer TasksNextNotifications

Last updated 3 years ago

All connections are TCP and encrypted with:

  • TLS 1.2

  • RSA 2048bit

  • AES256

  • ECDH

  • AEAD

The following graphic shows you a remote session from an external support to user Y:

Step
Explanation

C1

Outbound connections to AnyDesk Cloud servers on ports 80, 443 or 6568

S0

Optional for sessions - if available direct connection between clients on port 7070

S1

A direct connection is tried to port 7070 towards public IP address of user Y known by AnyDesk Cloud (also hole punching is tried at the same time).

S2

If a direct connection (S1) cannot be established, a session over AnyDesk Cloud servers (S2) is established:

  • External support establishes new connection to the AnyDesk Cloud server where user Y is connected.

  • Data of session (S2) are then transferred:

    • External support over new connection to AnyDesk Cloud server

    • User Y over existing connection to AnyDesk Cloud server