Fix “The Remote Connection Was Not Made Because The Name of The Remote Access Server Did Not Resolve”

It could be the VPN server’s fault or your computer’s if you encounter the error “The Remote Connection Was Not Made Because The Name of The Remote Access Server Did Not Resolve” when trying to connect to a VPN.

The error code 868 was assigned to this problem in earlier versions of Windows, but it has been eliminated in Windows 10. Nowdays, virtual private networks (VPNs) are ubiquitous, and for some of us, they are our sole means of Internet access.

Still, things might be really frustrating if you find yourself in the midst of VPN-related difficulties. But you needn’t fret any longer; this article will guide you through the options available to you.

The Remote Connection Was Not Made Because The Name of The Remote Access Server Did Not Resolve

Method 1: Killing the DNS And Resetting Winsock

Above, we indicated that your DNS cache may be to blame for this problem. As an added complication, your network connections may be to blame. Therefore, clearing your DNS cache and restarting Winsock will solve the problem. Step by step instructions:

Step 1: To launch a command prompt with administrative privileges, press the Windows key plus X.

Step 2: When prompted, enter this at the command line:

ipconfig /flushdns

ipconfig /registerdns

Step 3: Then, type in these directives:

ipconfig /release

ipconfig /renew

Step 4: Then, click Enter after typing this command to restart Winsock:

Netsh winsock reset

Step 5: Try restarting your computer to see if it resolves the problem.

Method 2: Turn Off Any Extra Antivirus Software

When dealing with this issue, you can also try turning off any additional security software you may be using. When you install an antivirus programme on your computer, it will limit your ability to access the internet and other networks.

Therefore, you should disable your third-party antivirus to rule out the likelihood that it is causing the problem. After disconnecting, restart your VPN connection.

Method 3: Windows Defender Firewall Must Be Disabled.

The Windows Defender Firewall handles all requests for connections, both internal and external. It’s possible that Windows Defender Firewall is preventing you from connecting to your VPN.

As such, you’ll need to temporarily turn it off and check back to see whether the problem persists. To turn off Windows Firewall, do the following:

Step 1: Use the Start menu to access the Settings menu.

Step 2: Click Windows Defender Firewall after changing the View by setting to Bigger icons.

Step 3: To activate or deactivate Windows Defender Firewall, select the corresponding option on the left.

Step 4: Check the box labelled “Turn off Windows Defender Firewall,” and then click OK.

Step 5: To see if the problem has been fixed, try this.

Conclusion

Not much can trigger the problem, but when it does, it’s usually due to the following: The VPN server itself may be at fault if you are unable to establish a connection to the desired network. It’s also possible that the network connections on your computer are to blame for the problem.

Your DNS cache or similar factors may be to blame. Errors can also be caused by any third-party antivirus software you may have installed. It’s possible that the error appears because of the restrictions imposed by your antivirus software.