question

DavidEcho-4023 avatar image
0 Votes"
DavidEcho-4023 asked CarlFan-MSFT edited

Cannot RDP in to a VM?

I have a Windows 10 Pro VM running in Hyper-V on ly laptop, also running Windows 10 Pro. I can use vmconnect.exe to connect to the VM guest.

At some point in the past, that VM had some hardening applied to it from Windows Intune. Since then, it is impossibel to connect to it using mstsc.exe. I would like to modify the VM so that RDP is once again allowed. So far, I have:

1) Enabled RDP
84366-enable-remote-desktop.png


2) Allowed RDP
84307-allow-remote-desktop.png

3) Made sure RDP is allowed through firewall
84367-rdp-through-firewall.png

Yet, I still get this when I try to RDP to the VM using mstsc.exe
84368-remote-desktop-connection-fail.png

What else do I need to change to allow RDP access to this VM again?

Note that there are some other VMs in my Hyper-V host that did not have the hardening script applied, and they are available via RDP without issue.

Thanks
David

remote-desktop-client
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

CarlFan-5627 avatar image
0 Votes"
CarlFan-5627 answered

Hi,
Please check if you could access the VM with IP Address.
In most cases, this error means that there are problems with your DNS servers (or DNS records on them), because of which your computer can’t resolve the specified host name.
Try to connect to the RDP server by IP address instead of the DNS name. If the RDP connection by an IP address is established correctly, this means that the issue may be related to DNS.
Also please uncheck the option "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)." to see.
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DavidEcho-4023 avatar image
0 Votes"
DavidEcho-4023 answered

Thank you Carl

This is what I did to further test this.

1) I have three Windows 10 VMs in Hyper-V. One of these works fine with mstsc.exe, the other two do not.
2) I set up all of these VMs with only the "Internal" vNIC, then I can actually ping it, and see the reported IP address, in this case, the IPv6 address. So, this proves that the DNS is at least working
3) I then tried to connect using mstsc.exe, and both the IPv6 address and the IPv4 address for all three VMs. I connected successfully for the one VM that works by name too, but the other two reported the same issue as pictured above.

I also un-ticked "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)." and still no success.

Note also that the VM that I can connect to with mstsc.exe does have ""Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)." ticked.


Anything else I should look at?

Thanks
David

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

CarlFan-MSFT avatar image
0 Votes"
CarlFan-MSFT answered CarlFan-MSFT edited

Hi David,
Thank you for your update information.
As we can see from the error message, always we could make sure the settings below.
– Ensure the right names are given.
– Also, if you are using Name, ensure the name is resolvable.
– Lastly, if the two steps above do not resolve the issue, ensure your firewall permits this connection.
Also check the information below:
https://appuals.com/fix-remote-desktop-cant-find-the-computer-on-windows-10/
According to your description, one of the three VMs can connect normally with IP and the hostname, but two of them can't.
Could you type "winver" in Search Bar to check the system OS build? Let's check if these three machines are the same version.
I also doubt mstsc file may got corrupted.
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.