Remote Desktop can’t find the computer

hyper-vremote desktopwindows-server-2008-r2

This is my first attempt in setting up some VMs. I am trying to rdp to them but I'm encountering this error

Remote Desktop can't find the computer "[Server]". This might mean that "[Server]" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to.

I am trying to set up some dev servers. I have made 6 machines in Hyper-V, 1 domain controller and 5 member servers.

All running Windows Server 2008 R2 SP1. All on a domain (call it "d.com").

I have created an Internal virtual switch, configuring it as follows:

IPv4 Address = 198.168.10.1
Subnet Mask = 255.255.255.0
DNS Server = 198.168.10.1

For the Domain Controller (call it "DC") and the first member server (call it "S1"), I enabled Remote Desktop allowing for connections from computers running any version following this link's instructions. I did set the services listed in this instruction to start automatically:

DNS Client (already automatic)
Function Discovery Resource Publication
SSDP Discovery
UPnP Device Host

I'm able to ping the IP given above. I checked to see if it's a firewall issue by disabling the firewall in S1 and attempted to rdp but was met with the same error.

Wierdly I was able to rdp yesterday when I first set it all up, but today no such luck. I did spot that the SSDP Discovery service had not started when I spun up the machine, but even starting that did not resolve the issue.

Is there some configuration I'm missing?
Have I misconfigured something?

EDIT: RESOLVED

I amended the IP config of the internal switch, giving it an IP on the same subnet as the VMs, with appropriate subnet mask, and a default gateway (again on the same subnet). I have also removed the DNS server address.

I am now able to ping and remote desktop my VMs from the host machine.

Best Answer

Try using Bridge network in your VMware workstation.Outside devices on same network cannot communicate with VMware machine working inside OS. Please see here in my post how Bridge connection works.

How Bridge Work

Related Solutions

Remote Desktop Problem on Windows Server 2008 R2

If you are seeing SID's in local groups then your DNS or AD access is messed up from that server to either sub or parent domain IMO. RDP access could be a red herring and the real issue is proper connectivity to AD. Do you have event log events talking about unable to resolve account, etc? In a healthy server you should never see SID's IMO (unless accounts are deleted).
It's possible a GPO is affecting member servers security policy "allow log on through Remote Desktop Services" or the often forgotten "deny log on through Remote Desktop Services" inside the computer GPO config. You might be left out of the first or added to the second for member servers GPO, then that could be overwritten at the DC container level by the "default domain controllers policy". Run a Group Policy Results on a member server as you and see what shows up for:

computer config > Policies > Windows Settings > Security Settings > Local Policies > User Rights Assignments > two settings in quotes above

Win7 to W2K8 R2 Remote Desktop fails, yet 3rd party Remote Desktop client connects ok

Is it possible that your Win 7 box got the RDP 6.1 update? If so, perhaps it is failing server authentication. Did you try from another client such as an XP box?

Here's what I'm referring to:

http://support.microsoft.com/kb/951616

Server authentication
In RDC 6.1, server authentication verifies that you are connecting to the correct remote computer or remote server. This security feature helps prevent you from connecting to a computer or server to which you did not intend to connect. This feature also prevents you from unintentionally exposing confidential information.

By default, server authentication is enabled for the connection. However, if you want to change server authentication settings, follow these steps:

    Click Start, click All Programs, click Accessories, click Communication, and then click Remote Desktop Connection.
    Click Options, and then click the Advanced tab. 

The three available authentication options are as follows:

    Always connect, even if authentication fails
    If you enable this option, you can connect even if RDC 6.1 cannot verify the identity of the remote computer.
    Warn me if authentication fails
    If you enable this option, RDC 6.1 tells you if it cannot verify the identity of the remote computer. This option gives you the choice of whether to continue with the connection.
    Do not connect if authentication fails
    If you enable this option, you cannot connect if RDC 6.1 cannot verify the identity of the remote computer.

Related Topic