question

soulaimanebouderna-5355 avatar image
0 Votes"
soulaimanebouderna-5355 asked kobulloc-MSFT commented

Not able to connect to VM

hi i had probleme with rdp connection whene i try to test connction to rdp this error was appear to me " Network connectivity blocked by security group rule: DefaultRule_DenyAllInBound " i followed the step listed here- https://msft.it/6013nzs0P and i enable the RDP port in an NSG.
after that I could connect to the vm but after 5 minute the connection was closed I can't even connect by Bastion
and i m Not able to connect to VM
itry to restarted, redeployed. But still did not work any solution


Error code:
We couldn't connect to the remote PC. Make sure the PC is turned on and connected to the network, and that remote access is enabled.

azure-virtual-machines
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Do you have any inbound security rules lower than 300 which might block traffic and are you still getting the "Network connectivity blocked by security group rule: DefaultRule_DenyAllInBound" or are you just getting the "We couldn't connect to the remote PC" error now?

109152-image.png


0 Votes 0 ·
image.png (22.1 KiB)

1 Answer

soulaimanebouderna-5355 avatar image
1 Vote"
soulaimanebouderna-5355 answered kobulloc-MSFT commented

no i Dont have any inbound security rules lower than 300 i just getting the "We couldn't connect to the remote PC" When I created a new instant with a new plan, this problem no longer exists
Perhaps the problem is with the plan, it is no longer available

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you for the update! So everything works now on the new plan? If you're up for sharing, what was the old plan that was failing?

0 Votes 0 ·