For more information, see Using effective routes to troubleshoot VM traffic flow.Įnsure that any on-premises firewall, or firewall on your computer, allows outbound TCP 3389 traffic to Azure. You can also review effective routes to see all effective routes for a network interface. 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. Click the Redeploy button, and then click Redeploy:Īfter this operation finishes, ephemeral disk data is lost and dynamic IP addresses that are associated with the VM are updated. Scroll down the settings pane to the Help section near bottom of the list. This troubleshooting step redeploys your VM to another host within Azure to correct any underlying platform or networking issues. Select your VM in the Azure portal and click the Overview tab. This troubleshooting step can correct any underlying issues the VM itself is having. Make sure the Mode is set to Reset password and then enter your username and a new password. Once you have logged into the VM, you should reset the password for that user. This troubleshooting step resets the password on a local administrator account when you are unsure or have forgotten the credentials. This troubleshooting step verifies there are no known issues with the Azure platform that may impact connectivity to the VM. For more information, see how to reset NIC for Azure Windows VM.Ĭheck the VM Resource Health. For more information on reviewing the console logs and VM screenshot, see Boot Diagnostics for VMs. Specific troubleshooting steps are beyond the scope of this article, but may indicate a wider problem that is affecting RDP connectivity. Not all VMs have boot diagnostics enabled, so this troubleshooting step may be optional. This troubleshooting step reviews the VM console logs to determine if the VM is reporting an issue. For more information, see Using Effective Security Rules to troubleshoot VM traffic flow. You can also review effective security group rules to ensure inbound "Allow" NSG rule exists and is prioritized for RDP port(default 3389). Use IP flow verify to confirm if a rule in a Network Security Group is blocking traffic to or from a virtual machine. Set the Mode to Reset configuration only and then click the Update button: This troubleshooting step resets the RDP configuration when Remote Connections are disabled or Windows Firewall rules are blocking RDP, for example. If you still cannot connect, try the next step. You can also find steps on troubleshooting VMs created using the Classic deployment model.Īfter each troubleshooting step, try connecting to your VM again.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |