4

I was able to connect to Azure VM through RDP earlier but now suddenly I'm unable to connect to VM through RDP.

I tried to connect through Powersell.

Even powershell script was able to connect earlier but not working now. Myself didn't changed anything in Azure VM.

I'm getting below errors.

enter image description here

enter image description here

But I'm able to connect to VM through Bastion.

WinRM is already enabled in Azure VM.

I tried by creating new Azure VM and enabled RDP port 3389 but still getting same connection issue.

How to resolve issue.

S.Chandra Sekhar
  • 453
  • 3
  • 11
  • 22
  • You can follow [this doc](https://learn.microsoft.com/en-us/azure/virtual-machines/troubleshooting/troubleshoot-rdp-nsg-problem) to enable port 3389 in the NSG but change the `Source: Any` to `Source: your client public IP address` when you connect to Azure VM through RDP. – Nancy Apr 17 '20 at 08:19
  • I tried changing source to ip address but still not working. – S.Chandra Sekhar Apr 17 '20 at 10:13
  • I'm having the same issue - able to connect through bastion in Azure portal, but local rdp client does not work. I have a NSG rule to allow connections to port 3389. I followed this guide: https://jeffbrown.tech/azure-bastion-rdp-native-client/ - except it errors out when trying to authenticate: ... \cli\Lib\site-packages\azure/cli/command_modules/network/tunnel.py", line 104, in _get_auth_token msrestazure.azure_exceptions.CloudError: org.apache.guacamole.net.auth.credentials.BiFrostVMUnAvailableCredentialsException: VM is either not accessible or not found. Any ideas? – Tone May 12 '22 at 21:22

1 Answers1

0

When debugging RDP issues one tool I use to test connectivity from a windows client is:

  • start
  • run
  • cmd
  • telnet ip port
  • e.g telnet 99.99.99.99 3389
  • noting you may need to install the telnet client from windows features tool

Try this from multiple locations with different public addresses (including from the VM itself in some circumstances but clearly not for your issue).

Does it connect to the RDP Server listening port ?

If the answer is yes then you know the server is listening.

If the answer is no then the port is likely blocked, service is not available or a routing issue could be the cause.

Thinking out loud review the resources you have sitting in front of the VM:

  • window firewall (Disabling all firewall profiles is a more foolproof way of troubleshooting than setting the RDP-specific firewall rule, see REF)
  • local network outbound traffic blocks
  • firewall in front of the vm

Ref: https://learn.microsoft.com/en-us/azure/virtual-machines/troubleshooting/enable-disable-firewall-rule-guest-os

scott_lotus
  • 3,171
  • 22
  • 51
  • 69
  • Could you please elaborate on points window firewall if you can get to it, local network outbound traffic blocks, firewall in front of the vm . It would be great If you provide steps or any useful links. – S.Chandra Sekhar Apr 17 '20 at 07:45
  • Sorry, I meant the Windows Firewall on the host you are attempting to get too. I understand this is unlikely being that you are attempting to RDP into that host but I listed it as a cause of RDP blocking issues on remote machine. See https://learn.microsoft.com/en-us/azure/virtual-machines/troubleshooting/enable-disable-firewall-rule-guest-os – scott_lotus Apr 20 '20 at 07:03
  • 2
    I figured it out that Issue is with local machine itself not with azure vm. – S.Chandra Sekhar Apr 20 '20 at 18:20
  • thanks for the update John, all the best (ps , its why the telnet test is useful ) – scott_lotus Apr 21 '20 at 12:16