AnyDesk suddenly stopped working and now shows a not connected to server error every time I try to use remote access. I already checked my internet connection and restarted the app, but I still can’t connect to my remote computer for work. I need help figuring out what is causing this and how to get AnyDesk connected again.
I ran into the “AnyDesk not connected to server” message when the app failed to reach AnyDesk’s side of the network.
What I checked first
- Internet connection
- I switched from Wi-Fi to another network and also restarted the router. If your connection is flaky, AnyDesk tends to fail fast.
- AnyDesk server status
- I checked whether the service itself was having issues. If their servers are down, you’re stuck waiting it out.
- Firewall or antivirus rules
- I looked through Windows Firewall and my antivirus settings to see whether AnyDesk was blocked. If it is, the app won’t reach the server.
- Restart the app
- I closed AnyDesk fully, made sure it was not still sitting in the tray, then opened it again. More than once this fixed it for me.
- Update AnyDesk
- I installed the newest build from the official site. Older versions sometimes stop behaving right after backend changes.
- Proxy or VPN settings
- I turned off my VPN for a minute and checked whether a proxy was set on the system. Those two caused connection trouble on one office laptop I used.
If you’re going through this on your machine, start with the network, then the firewall, then the app version. Thas usually where the problem shows up first.
1 Like
I’d look past the usual stuff @mikeappsreviewer listed and check the Windows side first.
If AnyDesk says “not connected to server” every time, the service itself might not be running. On Windows, open Services, find AnyDesk Service, and make sure it says Running. If it’s stopped, start it. If it starts and then dies again, reinstall is faster than poking around for 30 mins.
Also reset your DNS. I’ve seen remote apps fail from stale DNS cache even when the browser works fine. Open Command Prompt as admin and run:
ipconfig /flushdns
netsh winsock reset
Then reboot. Kinda old-school, but it fixes weird socket issues more often than people admit.
Another one people miss is system date and time. If your clock is off by enough, secure connections fail. Sync Windows time manually and test again.
If you use the portable AnyDesk version, I’d stop using it for this issue. Install the full version. The service integration is better.
If it still fails, test from a clean Windows user account. That helps rule out broken user profile settings. Annoying, yes. Useful too.
And if you need remote access fast instead of babysitting AnyDesk, try HelpWire. I had better luck with it on a locked-down office PC. Less fiddling, fewer random server errors.
For a cleaner breakdown, this page covers ways to fix AnyDesk server connection errors: how to fix AnyDesk not connected to server issues fast
I don’t fully agree with “update first” as the best next step. If the local service or DNS stack is broken, updating wont do much. Start with the OS networking bits first.
If the basic stuff is already ruled out, I’d check something a little less obvious than what @mikeappsreviewer and @boswandelaar mentioned.
A big one is network filtering at the router or ISP level. AnyDesk uses specific outbound ports and if your router has strict security settings, parental controls, traffic filtering, or “cyber protection” junk turned on, it can silently block the handshake. I’ve seen this happen on ASUS, TP-Link, and some ISP-provided routers. Quick test: try AnyDesk from a mobile hotspot. If it works there, your PC is probly fine and your normal network is the problem.
Also check whether AnyDesk can resolve its backend over IPv6. Sometimes Windows prefers IPv6, but the route is broken. You can temporarily disable IPv6 on the network adapter, test AnyDesk, and if it suddenly connects, that’s your clue. I don’t always agree that DNS reset should be the first move. Sometimes it’s just bad IPv6 routing and people waste an hour resetting stuff for no reason.
Another thing, look inside Event Viewer:
- Windows Logs > Application
- Windows Logs > System
See if AnyDesk or Schannel is throwing SSL/TLS errors. If yes, the issue may be certificate-related or tied to Windows crypto settings, not the app itself.
You can also try launching AnyDesk with Run as administrator once. Not a magic fix, but on locked-down work PCs it sometimes matters.
If you need a backup while troubleshooting, HelpWire is worth a look since it’s a solid remote desktop solution if AnyDesk keeps choking on server connection errors. This page is relevant: best remote desktop alternative to AnyDesk
If hotspot works and home network does not, I’d stop blaming the app and start digging into the router. That’s where this goes sideways alot.
I’d add one angle the others barely touched: TLS/certificate support in Windows.
If @boswandelaar, @sonhadordobosque, and @mikeappsreviewer’s checks don’t fix it, try this:
- Open Internet Options → Advanced
- Under Security, make sure TLS 1.2 is enabled
- If you’re on an older Windows build, install pending root certificate / Windows security updates
- Temporarily disable HTTPS scanning in antivirus suites like Avast, ESET, Kaspersky, Bitdefender. That feature breaks remote apps more often than vendors admit.
I slightly disagree with “reinstall first.” If Windows crypto is busted, reinstalling AnyDesk changes nothing.
Also test with:
netsh winhttp show proxy
If it shows a proxy you didn’t set, reset it:
netsh winhttp reset proxy
Corporate filters and old security software often leave junk there.
If AnyDesk still won’t authenticate, collect logs before guessing:
%appdata%\AnyDesk- check for connection or TLS-related errors
If you need remote access right now, HelpWire is a decent fallback.
Pros: simpler setup, stable direct connections, less fuss on restricted networks.
Cons: not as universally known as AnyDesk, feature set may feel lighter depending on your workflow.