The issue can be with the Remote Desktop service on the VM, the network connection, or the Remote Desktop client on your host computer.
This article guides you through some of the most common methods to resolve RDP connection issues. Alternatively, you can file an Azure support incident. Go to the Azure support site and select Get Support.
Quick troubleshooting steps After each troubleshooting step, try reconnecting to the VM: Reset Remote Desktop configuration. Review VM console logs. Check the VM Resource Health. Reset your VM password. Restart your VM. Redeploy your VM. Continue reading if you need more detailed steps and explanations. Verify that local network equipment such as routers and firewalls are not blocking outbound TCP port , as noted in detailed RDP troubleshooting scenarios. You can read more about public IP addresses in Azure.
Azure portal - great if you need to quickly reset the RDP configuration or user credentials and you don't have the Azure tools installed. You can also find steps on troubleshooting VMs created using the Classic deployment model. Troubleshoot using the Azure portal After each troubleshooting step, try connecting to your VM again.
If you still cannot connect, try the next step. Reset your RDP connection. Select your VM in the Azure portal. Click the Reset password button. Set the Mode to Reset configuration only and then click the Update button: Verify Network Security Group rules. Use IP flow verify to confirm if a rule in a Network Security Group is blocking traffic to or from a virtual machine.
You can also review effective security group rules to ensure inbound "Allow" NSG rule exists and is prioritized for RDP port default Review VM boot diagnostics. This troubleshooting step reviews the VM console logs to determine if the VM is reporting an issue.
Not all VMs have boot diagnostics enabled, so this troubleshooting step may be optional. Specific troubleshooting steps are beyond the scope of this article, but may indicate a wider problem that is affecting RDP connectivity. This troubleshooting step verifies there are no known issues with the Azure platform that may impact connectivity to the VM.
Click the Resource health button. A healthy VM reports as being Available: Reset user credentials. This troubleshooting step resets the password on a local administrator account when you are unsure or have forgotten the credentials. Once you have logged into the VM, you should reset the password for that user. Make sure the Mode is set to Reset password and then enter your username and a new password.
Finally, click the Update button: This troubleshooting step can correct any underlying issues the VM itself is having. Select your VM in the Azure portal and click the Overview tab. Click the Restart button: This troubleshooting step redeploys your VM to another host within Azure to correct any underlying platform or networking issues. Click the Redeploy button, and then click Redeploy: After this operation finishes, ephemeral disk data is lost and dynamic IP addresses that are associated with the VM are updated.
Verify routing. Use Network Watcher's Next hop capability to confirm that a route isn't preventing traffic from being routed to or from a virtual machine. You can also review effective routes to see all effective routes for a network interface.
For more information, see Using effective routes to troubleshoot VM traffic flow. Ensure that any on-premises firewall, or firewall on your computer, allows outbound TCP traffic to Azure. If you are still encountering RDP issues, you can open a support request or read more detailed RDP troubleshooting concepts and steps.
Replace these variable names and locations with your own values. In the following examples, myVMAccessExtension is a name that you specify as part of the process. To view the name, look under the 'Extensions' section of the output.
After each troubleshooting step, try connecting to your VM again. Verify that a rule exists to allow TCP port for inbound connections as follows: Succeeded Description: Allow Priority: Allow TCP port This troubleshooting step resets the password on the local administrator account that you specify when you are unsure of, or have forgotten, the credentials. Password Restart your VM.
Troubleshoot VMs created using the Classic deployment model After each troubleshooting step, try reconnecting to the VM. Click the More button, then click Reset Remote Access: Verify Cloud Services endpoints. This troubleshooting step verifies that you have endpoints in your Cloud Services to permit RDP traffic. Click the Endpoints button to view the endpoints currently configured for your VM. The following example shows valid endpoints that permit RDP traffic: Allow TCP to private port Click the Resource Health button.
This troubleshooting step resets the password on the local administrator account that you specify when you are unsure or have forgotten the credentials. Enter your username and a new password. Finally, click the Save button: The following are the most common error messages:
Information. With Parallels Access you can easily access your virtual machine and work with your applications as if they are installed on your iPad. Depending. Nov 23, - The Remote Desktop Protocol (RDP) connection to your Windows-based Azure virtual machine (VM) can fail for various reasons, leaving you. Aug 9, - There can be multiple reasons for not being able to access your VM via Remote Desktop depending on the error you are getting. If you are.
Before starting the connection, you'll need to do the following preparations on the virtual machine. Set up the remote PC to allow remoting connections. You'll need to allow remote connection to your computer installed on virtual machineware. Look up the IP address of the remote computer. IP addresses are listed there.