AllTech
On this page
Field notes from the engineering team
Remote access is one of the most common reasons staff call our help desk. The person is at home, the laptop has internet, and the file share or office application will not open. Most of these calls end the same way: one small thing on the laptop or in a shortcut was out of date.
This guide covers the usual causes, what you can check before you call, and what we look at on our side. It applies to offices that are moving from an old VPN to a managed Zero Trust client, and to offices that are already there.
The short version
| Item | Detail |
|---|---|
| Common cause | A new laptop without the managed remote access client, or an old VPN client still installed. |
| Another common cause | A saved remote desktop shortcut that uses a computer name, not an address IT gave you. |
| First check | Is the remote access client open, signed in and showing Connected? |
| What to tell IT | The exact status or error text on screen, and whether it worked before. |
| What not to do | Do not install a different VPN app, or open a firewall port, to “make it work”. |
Why remote access stops working
Remote staff stop working when the connection fails, and a few things change often enough to cause it: new laptops, retired VPN products, and shortcuts that were saved years ago. The causes below are the ones our help desk sees most.
A new laptop without the remote access client. The laptop was set up for the office network, and the remote access app was never added. At the office it works. At home nothing reaches the office.
An old VPN client is still installed. Many offices are retiring their old VPN. If the old client stays on the laptop, the person opens the wrong app and connects to nothing, or to something that has been switched off. Removing it is part of finishing the move.
A saved shortcut that points to a computer name. A remote desktop shortcut that uses a computer name relies on DNS, the system that turns a name into an address. At the office, DNS knows the name. At home it may not, unless remote access has been set up to resolve it. Cloudflare’s documentation describes two ways to handle this: private hostname routes, which connect users to an internal application by its hostname, and Local Domain Fallback, which sends chosen domains to a DNS server you specify instead of the default resolver.
The office computer is off or unreachable. If the shortcut opens a remote desktop to a computer at the office, that computer has to be on and reachable. Microsoft lists three reasons for the error “Remote Desktop can’t connect to the remote computer”: remote access to the server is not enabled, the remote computer is turned off, or the remote computer is not available on the network.
What to check before you call
These checks take a few minutes and give IT what it needs to fix the problem quickly.
- Confirm the home internet works. Open a public website. If that fails, the problem is the home connection.
- Open the remote access client. On a laptop with our managed client, the client’s window shows its status. It should say Connected. If it shows an error code instead, write the code down.
- Use the shortcut IT gave you. Do not use an old shortcut, a note from a former colleague, or a saved connection from an older laptop.
- Check the office computer. If you connect to a specific desk computer, ask someone at the office to confirm it is on.
- Note what changed. A new laptop, a new router at home, a Windows update, or a password change are all useful clues.
Then call the help desk and give them the exact words on screen. “It says Connected but the file share will not open” and “it will not connect at all” lead to very different fixes.
What IT checks
On our side, the order is the same each time:
- Is the client installed, enrolled and connected? The Cloudflare One Client reports its progress while it connects, with stages such as checking the network, building a tunnel and applying DNS settings. If it stops at a stage, that stage tells us where to look. If it reports an error, the error code points to the cause.
- Is the old VPN client gone? If not, we remove it.
- Is the shortcut correct? We replace a name-based shortcut with one that works away from the office.
- Does the person’s profile include the resource? Cloudflare applies settings by device profile, including which traffic goes through the client. A new hire or a changed role can sit in the wrong profile.
- Did a recent change go out? Cloudflare notes that updated settings can take up to 10 minutes to reach devices. A fix made a minute ago may not have reached the laptop yet.
- Is the office side healthy? The tunnel that connects the office network to Cloudflare is outbound only, which means the office firewall does not need an open inbound port. If the office computer or the tunnel is down, no amount of work on the laptop will help.
For a remote desktop connection that still fails, Microsoft’s troubleshooting guide suggests testing whether the affected computer answers on port 3389 from another machine, and checking whether a firewall or a Group Policy setting is blocking Remote Desktop. That is administrator work. It is not something to try on a personal laptop.
What to do
1. Put the managed remote access client on every laptop before it leaves the office. A new laptop should not reach a user without it. Ask IT to include it in the new-computer checklist.
2. Retire the old VPN client completely. Ask IT to remove it from every laptop, not just stop using it.
3. Replace saved shortcuts with ones IT provides. Delete old remote desktop shortcuts when the new ones go out.
4. Tell IT before a laptop swap or a role change. Remote access follows the person’s profile and the device. A late request is how someone ends up at home with no access.
5. Do not work around it. Installing a personal VPN app or asking a vendor to open a port on the office firewall solves today’s problem and creates a bigger one.
6. Keep the exact error text. A photo of the error window is enough. It saves a round of questions.
How we help
Our help desk handles remote access problems and the checks above. We deploy the client to managed laptops, including through Entra ID and Intune, and move offices off legacy VPNs with ZTNA and VPN replacement built on Cloudflare Zero Trust. Users sign in once, and the client reconnects on its own.
Remote access matters most where staff split time between sites or work from home. Multi-location businesses, law firms and manufacturers all depend on it daily. If remote staff in your office run into these problems, contact us.
Sources
- Cloudflare Docs, Cloudflare One Client
- Cloudflare Docs, Connectivity status
- Cloudflare Docs, Connect with cloudflared
- Cloudflare Docs, Connect a private hostname
- Cloudflare Docs, Local Domain Fallback
- Cloudflare Docs, Split Tunnels
- Microsoft Learn, Remote Desktop can’t connect to the remote computer
- Microsoft Learn, General Remote Desktop connection troubleshooting
