Fix Cannot Connect To The Virtual Machine Error In Windows

In this guide, we will explain the method to prevent the issue where you cannot connect to the Virtual Machine.

Workaround: Restart the Virtual Machine

Before making any changes to your system, you must make sure that you have re-started the Virtual Machine manually.

1. Turn on Store my credentials

One of the major reasons why you are facing this error is due to the credentials of User 1 (account logged in to Windows) are being passed instead of User 2 (authenticate to the SSP). By default, the “Do not store my credentials” is selected which causes this error. Therefore, you must manually select the radio button “Store my credentials” on the SSP login page to pass the credentials through User 2.

2. Turn off NUMA Spanning

NUMA Spanning is a setting in the Virtual Machine Manager that allows you to run multiple virtual machines simultaneously. Additionally, it provides extra memory to the virtual machine than the one available on the single NUMA node. However, this setting causes performance issues when connecting to the Virtual Machine. Below are the instructions for turning off the NUMA Spanning setting in the Hyper -V Manager.

3. Uninstall third-party VPN software

Although VPNs are a safe way to keep your data Unencrypted and secure, they are known to cause connection issues with the Virtual Machine you create on Hyper-V. Therefore, it is best to run a VPN directly within the virtual machine and remove any third-party VPN software from your system:

4. Uncheck the override system setting

Code flow guard is a feature in Windows that helps minimize memory corruption. However, it can also be a cause that prevents you from connecting to the Virtual Machine in Hyper-V. Therefore, you must turn it off.

An error in the Hyper-V services can be causing this connection error. Therefore, you must restart the Hyper-V-related services running in the background. You can do that with the instructions below:

6. Remove manual DNS entry

Having a manual DNS Entry saved in your Host file is also a reason that prevents you from connecting to the virtual machine. Therefore, you must check your host file and remove any manual DNS entries such as “rhino.acme.com” present there. You can do that with the steps listed below:

7. Disable the Cryptographic services

Cryptographic services are used for encrypting and decrypting the available data and information stored on the storage devices upon accessing them. However, when connecting to the Virtual Machine, this service will interfere and prevent the connection from being made. Therefore, you must follow the instructions below to disable this service:

8. Change the default Windows port number

Windows has a default port number for the Hyper-V and Virtual Machine connectivity. When Windows fails to communicate with that port number, it fails to connect to the Virtual Machine. Changing this port number is known to fix connectivity errors. Therefore, you can change your default port number with the following instructions: