How to Fix: Windows VPN Error 800 (‘The remote connection was not made’)

Quick Fix

Fastest fix: Open your VPN connection’s Properties, go to the Security tab, and instead of leaving ‘Type of VPN’ set to Automatic, manually pick the exact protocol your provider uses (for example IKEv2, L2TP/IPsec, SSTP, or PPTP). Save and reconnect. This alone resolves Error 800 in most cases because Automatic mode fails silently when even one protocol handshake breaks.

1. Confirm the server is reachable by pinging its address from an elevated Command Prompt.
2. Temporarily disable your firewall/antivirus to rule out blocking, then re-enable it and add an exception for the VPN app instead.
3. Double-check the server address, username, and password for typos.

Step-by-Step Guide

What VPN Error 800 Means

On Windows, Error 800 shows up as a message resembling: ‘The remote connection was not made because the attempted VPN tunnels failed. The VPN server might be unreachable.’ It is essentially a catch-all failure code. This error comes when the VPN tunnel type is set to ‘Automatic’ and the connection establishment fails for all the VPN tunnels. It occurs when the VPN client is unable to reach the server, and is often caused by a problem with the network connection, for example when the network is down or overloaded.

Common root causes include: an unreachable or offline VPN server, blocked ports on your firewall/router/ISP, incorrect or outdated VPN client settings, an outdated VPN app, or a mismatched security/authentication configuration (especially with L2TP/IPsec). Causes can include an outdated VPN application, VPN connection timeout, connectivity issues with your own internet, incorrectly configured VPN protocol/encryption settings, software conflicts, or server-side downtime or high traffic.

Step 1: Do the Quick Checks First

1. Confirm your regular internet connection works (load a couple of websites) before blaming the VPN.
2. Restart your PC and, if possible, restart your router/modem.
3. Re-check the VPN server address, username, and password for typos — make sure the VPN username and password are correct, and if unsure, log into your provider’s account dashboard and reset the password.
4. If your VPN app was recently updated or changed, try disconnecting fully and reconnecting from scratch — removing the current VPN connection and re-entering the same setup information exactly as done originally surprisingly fixes the problem often.

Step 2: Test Whether the Server Is Actually Reachable

1. Press Windows Key + X and choose Command Prompt (Admin) or Terminal (Admin).
2. Enter ping followed by the address you want to ping, for example ping myvpnaddress.com, then press Enter and see how long it takes for the server to respond.
3. Keep in mind some firewalls block the ping command itself, so no response does not automatically mean the server is down — you can also wait a few minutes and try connecting again.
4. If you are connecting via a raw IP address instead of a domain name, this specific issue can occur when trying to access the VPN server by IP address, and switching to a regular address (adding the VPN’s IP to the Windows hosts file) can fix it.
5. If the server does not respond at all and this happens consistently on one server, try a different server location if your provider offers one, or contact the provider to check server status.

Step 3: Manually Set the VPN Tunnel Type (Most Effective Fix)

1. Open Settings > Network & Internet > VPN (Windows 10/11), click your VPN connection, then ‘Advanced options’, or find it in classic Network Connections > right-click your VPN > Properties.
2. Go to the Security tab.
3. If you know which tunnel type should actually be used for your setup, set ‘Type of VPN’ to that specific protocol rather than Automatic, via Network Connections > right-click your connection > Properties > Security tab.
4. Try IKEv2, SSTP, L2TP/IPsec, or PPTP specifically, then save and reconnect. If using a third-party VPN app rather than the built-in Windows client, open its Settings, go to Protocol, and switch between IKEv2, OpenVPN, or WireGuard.
5. If using L2TP/IPsec specifically, make sure a pre-shared key is entered — select L2TP/IPSec for VPN Type, click Advanced, select ‘Use preshared key for authentication’, since the Windows VPN Setup Wizard does not ask for the shared key during initial setup.

Step 4: Check Firewall, Antivirus, and Router Port Settings

1. Temporarily disable your Windows Firewall and any third-party antivirus, then retry the connection. If the connection succeeds without the firewall, it’s a clear sign your firewall settings need adjusting.
2. Instead of leaving it off, add a proper exception: open Control Panel > System and Security > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall, click Change settings, then find your VPN app and tick both Private and Public, or click Allow another app, browse to the VPN program, and add it.
3. Make sure the correct ports are open on your firewall and router for your protocol:
4. For PPTP: PPTP port (TCP 1723) or GRE Port (47) must not be blocked.
5. For L2TP: correct pre-shared keys must be present on the client, and L2TP port (UDP 1701) must not be blocked by your firewall.
6. For IKEv2: IKE ports (UDP port 500, UDP port 4500) must not be blocked.
7. For SSTP: the SSTP protocol port (TCP 443) must not be blocked.
8. Log into your router’s admin page (commonly 192.168.1.1 or 192.168.0.1) and check Port Forwarding / VPN Passthrough settings — ensure that L2TP and IPSec pass-through options are enabled from your router, as this may cause the problem.
9. If you have more than one VPN client installed, make sure only one of them is active, as several clients may interfere and cause the problem.

Step 5: Reset Network Components

1. Reset the network adapter: open Device Manager, expand Network Adapters, and for stubborn L2TP issues some users report success after opening Device Manager, expanding network adapters, uninstalling all miniport adapters, then scanning for hardware changes.
2. Reset Winsock and TCP/IP from an elevated Command Prompt: run ‘netsh winsock reset’ and ‘netsh int ip reset’, then restart your PC. Resetting Winsock can help fix VPN error 800, especially if the issue is related to network socket problems, since it returns network settings to their default configuration and can resolve issues caused by corrupt or modified network settings.
3. If using the built-in Windows VPN client, you can also reset just the VPN entry: go to Settings > Network & Internet > VPN, click the problem connection, and select Reset VPN (on newer Windows builds) or simply delete and recreate the connection.
4. Update your network adapter drivers from the manufacturer’s website, and check for pending Windows updates.

Step 6: Rule Out ISP-Side Blocking

1. Some ISPs block the GRE protocol remotely, which causes this error; contact your ISP and ask them to unblock GRE if you rely on PPTP.
2. If your VPN app supports switching transport, some VPN apps allow switching between TCP and UDP; error 800 is common when using UDP, so switching to TCP in the app’s protocol settings often fixes it.
3. Try connecting from a different network (mobile hotspot) to see if the problem follows you — if it connects fine elsewhere, the issue is specific to your home network/router/ISP.

Step 7: Reinstall the VPN Client

1. If nothing above works, completely uninstall the VPN app via Settings > Apps > Apps & Features, restart your computer, then download and install the latest version from the official website and reconfigure it from scratch.

When to Seek Further Help

If you’ve verified credentials, tried a fixed protocol, opened the correct ports, reset network components, and reinstalled the client but Error 800 persists, the problem is likely on the server or provider side. Platform note: This is a Windows-specific error code; error 800 is a Windows-specific code, and other platforms use different wording for failed VPN connections, so Mac/mobile users seeing similar symptoms should look up their platform’s equivalent message instead. For work/corporate VPNs, contact your IT department, since server-side RRAS/firewall configuration is often outside your control. For a paid consumer VPN service, contact that provider’s support to check for server outages or account-specific restrictions, and consider trying a different server location in their app in the meantime.