VPN 868 Error: What It Means and How to Fix It on Windows

VPN error 868 means Windows couldn’t find your VPN server: the full message reads “The remote connection was not made because the name of the remote access server did not resolve.” In practice it’s almost always a wrong or outdated server address, a DNS problem on your network, or security software blocking the connection, and you can usually fix it in a few minutes by checking those three things in order.

Below we explain what the error actually means, then walk through the fixes from quickest to most involved. The steps apply to Windows 10 and Windows 11 as of October 2026.

What error 868 actually means

Every VPN connection starts with a lookup. Your computer takes the server name you were given (something like vpn.example.com) and asks a DNS server for its IP address. Error 868 is Windows’ Remote Access (RAS) error for when that lookup fails.

A responder in the Microsoft Q&A thread on error 868 sums it up: the code indicates the name of the remote access server did not resolve, so the first question is whether you can resolve the VPN server name to an IP address at all.

VyprVPN’s support team describes it more broadly as a connection failure that can occur with PPTP, L2TP and IKEv2, caused either by a configuration error or by something blocking access to the VPN servers. So while DNS is the textbook cause, firewalls and antivirus tools are worth checking too.

One detail that confuses people: some troubleshooting sites, such as AnyViewer, report that Windows 7 showed this message with the code 868, while newer Windows versions may show only the text. If you see the “did not resolve” wording without a number, this guide still applies.

Common causes at a glance

How to fix VPN error 868

Work through these in order and test the VPN after each one.

1. Check the server address

A typo or an outdated server name is the simplest explanation, and it’s easy to miss.

1. Open Settings > Network & internet > VPN.
2. Select your VPN connection and choose Advanced options (or Edit).
3. Compare Server name or address character by character with what your provider or IT department gave you.
4. If your organization recently changed VPN servers, ask for the current address.

If you use a provider’s own app rather than the built-in Windows VPN, make sure you’ve picked a server from the app’s list rather than typing one in.

2. Confirm the name resolves

Because 868 is a name-resolution failure, it helps to test that directly.

1. Open Command Prompt.
2. Type nslookup followed by a space and your VPN server name, then press Enter.
3. If you get back an IP address, DNS is working for that name and the problem is more likely firewall or server-side.
4. If you get an error such as “Non-existent domain” or a timeout, the problem is DNS or the server name itself.

3. Flush DNS and reset Winsock

VyprVPN’s support article recommends clearing the DNS cache and resetting Windows’ network stack. This clears out stale or corrupted lookup results.

1. Search for cmd, right-click Command Prompt and choose Run as administrator.
2. Run ipconfig /flushdns.
3. Run netsh winsock reset catalog.
4. Restart your computer and try the VPN again.

4. Try the server’s IP address instead of its name

If DNS on your current network is the problem, you can bypass the lookup. A long-standing suggestion in Microsoft’s Q&A threads is to enter the VPN server’s IP address instead of its domain name in the connection properties.

1. Get the server’s IP address from your VPN provider or IT administrator (or from a working nslookup on another network).
2. Edit the VPN connection as in step 1 and replace the server name with the IP address.
3. Save and connect.

A caveat: some providers and corporate setups rotate IP addresses or rely on the name for certificate checks, so this may not work everywhere. Treat it as a test, and ask your provider before making it permanent.

5. Try a different network or DNS server

Microsoft Q&A responders have pointed out that some networks’ DNS servers fail to return the correct answer for VPN server names, for example on hotel, public or restrictive networks. To check:

1. Connect your PC to a different network, such as your phone’s hotspot, and try the VPN.
2. If it works there, the original network’s DNS is the likely culprit. Restarting your router is a reasonable next step at home, and several guides, including VPNCentral’s, also suggest changing the DNS servers your PC uses.
3. On a work, school or hotel network, the network may deliberately block VPN traffic, and only the network’s administrator can change that.

If you have a web proxy configured in Windows, try turning it off under Settings > Network & internet > Proxy and connecting again.

6. Check your firewall and antivirus

Both VyprVPN and Microsoft Q&A responders list security software as a possible cause.

1. Temporarily disable your third-party firewall or antivirus.
2. Try the VPN.
3. If it connects, turn your protection back on immediately.
4. Add your VPN app or connection to the security software’s allowed list or exceptions, following that product’s official instructions.

Don’t leave your firewall or antivirus switched off as a “fix.”

7. Update your VPN app

If you use a provider’s app, VyprVPN’s guidance is to make sure you’re on the latest version. Download updates only from your provider’s official website or your device’s official app store.

When the error keeps coming back

Not every case has a neat answer. In one Microsoft Q&A thread, a user reported error 868 even with the server’s IP address hard-coded, and noted that retrying a few seconds later mostly succeeded. That pattern doesn’t fit a simple DNS misconfiguration, and the thread doesn’t include a confirmed fix.

If you’ve worked through every step above and still see the error:

• Note when it happens. Specific networks, times of day or only after sleep are useful clues.
• Contact your VPN provider’s support or, for a work VPN, your IT department. Give them the exact error text and what you’ve already tried.
• Ask whether the server is having problems. If the server name was retired or the service is down, nothing on your PC will fix it.

Bottom line

Error 868 is Windows telling you it couldn’t find the VPN server. Check the server address, flush DNS, try another network, and rule out your firewall: one of those resolves most cases. If none do, the problem is likely on the network or server side, and your provider or administrator is the right next stop.