Fix: ‘The remote connection was not made’ Windows 10 error

Matthew Adams
by Matthew Adams
Author
Loading Comments
Affiliate Disclosure

VPNs (Virtual Private Networks) are tools used to make it harder for outside entities to track your browsing behavior while circumventing censorship. Although they are generally reliable, one error you might get when establishing a connection to VPN is “The remote connection was not made because the name of the remote access server did not resolve” error. This is how you can fix ‘the remote connection was not made’ VPN error in Windows 10.

How to fix The remote connection was not made error on Windows 10?

The remote connection was not made error can cause many issues on your PC, and speaking of this problem, here are some similar errors that users reported:

  • The remote connection was not made because the name of the remote access server did not resolve – This problem can occur due to your VPN. If you encounter this issue, be sure to check your VPN settings and see if that helps.
  • The remote connection was not made because the VPN tunnels failed Windows 10 – This is another variation of this problem. If you encounter this issue, try disabling your antivirus or firewall and check if that helps.
  • A connection to the remote access was not made because the modem was not found – According to users, this error can appear due to your DNS, so try changing your DNS settings and check if that solves the problem.
  • The remote connection was not made error 800, 868 – There are various error codes that can appear alongside this message. However, you should be able to fix them using one of our solutions.
  • The remote connection was denied, has timed out, was interrupted and is reconnecting – These are some common problems that can appear, and in most cases these issues are caused by your configuration. To fix the problem, check the configuration and see if that helps.

Solution 1 – Double-check the Hostname

First, double-check you’re entering the correct hostname. Make sure there are no typos in the hostname entered to connect with VPN. Alternatively, you can also establish a VPN connection with your server IP address instead.

Solution 2 – Flush the DNS and reset connections with Command Prompt

Flushing the DNS (Domain Name System) and resetting network settings together are one of the most effective fixes for this VPN error.

  1. First, open the Command Prompt by pressing the Win key + X hotkey and selecting Command Prompt (Admin).
    The remote connection was not made because the VPN tunnels failed Windows 10
  2. Run the following commands one by one:
  • ipconfig /flushdns
  • ipconfig /registerdns
  • ipconfig /release‘ipconfig /renew
  • netsh winsock reset

After running these commands, check if the problem is resolved.

Solution  3 – Close anti-virus software and firewalls

If you keep getting The remote connection was not made error message, the problem might be your antivirus or firewall. Third-party antivirus tools can sometimes interfere with Windows and cause this and other errors to occur.

To fix the problem, you need to disable certain antivirus features and check if that helps. If the issue is still there, you might have to temporarily disable your antivirus. In worst case scenario, you might have to remove your antivirus and check if that solves the problem.

If removing your antivirus solves the issue, you should consider switching to a different antivirus software. There are many great antivirus tools on the market, but if you want maximum security, you should consider using Bitdefender.

Solution 4 – Disable your firewall

Firewall is a great security feature, but sometimes your firewall can cause The remote connection was not made error to appear. If you encounter this issue, you might have to temporarily disable your firewall.

To do that, just do the following:

  1. Press Windows Key + S and enter firewall. Now choose Windows Defender Firewall from the list.
    A connection to the remote access was not made because the modem was not found
  2. When Windows Defender Firewall window opens, select Turn Windows Defender Firewall on or off.
    The remote connection was not made error 868
  3. Now select Turn off Windows Defender Firewall (not recommended) for both Private and Public networks. Click OK to save changes.
    The remote connection has timed out

After doing that, your firewall should be completely disabled. Now check if the issue is still there. If the problem doesn’t appear, it means that your firewall isn’t properly configured. To fix the problem, you need to enable your firewall and check your configuration.

Solution 5 – Change your DNS

According to users, you can fix the problem with The remote connection was not made message simply by changing your DNS. To change the DNS, you need to do the following:

  1. Right-click the network icon on your Taskbar and select your network from the menu.
    A connection to the remote access was not made because the modem was not found
  2. Now click on Change adapter options.
    The remote connection was not made error 800
  3. List of all network connections on your PC will now appear. Right-click your network connection and choose Properties.
    The remote connection was denied
  4. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
    The remote connection was not made because the name of the remote access server did not resolve
  5. Now select Use the following DNS server addresses and enter 8.8.8.8 as a Preferred DNS server and 8.8.4.4 as Alternate DNS server. Now click OK to save changes.
    The remote connection was not made because the VPN tunnels failed Windows 10

After doing that, you’ll use Google’s DNS and the issue should be resolved. If you want, you can also use OpenDNS or any other DNS by using this method.

Solution 6 – Restart RasMan process

Many users reported that The remote connection was not made error message can occur due to RasMan process. To fix the problem, it’s required that you restart this process. This is relatively simple, and you can do it by following these steps:

  1. Open Command Prompt as administrator.
  2. When Command Prompt opens, enter the following commands:
  • net stop RasMan
  • net start RasMan

After running these two commands, the RasMan process will restart and the issue should be completely resolved.

Solution 7 – Disable your proxy

Many users use proxy in order to protect their privacy online, but sometimes your proxy can cause The remote connection was not made error to appear. To fix the problem, it’s advised to disable your proxy. This is relatively simple, and you can do it by following these steps:

  1. Open the Settings app and go to Network & Internet.
    The remote connection was interrupted
  2. Select Proxy from the menu on the left and in the right pane disable all options.
    The remote connection was not made because the name of the remote access server did not resolve

After disabling proxy, check if the problem is resolved.

Solution 8 – Perform a clean boot

Sometimes third-party applications or services can interfere with Windows and cause this and other errors to appear. To fix the problem, you need to start your PC in Clean boot mode. This is quite simple, and you can do it by following these steps:

  1. Press Windows Key + R and enter msconfig. Now press Enter or click OK.
    The remote connection was not made because the name of the remote access server did not resolve
  2. System Configuration window will now open. Go to Services tab and check Hide all Microsoft services. Now click Disable all button.
    The remote connection was denied, has timed out
  3. Navigate to Startup window and click Open Task Manager.
    The remote connection was not made error 800
  4. Task Manager will now open and you’ll see a list of startup apps. Right-click each entry on the list and choose Disable from the menu.
    The remote connection was denied
  5. Once you disable all startup apps, go back to System Configuration window and click Apply and OK and restart your PC.
    A connection to the remote access was not made because the modem was not found

Once your PC restarts, check if the problem is still there. If not, you need to enable disabled services and apps one by one until you find the cause. Once you find the problematic application, you need to remove it, preferably with software such as IOBit Uninstaller, in order to permanently solve the issue.

For further details on how you can fix VPN errors, check out this Windows Report article.

Editor’s Note: This post was originally published in April 2017 and has been since completely revamped and updated for freshness, accuracy, and comprehensiveness.

READ ALSO:

Tags