Remote Desktop Issues

Question

I have recently created a new VM in azure but cannot RDP into it.   The VM was created by uploading the preexisting .vhd to Azure and then creating it from the gallery.  The server is also currently running on my internal network.

Relevant information:

RDP works internally to server(in production network).

Windows firewall is disabled.

UAC is disabled.

Other Azure VM’s can connect through RDP.

Endpoints are created and have been changed.

Server has been re-sized.

Server has been rebooted

Server has been recreated

I have created a test VM in Hyper-V with the VHD file I uploaded to Azure and confirmed functionality.

Azure laaS Windows Diagnostics package has been ran.  It should be noted that only one of my azure servers appear when it query’s for Azure VM’s

Cannot RDP or ping(by ip or DNS name) to problematic server when RDP’d into other Azure VM.  It should be noted that its ip address does appear in arp tables.

In the azure portal it only show CPU usage as .03% all other resources are at 0

Any and all help will be greatly appreciated.

Answer 1

Hi,

Do you see any error messages ? Recommend you to go through this link that talks abt common RDP issues and write back if it helps.

Regards,

Shirisha Paderu

Answer 2

Thanks for your response 

The error I am seeing when attempting to connect to the VM is the generic failure

"Remote Desktop can't connect to the remote computer for one of these reasons"  

1.Remote access to the server is not enabled. 

2.the remote computer is turned off. 

3.The remote computer is not available on the network. 

I did try to telnet to the machine from my workstation and confirmed that it failed.  Please note that telnet works with other azure VM's and for the problematic server when testing internally. 

I have also attempted to connect from another network as well with the same results.  In addition to this I have reset the remote connection settings as well. 

Once again thanks for your time. 

Answer 3

Hi,

What is the status of the VM in the portal ? Make sure the the status of the VM is running.

To what port are you telneting into ?

Please check this thread which has similar issue " Telnet fail to a VM open port "

If that doesn't work, recommend you to use the remote PowerShell by downloading the 3rd party tool - uvnc as shown  here

Regards,

Shirisha Paderu