AnyDesk Not Connecting | Fix Timeouts And Blocked Ports

You click Connect, type the remote ID, and then you’re stuck staring at a spinner. It’s annoying, and it’s also fixable. The trick is to stop guessing and run a short, repeatable check that separates “their side” from “your side,” then drills into the handful of settings that break remote sessions.

This walkthrough fits home Wi-Fi and office networks. You’ll start with a quick triage, then move into fixes that solve most cases of anydesk not connecting without a reinstall.

Start With A Fast Triage

Before you change settings, get two facts: can your device reach the AnyDesk network, and is the remote device able to accept a session. Five minutes here saves an hour later.

• Check the remote device — Ask the person on the other end to confirm AnyDesk is open, the device is awake, and it’s on the internet.
• Try a second network — Hotspot your phone or switch Wi-Fi to see if the issue follows the network or the device.
• Test a second target — Connect to a different AnyDesk ID you trust. If that works, the problem is likely on the original remote device.
• Note the exact message — “Disconnected from the AnyDesk network,” “Network timeout,” and “Session denied” point to different fixes.

Use This Quick Symptom Table

If you’re not sure where to start, match what you see to the first move that tends to work.

Check AnyDesk Network Status And Your Internet

Start with the simplest possibility, an outage or a shaky connection. AnyDesk runs through its own global network, so a service issue can look like a local problem. Open AnyDesk’s status page in a browser and confirm your region shows as operational. If there’s an incident, you’re done. Wait, then try again.

If the status page looks normal, test your internet for dropouts. Load two less-used sites, then ping a public DNS server. If you see packet loss, fix the link first.

• Restart your router — Power it off for 20 seconds, then bring it back up and reconnect.
• Switch bands — Try 5 GHz instead of 2.4 GHz if your router offers both.
• Pause heavy uploads — Cloud backups and large file uploads can choke upstream bandwidth.
• Retry with a clean path — Disconnect a VPN and retry once, then test again with the VPN on.

Fix Firewall, Ports, And Filtering

If AnyDesk works on a hotspot but not on your main network, treat it like a block. AnyDesk needs outbound access on at least one common TCP port. Many networks allow web traffic on 80 and 443, yet still block the specific destinations or add inspection that breaks encrypted sessions.

Allow The Ports AnyDesk Uses

On most networks, opening TCP 443 is the cleanest first step, since it blends with normal HTTPS traffic. AnyDesk can also use TCP 80 and TCP 6568. On a local LAN, its device discovery feature can use UDP ports 50001–50003 with multicast traffic.

• Open outbound TCP 443 — Allow your device to reach the AnyDesk network over port 443.
• Allow TCP 80 or 6568 if needed — If 443 is filtered, permit one of the other TCP options.
• Permit discovery traffic on LAN — If you rely on device discovery, allow UDP 50001–50003 and multicast on your local network.

Whitelist AnyDesk Network Domains

Some security gateways allow ports but still block the destination by category, reputation score, or strict allow-lists. AnyDesk recommends whitelisting its network domain so the client can reach the servers and keep a session alive.

• Add the AnyDesk network domain — Whitelist *.net.anydesk.com in your firewall, proxy, or web filter.
• Skip SSL inspection for AnyDesk — If your gateway runs HTTPS scanning or deep packet inspection, exempt AnyDesk traffic so TLS stays intact.

Fix Windows Firewall Prompts You Clicked Away

On Windows, portable mode can trigger a firewall prompt the first time you connect. If you denied it, AnyDesk may fail to establish or keep connections until you allow it.

1. Open Windows Security — Go to Settings, then Privacy & security, then Windows Security.
2. Open Firewall & network protection — Tap into the firewall section.
3. Allow an app through firewall — Find AnyDesk and tick both Private and Public where it applies.
4. Retry a connection — Close AnyDesk, reopen it, then connect again.

Fix Proxies, DNS, And System Time

When ports are open and it still won’t connect, look for “invisible” blockers: proxy settings, DNS resolution, and a clock that’s out of sync. Each can break certificate checks or route your session into a dead end.

Sync The Clock So Certificates Validate

If your system date or time is off, encrypted connections can fail. AnyDesk calls out clock sync as a common fix for network-disconnect errors because TLS certificates depend on correct time.

• Turn on automatic time — Set your device to sync time with the operating system’s time service.
• Force a sync — Run the “Sync now” option, then reopen AnyDesk.
• Check time zone — Make sure your time zone matches your location, then retry.

