Can't connect to a server

Saved hosts on the Connections page normally connect straight from your PC to the server, not through the RemoteAccessApp relay you choose in relay location. When one fails, its tab shows Connection failed or Couldn't connect with the reason, and a Reconnect button. To try the details before saving, use Test in the host's settings.

Connection refused

The server answered, but nothing accepted the connection. Usually:

• the service isn't running there (SSH, Remote Desktop or the VNC server),
• the port in the address is wrong, or
• a firewall on the server or the network said no.

For Remote Desktop, also check that Remote Desktop is turned on for that computer.

Timed out or no reply

Nothing answered in time. The server may be off or asleep, the address may be wrong, or a firewall may be silently dropping the connection. Check that you can reach the server from this PC at all: for a server on a private network, you may need to be on that network or its VPN.

Name not found

That name isn't known on this network or Host not found means the server's name couldn't be looked up. Check the spelling, or use the server's address instead of its name.

Wrong user name or password

Messages like "refused the user name or password" or "Sign-in failed" mean the server turned down the sign-in.

1. Check the user name, and for Remote Desktop the domain, in the host's settings.
2. Edit the host and type the password again: a saved password may be out of date.
3. If the server uses keys, see SSH keys.

RemoteAccessApp never sends your password to a server whose key you didn't trust. See server keys.

Still stuck?

Try connecting from another tool on the same PC. If that fails too, the problem is between this PC and the server, not in RemoteAccessApp. If only RemoteAccessApp fails, make sure it's on the current version: Settings, then Updates, has Check for updates (see automatic updates).