Troubleshoot Remote Desktop connections to an Azure virtual machine

Question Info

When to use Remote Desktop over VPN
A Virtual Private Network, or VPN, is the creation of a smaller private network on top of a larger public network, like the internet. For example, if my public IP was If you haven't already, install and configure the latest Azure PowerShell. Allow TCP to private port I am not an IT person; I am a Win 10 user. Submit your e-mail address below.

Virtual Private Networks

Win 10 - Cannot connect using Remote Desktop over VPN

If they aren't going to have a live Internet connection when they work remotely then set up offline folders in Windows and watch your access permissions on those files so you don't have conflicts when the user returns from the field. Please check the box if you want to proceed.

Find out if you know when and where VDI is a good fit with this quiz on Citrix offers a slew of certifications that prove how well an IT pro knows a certain technology.

To earn a certification, IT pros Successfully deploying virtual desktops is no easy feat. IT pros shared their stories of adopting virtual desktops in a customer Microsoft made Cubic the default congestion control provider for Windows 10 and plans to do the same for Windows Server Administrators should prioritize patching systems affected by four public disclosures resolved by the Patch Tuesday updates.

Admins proficient in PowerShell can build advanced scripts that copy files for different scenarios with added measures to ensure Email attacks are inevitable, so supporting incident response policies and procedures is necessary to ensure your enterprise is Considering an upgrade to Outlook , but unsure if it's worth it?

Get a close look at the sleeker interface, new features and This was last published in April Will IT ever untie from legacy systems? Load More View All News. How do I stop Windows 8 apps from collecting my data? Login Forgot your password? Submit your e-mail address below.

We'll send you an email containing your password. 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.

Check the VM Resource Health. 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:. 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. 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. If you haven't already, install and configure the latest Azure PowerShell. 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. Before you dive into the Registry, you should also note that some routers allow you to listen for traffic on one external port number, but then forward traffic to a different port number and PC internally.

For example, you could have your router listen for traffic coming from the internet on a port number like 55, and then forward that traffic to a specific PC on your local network. You could do it all on your router. So, check whether your router supports this first. If it does, skip the Registry part of these instructions. And our usual standard warning: Registry Editor is a powerful tool and misusing it can render your system unstable or even inoperable.

What port number you choose is up to you, but be aware that some port numbers are already in use. Port numbers can go all the way up to 65,, though, and if you choose port numbers over 50, you should be pretty safe. You can now close Registry Editor. Then move on to the next PC. If your router allows it, you should also enter the name of the PC just to keep things straight.

Ways to troubleshoot RDP issues