Windows Azure虚拟机RDP远程桌面连接问题（家庭网络环境）

Hey there, let's work through fixing your RDP connection issue with that Azure VM running SQL Server 2016 you set up with the free subscription and default config. Since your home network has no firewall, the problem is almost certainly tied to Azure's network settings or the VM's internal configuration. Here are the key troubleshooting steps:

• Verify Azure Network Security Group (NSG) allows RDP traffic
  Even with default settings, sometimes the NSG rule for RDP (port 3389) might not apply correctly or get accidentally modified. Head to the Azure portal, navigate to your VM, go to Networking under the Settings menu, and check the inbound rules. You need a rule that allows traffic on port 3389:

  • Source: Use your home public IP for security, or select "Any" temporarily for testing
  • Source port ranges: *
  • Destination: Any
  • Destination port ranges: 3389
  • Protocol: TCP
  • Action: Allow
  • Priority: Set to a lower number than any existing Deny rules (e.g., 100)
    If the rule doesn't exist, create it with these parameters.

• Confirm you're using the correct public IP for the VM
  It's easy to mix up public IPs if you have multiple Azure resources. Go to your VM's Overview page in the portal, copy the Public IP address, and double-check that this is the address you're entering in your RDP client. Also, note that default free-tier VMs use dynamic IPs — if the IP changed since you created the VM, that would break the connection. You can switch it to static in the Public IP resource settings if needed.

• Enable RDP and allow it through the VM's Windows Firewall
  Even without a home firewall, the VM's own Windows Firewall might block RDP access. Since you can't connect via RDP right now, use Azure's Serial Console to fix this:

  1. In the Azure portal, go to your VM and select Serial console under Support + troubleshooting.
  2. Log in using your VM's local admin credentials.
  3. Run these commands in the console:

     netsh advfirewall firewall set rule group="Remote Desktop" new enable=Yes
     reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f
     

  This enables RDP on the VM and ensures the Windows Firewall allows the traffic.

• Double-check your VM admin credentials
  Make sure you're using the exact username and password you set when creating the VM. If you forgot the password, reset it via the Azure portal: go to your VM, select Reset password under Operations, choose "Reset password", enter a new password, and save. Then try connecting again with the updated credentials.

• Test port connectivity from your home computer
  To confirm if port 3389 is reachable, open Command Prompt on your home PC and run:

  telnet <VM_Public_IP> 3389
  

  If telnet isn't enabled, use PowerShell instead:

  Test-NetConnection <VM_Public_IP> -Port 3389
  

  If this test fails, the issue is with Azure's network settings (go back to checking NSG rules). If it succeeds, the problem is likely with your RDP client or the VM's local configuration.

Pro tip: If you're still stuck, try restarting the VM from the Azure portal — transient network glitches often get fixed with a simple reboot.

内容的提问来源于stack exchange，提问作者PPrat