Remote desktop can’t connect? Fixes by message

When a connection fails, the viewer says why. Find the message below. Most problems are the access code, TideDesk not running on the host, Windows Firewall, or a network that cannot open a direct path.

First, the three usual causes

• TideDesk is not running on the host. It must be running there, with Accept new connections ticked on its Share this computer tab. Closing the window keeps it running in the tray; quitting from the tray stops it.
• Windows Firewall blocked it. The first time, Windows asks whether to allow tidedesk. Allow it on private networks. If the question was dismissed, open Windows Security, Firewall & network protection, Allow an app through firewall, and tick tidedesk for private networks, on both computers.
• Different versions. Internet and device-ID connections need both computers on a current release. Update both from the same place you installed them.

Messages about the code or password

“wrong access code”

Since v0.1.0-alpha.10 the host makes a new code after every session. Read the code shown on the host now; the previous one keeps working for 5 minutes after a session ends, then stops. For your own computers, set a password on the host or press Trust this viewer during a session, and you no longer need the code.

“too many failed attempts, try again later”

After 5 wrong codes from one address, the host makes that address wait, longer after each further wrong code, up to an hour. A wrong password counts double. Wait, then use the right code. The host’s Share this computer tab shows which addresses are waiting.

“wrong password” or “the host has no saved password; use its access code”

Passwords are set on the host, under Share this computer. Without one, connect with the access code. Neither computer ever sends the password itself.

Messages about the host

“host already has a viewer connected”

One viewer at a time. The other session must end first.

“host is not accepting connections right now”

Tick Accept new connections on the host’s Share this computer tab.

“protocol mismatch”

The two computers run TideDesk versions that cannot talk to each other. Update both.

Messages about finding the host

“… is not online right now (not registered at …)”

You connected by device ID and the host is not registered with the connection service. Check that the host is switched on, connected to the internet and running TideDesk, and that Reachable by device ID from other networks is on in its Host Settings. A host that just started needs a few seconds to register.

“… was not found on this network”

The viewer asked its local network for that device ID and nobody answered. The host may be on another network (then it needs the connection service), or a firewall, guest Wi-Fi or a VPN keeps the two computers apart. On the same network, try the host’s address shown on its Share this computer tab.

“could not reach a TideDesk host at …” or “… did not answer”

Nothing answered at that address. Check the address and port (the host shows both), that TideDesk is running there, and Windows Firewall on the host. An address like 192.168.x.x only works on the same local network; from elsewhere, use the device ID.

“… answered on this network at … but could not be reached there”

The host was found but the session could not start. This is almost always Windows Firewall on the host allowing the question but not the connection, or a network that isolates its devices (guest Wi-Fi, some hotel and office networks).

“cannot find the connection service …”

The viewer cannot reach rendezvous.tidedesk.app: no internet, a DNS problem, or a network that blocks it. If you changed the connection service in Settings, check that address. On a local network you can always connect by the host’s address instead.

Over the internet: it works at home but not from here

TideDesk always connects your computers directly and never sends a session through a relay. Mobile data and carrier-grade NAT often prevent a direct path. Use a VPN such as Tailscale between the two computers, or forward UDP port 47800 to the host on its router. The mobile data guide explains both.

Still stuck?

Each computer writes what went wrong to tidedesk.log in %APPDATA%\TideDesk. Report the problem on GitHub with the message you saw, both versions (shown under About), and the lines of the log around that time. Remove any addresses you would rather not share.