Common issues

Frequent “Connection lost” errors

On macOS 15 Sequoia and later, a session may occasionally end with “Connection has been lost”, even though nothing is wrong with your network or the remote machine. It often happens while you’re working in other apps, and reconnecting works straight away.

Why it happens

macOS 15 introduced Local Network privacy: apps need your permission to connect to devices on your home or office network. You granted RDPlenty this permission the first time you launched the app.

Whenever any app on your Mac is installed or updated, macOS rebuilds its local network permission rules. This includes updates that happen silently in the background, such as Apple’s own security updates, App Store updates, and apps that update themselves. Because of a bug in macOS, rebuilding these rules can cut connections that are already open, including ones from apps that have permission. RDPlenty’s connection is one of them, so the session drops.

This is not specific to RDPlenty. Other developers have reported the same problem to Apple, and it hasn’t been fixed. RDPlenty can’t prevent it: there is no setting, permission, or exemption an app can request to keep macOS from closing its connections.

Only connections to machines on your local network are affected. Connections over a VPN or the internet aren’t, and neither are Macs running macOS 14 or earlier.

Workaround: start RDPlenty from Terminal

macOS doesn’t apply Local Network privacy to programs started from Terminal, so the bug can’t affect them. To start RDPlenty this way:

  1. Quit RDPlenty if it’s running. Otherwise, starting it again just switches to the copy that’s already running.

  2. Open Terminal. It’s in the Utilities folder inside Applications.

  3. Paste this line and press Return:

    /Applications/RDPlenty.app/Contents/MacOS/RDPlenty &
    

    The & at the end runs RDPlenty in the background, so the Terminal window stays free for other commands. If RDPlenty is installed somewhere other than Applications, adjust the path to match.

  4. Keep the Terminal window open while you use RDPlenty. You can minimize it or move it out of the way, but closing the window or quitting Terminal also quits RDPlenty.

The window may show some text while RDPlenty runs. You can ignore it.

You need to do this each time you start RDPlenty. Starting it the usual way, from the Dock, Finder, or Launchpad, makes it subject to Local Network privacy again.

Disconnect after connecting to a just-awoken machine

If you wake a Windows PC (for example, with Wake-on-LAN) and connect to it right away, the session may start normally, show the remote desktop, then freeze for a few seconds and end with “Connection has been lost”. Reconnecting works, and the new session stays up.

Why it happens

When Windows wakes up, it doesn’t immediately know which network it’s on. For the first several seconds it’s identifying the network, and during that time it treats the connection as a Public network. Once it recognizes your home or office network, it switches to Private.

If your remote session started during those first seconds, it was opened while the network was Public. When Windows then switches to Private, it cuts that open connection. Any connection made after the switch is unaffected, which is why reconnecting works.

This happens on the Windows side, so it affects every remote desktop client, including Microsoft’s own Windows App. RDPlenty can’t prevent it.

Workaround: treat networks as Private while Windows identifies them

Warning

Only do this if the Windows PC always wakes up on a network you trust, such as a desktop on your home or office network. Don’t do it on a laptop that may wake up on public Wi-Fi in a café, hotel, or airport. With this setting, Windows treats every network as Private while identifying it, so for those first seconds a public network would get the same trust as your home network, including file sharing and network discovery if you use them.

Windows has a setting that decides how a network is treated while it’s being identified. Setting it to Private means there’s no switch, so the connection isn’t cut.

This setting is in the Local Security Policy tool, which is available on Windows Pro, Enterprise, and Education, but not on Windows Home.

On the Windows PC:

  1. Press Windows+R, type secpol.msc, and press Return. Approve the administrator prompt if one appears.

  2. In the left pane, select Network List Manager Policies.

  3. In the right pane, double-click Identifying networks.

  4. Under Location type, choose Private and click OK.

To undo it, repeat these steps and choose Not configured.