RDP or SSH Port Did Not Respond to Port Scan, unable to fix after following all troubleshooting steps

Question

RDP or SSH Port Did Not Respond to Port Scan, unable to fix after following all troubleshooting steps

Kate Waldhauser 0

I'm unable to connect to my VM via RDP or WAC. It appears there is a firewall on my Windows machine, but I'm unable to successfully open this port on the Windows machine.

The error I'm seeing under diagnostics is:
When Virtual machine did not respond to a port scan of port '3389'.

Dharani Reguri 1,175 Reputation points Microsoft External Staff Moderator

2025-04-25T17:46:58.0533333+00:00
Hi Kate Waldhauser,

In addition to Andreas Baumgarten, if you have serial console access, could you please check the Windows Firewall on your VM is not blocking traffic on port 3389 using the following command to ensure the firewall rule is enabled:

Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Set-NetFirewallRule -Enabled True

Also check if RDP is enabled in Registry by running following command in serail console.

Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections

Please let me know the results of the commands.

Thank you
Dharani Reguri 1,175 Reputation points Microsoft External Staff Moderator

2025-04-28T08:46:45.6566667+00:00

Hi Kate Waldhauser,

Just checking in to see if you have got a chance to see my response to your question in resolving the issue.

If it was helpful, please click "Upvote" on this post to let us know.

Thank You.

2 answers

Your answer

Dharani Reguri 1,175 Reputation points Microsoft External Staff Moderator

2025-04-25T17:46:58.0533333+00:00

Hi Kate Waldhauser,

In addition to Andreas Baumgarten, if you have serial console access, could you please check the Windows Firewall on your VM is not blocking traffic on port 3389 using the following command to ensure the firewall rule is enabled:

Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Set-NetFirewallRule -Enabled True

Also check if RDP is enabled in Registry by running following command in serail console.

Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections

Please let me know the results of the commands.

Thank you
Dharani Reguri 1,175 Reputation points Microsoft External Staff Moderator

2025-04-28T08:46:45.6566667+00:00

Hi Kate Waldhauser,

Just checking in to see if you have got a chance to see my response to your question in resolving the issue.

If it was helpful, please click "Upvote" on this post to let us know.

Thank You.

Answer 1

Andreas Baumgarten 123.4K MVP Volunteer Moderator

Hi @Kate Waldhauser ,

did it work before? Or it never worked before?

From where do you try to connect to the Azure VM via RDP? From your on-premises computer? Or from another Azure VM (same or different vnet/subnet)?

If you try to connect from your computer: Is there a Network Security Group (NSG) associated with the Azure VM NIC and/or the subnet the Azure VM is connected to? If so please check the rules if there is a rule allowing incoming TCP on port 3389.

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards

Andreas Baumgarten

Kate Waldhauser 0 Reputation points

2025-04-25T15:43:46.62+00:00

Thank you, @Andreas Baumgarten . I am trying to connect from my on premise machine. It was wrong successfully before today.I have tried resetting the NIC and even redeploying, and I've added the incoming port rule to the NSG.

Answer 2

Andreas Baumgarten 123.4K MVP Volunteer Moderator

Hi @Kate Waldhauser ,

are you connecting via Public IP or via VPN connection from your machine to the Azure VM?

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards

Andreas Baumgarten

Share via

RDP or SSH Port Did Not Respond to Port Scan, unable to fix after following all troubleshooting steps

2 answers

Your answer