Local network and Wake-on-LAN

Direct connections

When you connect by ID and both PCs are on the same network (or behind the same internet address at one site, with routed networks inside), the app tries to connect straight to the remote PC while it also tries the server's relay, and keeps whichever works first. A direct connection is faster and doesn't use the server's bandwidth; the session window's status line says Direct (LAN).

For direct connections to work:

the remote PC has Accept direct connections from the local network on (Settings > Security, on by default),
your PC can reach the remote PC's port 21118 (or the port it is set to). The installer opens it in Windows Firewall on private and domain networks; on a network Windows treats as public, the session uses the relay.

Direct connections still go through your server's introduction: the remote PC only accepts sessions the server set up, unless direct IP access is on (below). If your PCs always use the relay even on the same network, see Troubleshooting.

Connecting by address, without a server

On a network without an Obsidian Remote server, or to reach a PC that isn't registered with yours, you can connect to its network address: see Connecting to a computer. The remote PC must have Allow direct IP access without the server on. Leave that off unless you need it, and only use it on a network you trust: anyone who can reach the PC's port can then try its password.

The first time, you check the PC's key by hand (the server isn't there to vouch for it), and the app remembers it.

LAN discovery

The Discovered tab in the main window lists Obsidian Remote PCs on your local network, with their names, IDs and addresses. It searches the first time you open the tab; the magnifier button (Search the local network) searches again.

A PC shows up there when Answer LAN discovery is on in its Settings > Security (on by default). It answers only PCs on the local network. Discovery uses UDP port 21119, which the installer opens in Windows Firewall for the local subnet, on private and domain networks only.

Double-click a discovered PC to connect. With a server set up, the app connects by its ID; without one, it connects to its address, which needs direct IP access on that PC.

If No Obsidian Remote hosts answered on this network, the PCs may have LAN discovery off, be on another subnet, or be on a network Windows treats as public.

Wake-on-LAN

You can wake an Obsidian Remote PC that is asleep or switched off, if its network card and its BIOS or UEFI settings allow Wake-on-LAN. On most PCs it only works over a wired network connection.

From the app:

Right-click the device and choose Wake up (Wake-on-LAN). The item is there on the Server devices tab, and for devices whose network card the app knows: the ones on the Discovered tab, and favourites you added from there.
For a device it found on the network, the app sends the wake-up on your own network, then says it sent it. (Discover the PC while it is on, and add it to Favourites, so you can wake it later.)
On the Server devices tab, the server asks another online Obsidian Remote PC at the same site (behind the same internet address) to send the wake-up for you. This works from anywhere.

From the admin console, the Wake on LAN button next to an offline device does the same as the server's wake-up.

Give the PC a minute to start, then connect. On an installed PC, Obsidian Remote is online as soon as Windows has started, before anyone signs in.

If nothing happens: check that Wake-on-LAN is enabled in the PC's firmware and in the network card's settings in Windows, that the PC is connected by cable, and (for a server wake-up) that another Obsidian Remote PC at that site is online.