Note: We just discuss the Windows Server Virtual Machine here.
When creating a Virtual Machine from Azure Management Portal, the Remote Desktop endpoint is created by default. From the Windows Azure Management Portal, we could select the virtual machine, then clickConnect to start the remote session.
However, sometimes, we could not connect the virtual machine, and we may see the error below (Figure 1):
Figure 1: Remote Desktop Connection Error Message
This issue could be caused by many factors, you can refer to the checklist below to narrow down the issue.
1. Make sure the virtual machine is running in Azure Management Portal.
2. Make sure the username and password are correct.
The username and password are created when we create the virtual machine. When RDP to the virtual machine from Management Portal, we just need to input the correct username and password.
3. Make sure the domain information.
If the RDP connection fails, we need to check the domain information. If the domain information is not correct, please selectOther User, add a backslash before user name and then input the password.
4. Remote Desktop endpoint is missing.
Each virtual machine that is created should have a remote desktop endpoint at TCP Port 3389 (Figure 2).
Figure 2: TCP Port 3389
If this endpoint is deleted then a new one should be created. The public port can be any available port number. But the private port must be 3389. For more and detail information about setting up endpoints, please refer to: How to Set Up Endpoints to a Virtual Machine
5. Connect using a different network.
If you are using a corporate network, try a network that’s separate from the corporate network. If that works, it indicates that the corporate network doesn’t allow that type of connection. For example, the connection might be blocked by the corporate firewall. Contact your corporate network administrator for help.
6. If none of above steps resolve the problem, resize the virtual machine to have a try.
Warning: All data on the D: drive will be lost when changing the virtual machine size and the VM ends up on a different host. So if you have data on D: that you care about losing, move it to C: or to a data disk before changing the virtual machine size.
If you need further assistance, welcome to post your questions in the Windows Azure forum.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.