- AnyDesk may not connect due to issues like internet problems, incorrect settings, or device conditions such as being offline or asleep. To fix it, you need to first identify what might be causing the problem, like checking your internet connection, ensuring devices are awake, or making sure AnyDesk is running properly.
- Solving connection problems involves trying various fixes for each step, like checking your network settings, ensuring AnyDesk is updated, and verifying firewall permissions. If the remote device needs approval for connection, make sure to configure the correct settings for either manual or unattended access, using the right password as needed.
AnyDesk not connecting can interrupt remote work, delay technical support, or leave you unable to access important files. Sometimes the application reports that it cannot reach the AnyDesk network. Other times, the remote computer appears offline, rejects your request, or connects without displaying a usable screen.
The right fix depends on where the connection fails. This guide explains how to identify the problem and troubleshoot it on Windows, macOS, Linux, and Android without making unnecessary changes.
Why Is AnyDesk Not Connecting?
AnyDesk lets you view and control another device remotely. For a standard cloud connection, both devices need working network access, a running AnyDesk client, and settings that permit the session.
Start by identifying which situation matches yours:
- Your AnyDesk client is disconnected: Investigate your internet connection, system clock, DNS, and security software.
- Only one remote device appears offline: Check that device’s power, connectivity, and AnyDesk application.
- The request reaches the remote device but fails: Review approval requirements, credentials, and access restrictions.
- The session opens but is unusable: Check display permissions, input permissions, and platform compatibility.
These distinctions help you avoid changing your own computer when the problem is elsewhere.
How to Fix AnyDesk Not Connecting
1. Check for an AnyDesk Service Outage
Visit the AnyDesk status page before reinstalling anything. Check for an active incident affecting connections and review its latest update.
If several unrelated devices stop connecting simultaneously, a service issue becomes more plausible. However, a normal status page does not rule out a local network problem or an incident that has not yet been reported.
2. Confirm the Remote Device Is Available
A computer that is asleep, disconnected, or no longer running AnyDesk cannot accept a normal remote session. Ask someone near the device to perform these checks:
- Turn on the computer and wake it from sleep.
- Confirm that it has internet access.
- Open AnyDesk and check its connection status.
- Read back the current AnyDesk ID or alias.
Enter that address again instead of relying on an old saved entry. If the computer repeatedly becomes unavailable after being idle, review its sleep settings for the periods when remote access is needed.
3. Test the Internet Connection on Both Devices
Open several websites on each device. If browsing also fails, resolve that connection problem first, including any hotel, office, or public Wi-Fi sign-in page.
Next, test AnyDesk through another permitted connection, such as a phone hotspot. Change the network on one device at a time so you can identify which side makes the difference.
If AnyDesk works through the hotspot but fails through your usual Wi-Fi, that points toward the original network, its DNS service, or filtering rules. It does not automatically prove that the router itself is faulty.
4. Restart AnyDesk and Update Both Clients
Close and reopen AnyDesk on both devices. If it remains unresponsive, save open work and restart the affected computer when someone can restore access if necessary.
Check both clients for updates through the official AnyDesk download source or your organization’s approved deployment process. Updating only your own device leaves an outdated remote installation unchanged.
For an installed Windows client, you can also open services.msc, locate the AnyDesk service, and restart it if available. Restarting the remote service disconnects active sessions, so coordinate this action beforehand.
5. Correct the Date and Time
An incorrect system clock can interfere with certificate validation. A computer may browse normally while still failing to establish a secure AnyDesk connection.
- On Windows, open Settings > Time & language > Date & time.
- Enable automatic time, verify the time zone, and select Sync now.
- On macOS, find Date & Time in System Settings and enable automatic time.
- Reopen AnyDesk and retry.
Check the remote computer’s clock too. AnyDesk specifically recommends synchronized time, working DNS resolution, and permitted server traffic in its network troubleshooting guidance.
6. Review Firewall and Antivirus Restrictions
Security software can block AnyDesk even when ordinary browsing works. Review its blocked-application history and create an appropriate exception for the legitimate AnyDesk application.
On Windows, open Windows Security > Firewall & network protection > Allow an app through firewall. Select Change settings, locate AnyDesk, and allow it on the network profiles where you need access.
For managed networks, give the administrator these requirements:
- AnyDesk uses TCP ports 80, 443, and 6568; at least one must be available.
- The server domain pattern *.net.anydesk.com should be allowed.
- HTTPS inspection or deep packet inspection may interrupt encrypted sessions.
- UDP ports 50001–50003 support local discovery, rather than every remote connection.
7. Check VPN, Proxy, and Direct Connection Settings
If the problem began after enabling a VPN, briefly disconnect it and test again where organizational policy permits. On company networks, ask IT to verify the required proxy configuration rather than removing it.
For sessions that connect and then terminate, open Settings > Connection > General and temporarily clear Allow direct connections. Reconnect and compare the result.
8. Fix Approval and Unattended Access Settings
If the remote computer receives your request, basic connectivity is already working. Check whether someone needs to accept the session or whether its settings prevent the acceptance window from appearing.
Under Settings > Access > Interactive Access, review when incoming requests are shown. Selecting the option that never displays requests requires correctly configured Unattended Access.
For unattended connections, open Settings > Access on the remote desktop and configure an Unattended Access password. Use that password when connecting, plus an authentication code if two-factor authentication is enabled.
Do not confuse this password with your AnyDesk account login. Installing AnyDesk can also help maintain availability after restarting or signing out.
Platform-Specific AnyDesk Connection Fixes
Mac: Connected but Cannot View or Control the Screen
Open System Settings > Privacy & Security on the remote Mac. Grant AnyDesk screen-recording permission for viewing and Accessibility permission for keyboard and mouse control, then restart the application if prompted.
Full Disk Access relates to file access and transfer, so it is not a universal connection fix. Check the permissions appropriate to the failed feature using AnyDesk’s.
Android: Missing Prompts or Sessions That Keep Closing
Open AnyDesk’s setup checklist and complete the relevant permissions. If you can see the screen but cannot control it, install the control plugin recommended by AnyDesk and enable its Accessibility permission.
For background disconnections, allow unrestricted battery usage for both AnyDesk and its plugin. On Android 10 and newer, a system screen-sharing confirmation may still require someone physically present, even with Unattended Access enabled.
Linux: Unsupported Display Server
AnyDesk requires an Xorg graphical session for incoming Linux connections. Wayland supports outgoing sessions but does not support receiving them.
If the remote Linux computer uses Wayland, select a supported Xorg or X11 session at login if available. Changing firewall rules will not resolve this compatibility limitation.
Additional Troubleshooting Tips
Change one setting at a time and retry after each change. Record the exact error, whether one or every remote device fails, and whether another network works.
Avoid deleting AnyDesk configuration folders as a first response. If reinstalling becomes necessary, preserve your settings and arrange another way to access the remote computer.
For support escalation, include both operating systems, client versions, timestamps, screenshots, and diagnostic information requested by support. Never include unattended-access passwords.
Frequently Asked Questions
Why Does AnyDesk Fail When My Internet Works?
Working websites do not prove that AnyDesk traffic is permitted. Application filtering, proxy settings, DNS problems, or an incorrect clock can affect AnyDesk separately.
What Does desk_rt_ipc_error Mean?
This error indicates that an external application or operating-system component terminated the session.
Will Reinstalling AnyDesk Fix Every Connection Problem?
No. Reinstalling cannot resolve a sleeping remote computer, service outage, restrictive network policy, or unsupported display environment. Diagnose those possibilities first.
Final Thoughts
When AnyDesk is not connecting, identify whether the failure involves network access, remote-device availability, session approval, or screen control. Start with simple checks, then apply the fix that matches the symptom. This approach saves time and avoids unnecessary changes.
