Remote Desktop not available after cloning a Windows Server 2008 R2 virtual machine

After cloning and syspreping XenApp 6.5 VMs running Windows 2008 R2 SP1, I was not able to connect to the cloned servers by Remote Desktop.

After troubleshooting the steps below, I noticed the the RDP-TCP listener was not listening on a network adapter. (I am certain it occurred while cloning /VMTools update)

Executing the netstat -aon command you find out that the port on which Remote Desktop should listen, isn’t listed in the Local Address column.

  • Log on to the server by using the console
  • Checked the event log for possible errors relating to Remote Desktop services.
  • Verified if no other process is using the default RDP TCP port 3389
  • You also checked the Windows firewall rules and/or disabled the Windows firewall
  • Re-entered the IP address information
  • Reset the TCP/IP stack (netsh int ip reset)
  • Reinstalled the network adapter
  • Verified if the Remote Desktop services indeed was running (services.msc)
  • Checked if the Remote Desktop services port is configured to listen on the default RDP port 3389 (HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber)
  • Entered the command netstat -aon on a cmd prompt to verify if the RDP indeed was open and listening on the configured RDP port, TCP port 3389 by default. Look for in the Local Address column to make sure the port is open.

Solution: (In this case, the RDP-Tcp listener is probably not listening on a  network adapter)

  • Open Remote Desktop Session Host Configuration
  • Double click on the RDP-Tcp connection, the RDP-Tcp Properties appears
  • Select the Network Adapter tab
  • If the Network Adapter drop-down list is empty or set to listen on a specific network adapter (e.g. Intel(R) PRO/1000 MT Network connection), change it to listen to All network adapters configured with this protocol
  • Save the changes and try to connect to the server by Remote Desktop again.