Remote Work Depends on Remote Access

Remote access failures — VPN not connecting, Remote Desktop refusing connections, or remote sessions constantly dropping — can completely stop remote workers in their tracks. Most problems fall into a small number of categories: authentication, firewall rules, network routing, or software configuration. This guide covers the most common scenarios and their fixes.

VPN Not Connecting

Start With the Basics

  • Verify credentials — passwords expire on corporate VPNs; check if your domain password recently changed
  • Update the VPN client — outdated clients often have authentication failures after server-side updates
  • Try a different VPN server if your client offers multiple locations
  • Restart the VPN service: on Windows, open services.msc, find your VPN's service, and restart it

Specific Error Types

  • Authentication failed / invalid credentials: Try resetting your VPN account password via your IT portal. Enable MFA if required and not set up.
  • Connection timed out / can't reach server: Your ISP or local firewall may be blocking VPN traffic. Try a different network (phone hotspot) to isolate whether it's your home network.
  • DNS not resolving after connecting: VPN connected but can't reach internal resources by name. Check DNS settings — the VPN should push internal DNS servers. Manually set DNS to your VPN gateway's internal DNS IP.
  • Split tunnel problems: VPN traffic routes correctly but regular internet traffic breaks. Contact IT to check the split tunnel configuration.

Remote Desktop (RDP) Issues

Enable Remote Desktop on the Target Machine

  1. On the computer you want to connect to: Settings → System → Remote Desktop → toggle On.
  2. Ensure the account you're using to connect has Remote Desktop access — only Administrators have it by default. To add others: Remote Desktop Settings → User accounts → Add.

Firewall Rules

Windows Firewall blocks RDP by default from external networks. To allow RDP through:

  1. Control Panel → Windows Defender Firewall → Allow an app or feature → check Remote Desktop for both Private and Domain networks.
  2. If connecting over the internet (not VPN), you'll also need to configure port forwarding on the router — RDP uses port 3389 by default.

Never expose RDP directly to the internet. Port 3389 open to the public internet is one of the most attacked vectors in existence. Always use RDP over a VPN, or use a remote desktop tool with its own secure tunnel (like TeamViewer or AnyDesk) instead of direct RDP for internet access.

Common RDP Error Messages

  • "Remote Desktop can't connect to the remote computer": Target machine is off, asleep, or firewalled. Confirm the target is powered on and reachable by ping.
  • "The credentials that were used to connect did not work": The account may be disabled, locked, or the password changed. Also check that the username is typed as DOMAIN\username for domain accounts.
  • "The remote computer requires Network Level Authentication": The connection client doesn't support NLA, or the connecting machine doesn't have a compatible credential. Update the RDP client or contact IT.
  • "This computer can't connect to the remote computer": Often an SSL/TLS certificate issue between old and new Windows versions. Enable "Allow connections from computers running any version of Remote Desktop" as a temporary workaround.

Third-Party Remote Tools

For non-corporate remote access, third-party tools are simpler than VPN+RDP:

  • TeamViewer: Free for personal use, cross-platform, no firewall configuration needed
  • AnyDesk: Similar to TeamViewer, often faster
  • Chrome Remote Desktop: Free, runs in Chrome browser, easiest to set up
  • Windows Quick Assist: Built into Windows 10/11 for quick help sessions

We set up remote access. Whether you need VPN configured, Remote Desktop enabled, or a reliable remote tool set up for personal or business use, bring your machine in and we'll configure it correctly and securely.