If the service refuses to start, you may need to reinstall AnyDesk on the remote machine.
Open and run:
If you still see error 10061, run through this checklist on the :
If the background service has crashed or failed to start, the machine will refuse incoming connections. Open the (Ctrl+Shift+Esc). Go to the Services tab and look for AnyDesk . If it is stopped, right-click it and select Start .
In the context of AnyDesk, this usually means one of two things:
| Scenario | Why Error 10061 Occurs | |----------|------------------------| | | Your client connects to 192.168.x.x:7070 but the remote AnyDesk service is stopped, crashed, or not running in “accept connections” mode. | | AnyDesk behind NAT with port forwarding | Router forwards external port to internal host, but the internal host’s AnyDesk is not listening (e.g., service not started, or AnyDesk running as “on‑demand only”). | | AnyDesk custom port | Remote is set to listen on port 8888 , but you are trying 7070 – connection reaches the IP but no service on that port → RST. | | Windows Firewall with advanced rules | Firewall allows SYN packets but an application‑layer rule (e.g., “only allow connections from specific IPs”) sends an RST instead of dropping. | | Multiple AnyDesk instances | Two AnyDesk processes trying to bind same port; second one fails and actively refuses connections. |
netstat -ano | findstr :7070
Technically, this is a . The full description is: "No connection could be made because the target computer actively refused it."
Restart AnyDesk service. Attempt connection, then check the log for lines containing bind or listen failures.
Active VPNs or proxy servers can interfere with the direct routing AnyDesk requires, causing the "connection refused" message. Configure firewalls for AnyDesk