Verify DNS Can Resolve AnyDesk

If DNS can’t resolve AnyDesk hostnames, the app can’t find the network it needs.

1. Test DNS in a browser — Open the AnyDesk status page. If it won’t load, DNS or filtering may be in the way.
2. Switch DNS servers — Try a well-known public DNS resolver on your device, then test again.
3. Flush the DNS cache — Clear cached lookups, then relaunch AnyDesk.

Check AnyDesk Proxy Settings

Proxy auto-detection can be wrong, and a manual proxy can break remote sessions if it can’t tunnel encrypted traffic cleanly. AnyDesk’s client settings let you choose no proxy, auto detect, or manual setup. The proxy must allow the CONNECT method and must not interfere with SSL/TLS traffic.

1. Open AnyDesk Settings — Click the menu in the app, then open Settings.
2. Go to Connection — Find the proxy area and confirm the correct mode.
3. Try No proxy — If you’re on a home network, set No proxy and retry.
4. Confirm proxy capability — On office networks, confirm the proxy allows CONNECT without TLS meddling.

AnyDesk Not Connecting On Windows Or Mac

Once the network path is clean, the next set of failures comes from local settings that block incoming sessions or force a slow route. This section is also where you fix “It works on one machine but not the other” cases.

Check Direct Connections And The Local Port

AnyDesk can try a direct connection between two clients. That can be faster, yet it also means a local port setting can matter on restrictive networks. In the AnyDesk Connection settings, direct connections use a local TCP listen port (7070 by default), and you can set a custom port.

• Toggle direct connections — In Settings, switch Allow direct connections off and on, then retry.
• Reset the local port — Set the local port back to default, or pick a new allowed port if your network blocks 7070.
• Retry from the same network — Test again while both devices stay on the same Wi-Fi to rule out NAT quirks.

Review Access Control Lists And Unattended Access

A connection can fail instantly if the remote device is set to accept only certain IDs or aliases. AnyDesk’s Access Control List works like a whitelist: devices not listed get blocked. Unattended Access rules can also block a session if the remote device requires credentials and no one can accept the prompt.

• Check the remote ACL — On the remote device, open Settings, then Security, then Access Control List.
• Add your ID — Add your AnyDesk ID or alias to the list, then save.
• Confirm interactive prompts — Set incoming requests to show the accept window when someone is there to tap Accept.
• Set unattended credentials — If no one is at the remote device, set a password for unattended access and test again.

Make Sure The Remote Device Is Actually Reachable

This sounds obvious, yet it trips people all the time. A laptop can look “online” in your head while it’s asleep, on battery saver, or stuck behind a login screen that needs a local click.

• Disable sleep for testing — Keep the remote device awake for ten minutes while you connect.
• Plug in power — Some laptops cut Wi-Fi on low battery, which drops remote sessions.
• Confirm AnyDesk permissions — On macOS, screen recording and accessibility permissions can block control even if the session starts.

When It Still Won’t Connect

If you’ve cleared the basics and it still fails, narrow it down with one last loop. You’re trying to learn whether the block is tied to your device, the remote device, or your account limits.

Use Error Messages As Clues

AnyDesk’s error messages are blunt on purpose. A “disconnected from the AnyDesk network” message points to server reachability, DNS, time sync, or filtering. A “session was denied” message points to remote access settings, ACL rules, or permission profiles. If your license limits the number of sessions, you may see a message that your session limit is exceeded and you’ll need to close other sessions.

• Recreate the error — Attempt the connection once, then write down the exact wording.
• Change one thing — Adjust a single setting, then retest so you know what moved the needle.
• Try a clean install path — Remove AnyDesk, reboot, then install the latest build from AnyDesk.

Separate Cloud From On-Premises Setups

If your company runs AnyDesk on-premises, the path is different. Your client must reach your organization’s server, not the public AnyDesk cloud. In that setup, make sure your device can reach the on-prem server host, and keep system time synced so authentication and certificates don’t fail.

Know When To Stop And Escalate

If a security gateway is doing HTTPS scanning, if a corporate proxy rewrites certificates, or if an allow-list blocks unknown domains, you may not be able to fix it from the client side. At that point, bring your network admin a simple request: allow outbound TCP 443 to the AnyDesk network domain, exempt it from TLS inspection, and confirm DNS resolution works. That’s a clear ask, and it maps to what AnyDesk documents.

With a clean network path, AnyDesk should connect fast and stay stable. If the snag returns, run the same triage loop.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback