Share via


I'd to remove de role "DenyAllInBound"

Question

Tuesday, March 28, 2017 3:48 PM | 1 vote

Hi,

Until yesterday my VM worked well, but today when I trying to access my application using telnet on 50050 returns error about connection refusing my request. I investigated and I found a new policy called "DenyAllInBound", created by administrator and I can't remove or alter it. What should do?

Best,

Luiz

All replies (2)

Tuesday, March 28, 2017 5:34 PM âś…Answered | 3 votes

Network security groups come with a default set of rules configured on them, which you cannot remove, one of these is DenyAllInbound rule, which as it states denies all inound traffic. This rule is not your problem, these rules have a very low priority (65000) and so are design to be applied after all the rules you have added, so that if you have a rule that allows port 443 then this takes precedence over the deny all rule, but for all the other ports that you have not defined a rule for, traffic is not allowed. It basically means that the NSG is a whitelist, if you don't specifically allow a port then it won't be allowed. Default rules are normally hidden, but you can view them if you look in the right place.

So, back to your issue, if you are no longer able to access your application via port 50050 there are a few possible reasons:

1. You don't have an NSG rule to allow inbound traffic on port 50050, or it has been removed, so set this up

2. The firewall in the VM its self (windows firewall or similar) is blocking this, you'll need to open the port there as well

3. The application that should be responding is not actually running, or has crashed.

Sam Cogan Microsoft Azure MVP
Blog | Twitter


Wednesday, January 16, 2019 8:42 PM

Many thanks for your answer, it actually solved the issue for me.

So I had to create an inbound and outbound network rule for the port so that I can connect.